A public playbook documenting Babylon's iOS engineering team structure, roles, and squads to promote transparency.
iOS Playbook is an open-source documentation repository from Babylon that publicly shares their iOS engineering team's organizational structure, squad breakdowns, and team member information. It provides transparency into how a healthcare technology company organizes its mobile development teams and serves as a reference for engineering culture.
iOS developers interested in engineering team structures, tech leads looking for organizational inspiration, and developers considering roles at Babylon who want to understand their team dynamics.
It offers genuine insight into real-world team organization at a scale-up healthcare company, promoting transparency and serving as a public resource for the developer community rather than being kept internally.
The iOS Playbook is an open-source documentation project from Babylon that provides insight into their iOS engineering team's organization and ways of working. It serves as a transparent resource for the community and potential collaborators, showcasing how a large-scale healthcare technology company structures its mobile development efforts.
The project believes transparency should be present in everything they do, using this playbook to openly share their engineering culture and organizational approach with the wider community.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Clearly champions Babylon's core value of transparency, as stated in the README: 'we firmly believe that transparency is a core value,' making it a genuine open-source effort.
Provides detailed organization into squads like Partnerships and Real-Time Matching with missions, as shown in auto-generated tables from YAML files, offering real-world insights.
Includes GitHub and Twitter handles for all engineers, such as @scass91 and @TheAdamBorek, enabling easy community connection and recruitment outreach.
Uses Ruby scripts to auto-generate tables from squads.yml, ensuring maintainability and reducing manual errors, as noted in the README comments.
Lacks code samples, architectural diagrams, or development practices, limiting utility for developers seeking hands-on iOS guidance beyond team organization.
While auto-generated, it only provides a current team view without insights into dynamic processes, collaboration tools, or historical changes, reducing adaptability lessons.
Missing information on how squads operate day-to-day, workflow processes, or tooling, which limits practical application for teams looking to replicate success.