# Organizational Structure: Building for Growth | PointFive Canonical: https://www.pointfive.co/blog/organizational-structure-building-for-growth How PointFive's Pod-based engineering structure enables teams to move fast while maintaining deep technical expertise across AWS, GCP, Azure, and core... By: Ilai Fallach Published: 2025-03-04 [All articles](https://www.pointfive.co/blog) Ilai Fallach March 4, 2025 5 min read ## Structure Shapes Behavior How you organize an engineering team determines how fast it moves, how well it communicates, and how deeply it can specialize. At PointFive, we use a Pod-based structure -- small, cross-functional teams aligned to specific product domains. This approach lets us scale without sacrificing speed or ownership. ## Why Pods The Pod model is not novel, but the reasons we chose it are specific to the challenges we face: - Empowering teams -- Each Pod owns its domain end-to-end. Teams make decisions closest to the work, which reduces bottlenecks and increases accountability. - Maximizing technical expertise -- Cloud cost optimization spans AWS, GCP, and Azure, each with its own services, pricing models, and quirks. Pods develop deep expertise in their domain rather than spreading knowledge thin. - Reducing cognitive load -- Engineers perform best when they can focus. A well-scoped Pod means less context-switching and fewer competing priorities. - Fostering innovation -- Small teams with clear ownership are more likely to experiment, iterate, and push boundaries within their domain. - Knowledge sharing -- While Pods specialize, we build mechanisms to ensure knowledge flows across the organization. ## Practical Implementation Each Pod is a focused team typically composed of a Product Manager, a cloud researcher, and a group of engineers. This mix ensures that every team has direct access to customer context, domain expertise, and execution capacity. Day-to-day, Pods follow unified workflows: - Daily standups to surface blockers and coordinate work - Bi-weekly planning to set priorities and commit to deliverables - Retrospectives to reflect on what worked and what needs to change - Linear for task management to keep work visible and progress measurable This consistency across Pods makes it easy for engineers to move between teams when needed and ensures leadership has a clear view of progress across the organization. ## The Platform Pod Not everything fits neatly into a product domain. Some work spans the entire system -- APIs, unified data models, shared UX patterns, cross-cloud abstractions. That is where the Platform Pod comes in. The Platform Pod is responsible for system-wide integration. It builds and maintains the infrastructure that other Pods depend on, ensuring consistency and reducing duplication. When a new cloud provider integration needs a shared data model, or the frontend needs a common component library, the Platform Pod leads that work. ## Functional Forums (Guilds) Pods optimize for depth within a domain, but engineering also needs breadth. Functional Forums -- sometimes called Guilds -- provide cross-Pod collaboration around shared disciplines: - Frontend Guild -- Aligns on UI patterns, component standards, and frontend architecture across all Pods. - Data Collection Guild -- Coordinates how we ingest and normalize data from cloud providers. - Data Platform Guild -- Ensures our data infrastructure scales consistently as new sources and workloads are added. Guilds meet regularly, share best practices, and drive alignment on technical standards without introducing heavy governance. ## Growing With the Structure The Pod model is designed to scale. As PointFive grows, we can add new Pods for new product domains without reorganizing the entire team. The combination of focused Pods, a shared Platform team, and cross-cutting Guilds gives us both speed and coherence -- exactly what a growing engineering organization needs. ## Related reading [All articles](https://www.pointfive.co/blog) - ### [AWS Lambda MicroVMs: the foundation AI teams skipped is now rentable](https://www.pointfive.co/blog/aws-lambda-microvms-the-foundation-ai-teams-skipped) June 29, 2026 5 min read - ### [Strategic Guiding Principles: The Foundation of a Thriving Engineering Organization](https://www.pointfive.co/blog/strategic-guiding-principles-the-foundation-of-a-thriving-engineering-organization) February 20, 2025 5 min read - ### [How PointFive Enabled Cloud Cost Ownership and Action for Nubank Engineers](https://www.pointfive.co/blog/how-pointfive-enabled-cloud-cost-ownership-and-action-for-nubank-engineers) November 14, 2024 6 min read --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.