Maria Angelidou-Smith on Product Reviews, Hiring and Building Better Teams

Harry Stebbings asks Maria Angelidou-Smith, Personio’s chief product and technology officer, how she joined Facebook. In 2013 she nearly skipped a former employer’s alumni event, but went to congratulate a friend. A product leader spoke so passionately about Facebook that Angelidou-Smith visited, interviewed and received an offer within minutes of leaving, she recalls.

She joined as a product manager when she estimates the company had about 3,000 people and fewer than 100 product managers. Moving from individual contributor to manager meant responsibility for all of the team’s products and outcomes, as well as understanding people’s strengths, development needs and performance.

Stebbings asks whether career progression wrongly pushes excellent individual contributors into management. Angelidou-Smith agrees that a clear senior individual-contributor path matters. At Meta she helped introduce product-manager archetypes so people with different strengths could progress as far as vice president without becoming people managers.

Her three specialist archetypes sit alongside a generalist path. A captain coordinates complex work across many teams; an entrepreneur brings an idea from zero to product-market fit; a specialist has deep expertise in a domain such as integrity, growth or machine learning. The framework is intended to recognize different strengths rather than make every strong product manager the same.

A product leader, she says, also needs general-management skills: business judgment, resource allocation across products, management of a healthy profit-and-loss statement and responsibility for business outcomes. Product intuition alone is not enough when the job spans a portfolio.

Her first role at Facebook, in monetization, was one of the hardest of her career. She recalls a strong feedback culture in which people sometimes gave contradictory advice about the same meeting. Stebbings asks whether that suggests bad management; she says it taught her to calibrate which feedback to use.

To keep a product coherent as teams add features, Angelidou-Smith recommends consistent design guidelines, reusable front-end components and a shared tone of voice. These tools help independently developed parts feel like one product. She believes product combines science and art: data and method improve the odds, but judgment is needed for breakthroughs.

Asked to choose speed or quality, she says teams can often improve both. While more polishing can take longer, teams are rarely operating at their maximum potential. Better talent, ways of working and tools can move the whole speed-quality frontier, rather than merely trading one for the other.

She sees process as a common constraint but is wary of either extreme. Pure initiative can create conflicting work and chaos; excessive process can train people to wait and create bureaucracy. Her preference is the minimum process needed to help teams move faster or ship better products.

Angelidou-Smith sets aside two or three hours a week for product reviews without requiring every slot to be filled. She and her reports pull in ambiguous priorities, while teams can also request a review to resolve decisions or trade-offs. She asks for only people needed to contribute, typically up to ten, and records the meeting and actions for others.

She identifies four review types: strategy reviews define the problem and opportunity; roadmap reviews examine sequencing, milestones and goals; launch reviews check readiness and user experience; business reviews examine financial performance and operating levers. A meeting goes poorly when the team has not identified the important questions it needs answered.

Participants receive a written pre-read at least 24 hours ahead and add comments before the discussion. Angelidou-Smith says she makes a point of reading material sent on time, but cannot promise to read something delivered an hour before. Preparation is meant to make the meeting a decision discussion rather than a presentation.

Stebbings contrasts open debate with directive leadership and worries that talk consumes time. Angelidou-Smith values “strong opinions, loosely held”: do enough work to develop a view, share it, invite challenge and actively seek new information. She agrees that discussion is costly and that unproductive philosophizing is a warning sign.

When Stebbings says a leader can direct action and let the team return with evidence of a mistake, she says action and debate can coexist. Fast decisions unblock execution, but teams learn during execution and should revisit their choices. She argues leaders miss useful information if they refuse to hear smart colleagues.

“Possibility thinking” means allocating attention to ambitious ideas as well as incremental improvements. Large bets are less predictable and take longer, but may create step-change growth. To support them, leaders should state the strategy, assign resources across time horizons and reward thoughtful attempts even when some fail.

Stebbings describes asking teams what very different figures would do with the product to generate alternative ideas. Angelidou-Smith adds that a successful launch is usually not obvious at one instant: signals accumulate during discovery, testing and iteration. She recommends exploring a second product one or two years before results will be needed.

For a mature multi-product company, she divides capacity among new products and major bets, improvements to existing products, and maintenance plus internal productivity. As an illustrative allocation she suggests 30–40% each for existing and new products and about 25–30% for maintenance and productivity, with 5–10% of capacity for planting new seeds. These are guidelines, not a fixed formula.

She wants to hire direct reports who are stronger than she is in important areas and people she could imagine reporting to. Stebbings objects that this would exclude promising younger candidates. She clarifies that junior candidates should be assessed for potential, while even senior hires may be stronger in some dimensions rather than every one.

Her hiring process has four phases: recruiting and exploratory screens; functional interviews on product sense and execution; a case study; and leadership, drive and values interviews followed by a debrief. Product-sense interviews assess customer understanding and decisions under ambiguity, while execution interviews examine goals and measurement.

Stebbings worries that a long process will deter top candidates. She says it can be completed quickly if designed well. She nearly withdrew from Personio’s own lengthy case study before joining, but the real challenges described in it drew her in; she later retained the exercise while shortening it to roughly an hour and giving candidates at least two days.

Angelidou-Smith advises candidates to negotiate compensation, noting from her experience that women often negotiate less than men. She suggests negotiating with the recruiter if a direct discussion with the manager feels uncomfortable. She treats titles differently: organizations need consistent levels, so titles are not always as negotiable as pay.

A very poor hire can become apparent within weeks, she says, though many cases are less clear. The discussion turns to probation and differences between European and US employment arrangements. These are their observations in conversation, not jurisdiction-specific legal advice.

She says specialist hiring has been harder in Europe in her experience because the pool of candidates with relevant experience can be thinner. She believes this can slow companies without preventing them from becoming exceptional. Her numerical comparison of candidate availability is an anecdotal impression, not a measured labor-market study.

Angelidou-Smith generalizes that US employees may tie more identity to work, while in Europe work may play a smaller role; she believes this can affect effort. Asked about entitlement, she points to some younger first-time workers on both continents. These are personal impressions, not conclusions about individual workers or entire populations.

At Personio she researched remote work and chose to continue hiring remotely to access talent and hire faster. She acknowledges a loss of informal conversation and relationship-building. Her mitigation is regular in-person gatherings: she asks teams to meet at least quarterly.

About 30% of her product and technology organization worked remotely at the time, she says. The team uses asynchronous tools where possible, while structured product reviews can still work remotely. For brainstorming, she keeps time open to call people across levels rather than scheduling every interaction through direct reports.

She describes a general tendency for US companies to rely more on initiative and European companies more on process, while stressing that European firms can build initiative-driven cultures deliberately. Stebbings adds that employment decisions can be harder in Europe; their discussion is broad and does not establish rules for any particular country.

She recalls strongly disagreeing with a manager about promoting someone she had hired and developed. Her manager explained that promotions should follow sustained evidence of performing at the next level. Premature promotion can expose an employee to unfavorable comparisons and poor ratings; the lesson changed Angelidou-Smith’s mind.

Stebbings objects that people may not do the next job until someone gives them the opportunity. She replies that employees can take on higher-level responsibilities and demonstrate readiness before the title changes. The exchange illustrates a tension between creating opportunities and calibrating promotions fairly.

Common product-hiring mistakes include not knowing what the role requires, failing to assess candidates effectively and compromising too quickly. A collection of individually promising junior product managers also may not make a strong team if nobody has the experience to coach them.

Her advice to a new chief product officer is to build context quickly: speak with customers and finance, use the company’s products and competitors, and learn the business. At the same time, start contributing to the team and peers rather than waiting until expertise is complete.

She praises Microsoft’s AI strategy under Satya Nadella and highlights Instacart under Fidji Simo, a former Meta colleague, for its operating turnaround, advertising business and partnerships. These are her assessments of other companies, not independently verified causal analyses or investment recommendations.