Village: Expanding Engineering Capacity for a Community Intelligence Platform
How a platform for community-led businesses engaged an iOS Engineer.
Challenge
Village builds the intelligence layer for community-led businesses: turning what members actually do into signals about retention and revenue: who is drifting, who is worth a call, where recurring income is quietly leaking away. Part of that reaches members through an iOS application. Build and release engineering is work that rarely competes successfully with product work for a small team’s attention, and it becomes more valuable the longer a product runs, because an automated pipeline turns every release after it from an event into a routine. Village chose to put that foundation in deliberately, rather than carrying it as a standing item on the roadmap.
So the request was for an iOS engineer brought in for release engineering. Seven years across cross-platform and native mobile, team leadership through full delivery cycles, TypeScript and Expo alongside native module work in Swift and Kotlin, and a track record of raising the standard of other engineers’ work rather than only producing their own. The engagement was also deliberately temporary because the work was sequential, and more hours would not have made it finish sooner.
Work of this kind screens differently from feature work. The engineer has to open an unfamiliar codebase, get it building on their own machine, understand how it is configured, and then put a pipeline around it that a team of two founders can maintain afterwards. Shortlisting went to engineers who had built mobile CI/CD from scratch rather than maintained someone else’s, and who had the seniority to make configuration decisions that would still make sense in a year. Both the CEO and the CTO interviewed, and the engagement was confirmed 24 hours after the request opened.
Outcome
The useful thing about release engineering is how quickly it pays back. Source checked out and building locally, an application issue reviewed, a CI/CD pipeline and tests in place - after which every release costs less than every release before it.
- One request, matched in 24 hours.
- Build, release pipeline and test coverage for the iOS application, rather than feature development.
- Worked directly with the CEO and the CTO, with no team in between and no permanent role created.
- One month of engagement covering the build setup, the release pipeline and the test coverage behind it.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
A single request for an iOS engineer, scoped to build and release engineering rather than feature work.
Phase: Matching
Shortlisting went to 3 engineers who had built mobile CI/CD pipelines from nothing rather than inherited them, who could pick up an unfamiliar codebase and get it building, and who were senior enough to make configuration decisions a two-founder team would still want later on.
Phase: Interviews
The CEO and the CTO interviewed together, with 1 match confirmed 24 hours after the request opened.
Phase: Engagement
The engagement opened with part-time monthly hours, daily hour tracker, and monthly reporting.
Phase: Support
A 1 month-long engagement with all changes to workload, hour caps, and extra hours requested and approved from the account.
