QA & Business Analysis
A lot of what looks like an engineering bug is actually a requirement nobody wrote down. This role sits at that exact seam — between what the client meant and what actually got built.
You'd work through requirements and edge cases before they turn into surprises, and build up test coverage that catches regressions before a client does.
What you'd work on
- Turn ambiguous requirements into something a developer can actually build
- Map edge cases before they become a bug report from a client
- Build and maintain real test coverage, not a checkbox exercise
- Sit close enough to the work to catch drift between spec and build
What we look for
- Ownership. You see a task through to done, not just your slice of it.
- Direct communication. You can explain a decision to a client who isn't technical, without hiding behind jargon.
- Craft. You care about the code nobody's reviewing as much as the code everyone sees.
- Curiosity. You pick up a new stack or protocol when the project actually calls for it.
How we work
No layer of managers between you and the client — you talk to them yourself, the same way founders do. We don't run a fixed hiring pipeline: if this role fits how you think, apply below and tell us what you'd actually bring to it.