Functional org: depth and specialization
A functional organization groups people by discipline. All engineers report to the VP of engineering. All designers report to the VP of design. All product managers report to the Chief Product Officer. Within each function, there are sub-levels: junior, senior, staff. The career path is vertical: engineer to senior engineer to staff engineer to principal. This structure optimizes for depth: an engineer works with other engineers, learning from them, building expertise in a narrow domain.
Functional orgs are natural for specialized disciplines. Engineers can mentor other engineers and push the technical frontier. Designers can establish design systems and maintain craft. Data scientists can collaborate on methodologies. The clarity of reporting is high: everyone knows who their manager is and how they advance. The downside is coordination overhead: a product feature requires engineering, design, product, and data to align, which necessitates synchronous meetings and project management.
Matrix org: cross-functional ownership
A matrix organization overlays product or project lines on top of function. An engineer reports to the VP of Engineering (functional manager) but is assigned to Product A (product manager). The engineer works with designers, product managers, and other disciplines who are also assigned to Product A. The functional manager handles career development and technical standards. The product manager handles priority and project delivery.
Matrix orgs optimize for cross-functional collaboration. A small team owns a feature end-to-end, which reduces hand-offs and aligns incentives. The downside is complexity: dual reporting creates ambiguity when priorities conflict. Which manager's priorities win? It is also harder to move people between projects without losing them; they have weak ties to their functional group. Teams that run matrix well use clear decision frameworks (who decides technical approach vs product approach) and invest heavily in cross-functional mentorship. Teams that run it poorly experience role confusion and slow decisions.