Who we are looking for
We hire for potential and for what you have built, not for years on a CV. The profile we want:
- You have built things. An internal tool, a test suite, a script people run daily, a side project, a small business. Something that exists because you wanted it to. Send us the link (a portfolio link works too, if that is where your work lives).
- Technical profile. You do not write production features, but you read code, understand a mobile architecture, and work with logs, builds, flags and automation tools without needing a translator.
- Extreme attention to detail. A 2-pixel misalignment, inconsistent copy, an animation that stutters on an old device. Nothing gets past you without analysis.
- Genuinely mobile. You have done QA on mobile apps, not just web. You know what only breaks on a real device: low-end hardware, a bad connection, a denied permission, an upgrade from the previous version.
- You are not after a corporate job. No committees, no asking permission to decide, no three layers of approval. You want full autonomy and to be measured on results.
- Real ambition. You want this to be the place where you grow faster than anywhere you have been, and you know what that costs.
The role
You are Symmetry's QA wall: nothing reaches production without going through you. You will own the quality system across the whole dev team, product and engineering alike. There are no squads here: there is a single dev team, and QA for everything that team ships goes through you. You will design and maintain the QA framework, run testing for every release, manage feature flags and A/B tests in production, run our alpha and beta communities and, above all, reduce the bugs that reach production by improving how the team works in the first place.
This is a technical ownership role, not a management one: you do not run people, you run the system. It is not a manual testing job either, and it is not box-ticking. We want someone who builds the machine that makes quality inevitable: processes, gates, automation, testing programmes and a culture where bugs are caught while the solution is being designed, not in App Store reviews.
What you will do
- Design the dev team's QA framework: from the QA each dev does on their own task to the final gate before code is merged, through alpha, beta and production.
- Work with the whole dev team so every experiment, feature and release goes through the same process, without slowing the team down.
- Be the wall for every release: testing in parallel with development and before publishing to the stores, hotfixes and critical-blocker triage included.
- Manage feature flags and A/B tests in production: each flag's lifecycle, variant coverage, control-group preservation, progressive rollouts and retiring stale flags. No experiment reaches production without QA; no dead flag stays in the code.
- Grow the alpha and beta communities into a reliable early-warning system with structured feedback, not a passive mailing list.
- Go after root cause. Every bug that reaches users gets analysed and turned into a rule, a gate, a test or a process change that prevents that whole family of bugs.
- Put quality in at the start: testability, edge cases and clear acceptance criteria before a line of code is written.
- Publish the state of quality in real time: coverage, production bug trends, time to detection and the state of every release, visible to everyone without having to ask for it.
- Drive mobile automation with Engineering (E2E with Maestro and regression suites) so human judgement goes where it adds most.
- Use AI as a default tool: Claude, Cursor and agents to generate test plans and E2E flows, triage bug reports and analyse crashes.
Requirements
Required
- Obsession with detail. You see what everyone else walks past, and you can explain why it is wrong and how it should be.
- Extraordinary organisation. You carry QA for the whole dev team, several experiments and a weekly release calendar without dropping a thread. Logs and checklists are your habitat and they are always up to date.
- Mobile product judgement. You open an undocumented flow, understand immediately how it should behave and spot where it fails. You know how a first-rate iOS/Android app feels because you have worked on them.
- Technical grounding. You move through builds, logs, flags, automation tools and crash data without needing a translator.
- Quality at the source. You have reduced bugs by changing how a team works, not just by testing more.
- Influence without managing anyone. You align product and engineering around a shared process through technical judgement, not hierarchy. You do not manage people here and you do not need to: the system you build is your authority.
- Real daily AI use. Not "I have tried ChatGPT": AI tools built into how you work.
- Founder mentality. Full autonomy, extreme ownership and decisions made without waiting for permission.
- Direct, fast communication. On a remote team, communication speed is part of the job, especially when something breaks at the worst possible moment.
What counts most
- Flutter. Symmetry is a Flutter app: knowing its quirks (its own rendering, the differences between platforms, how it behaves on low-end devices) saves you months of ramp-up.
- Mobile automation, ideally Maestro. Appium or similar also count. What matters is that you have automated real E2E flows and turned them into quality gates inside CI.
- Alpha and beta programmes. TestFlight, Play Console tracks and progressive rollouts: having run a tester community and turned its feedback into prioritised bugs, not an inbox nobody reads.
- QA for A/B tests: variant coverage, flag states and control-group preservation.
Also counts
- Fitness, health, wellness or lifestyle apps.
- Sentry, Firebase Crashlytics, PostHog or equivalents.
- High-growth startups shipping at speed.
What success looks like here
- A measurable, sustained drop in bugs reaching production, reviewed at every release.
- A process so consistent that no feature, experiment or version skips the same gates.
- Feature flags and A/B fully under control: every variant verified before rollout, zero stale flags in the code.
- An alpha/beta programme that catches critical problems before production and returns structured feedback in hours, not weeks.
- Every production bug with its root cause and its preventive measure.
- Full ownership of the quality system — framework, reporting, flags and testing programmes — within two months.
This role is not for you if…
- You think QA means running test scripts someone else wrote.
- What you actually want is a management job: here you own systems, not a team.
- "It works on my device" strikes you as an acceptable answer.
- Process design bores you and you would rather test more than fix the source.
- You need documentation to understand how a mobile flow should behave.
- Your AI use stops at asking ChatGPT things.
- You need to be told exactly what to test at every step.
- Direct feedback, a high bar or an intense pace make you uncomfortable.
- You are looking for a nine to five with no pressure and no sense of urgency.
Compensation and benefits
- Competitive salary plus a quarterly bonus of 25% to 50% tied to results. We do not fix a number for the role: we adapt to your experience and your current situation.
- Equity: a direct stake in Symmetry's growth.
- 100% remote, no fixed hours and almost no meetings.
- Real impact: the quality bar you set defines the experience of hundreds of thousands of people.
- Accelerated growth: direct coaching from the leadership team and a clear path to more technical scope and more systems under your ownership.
How to apply
Three questions. No cover letter, no 40-field forms.
- A link to something you have built. An app, a script, a side project, a test suite, an internal tool… something you made because you wanted it to exist. Paste the link and tell us in 2-3 lines what it is and what your part in it was. If you have not built anything outside work, tell us what you built inside it. A portfolio link works too, if that is where your work lives.
- What badly done detail, in an app you use every day, drives you up the wall? Tell us which one, why it is wrong and how it should be.
- How do you test a new feature? Where you start, what you try to break first and when you call it ready.
The process
- First conversation (20 min).
- Technical test (72 h): a real Symmetry build. Find what is broken and report it the way you would here. We are looking for judgement, not volume.
- Final interview with the technical team: you defend your findings. Hard questions, fast decision.
You leave every step knowing what happens next.
.png)


