Member of Technical Staff (founding team)

faff is an early-stage, Seed-funded company based in Bengaluru. The founding team is still being assembled, and the engineering culture is being written from scratch. Details on the product, founders, and what they are building were not available at the time of this brief; the HM should add this before publishing.

faff is hiring one of its first engineers. The scope of this seat is broad by design: the person who takes it will work directly with the founding team, make early architecture calls, and set the technical bar the company builds on. The first-90-day priorities, the stack, and the specific surface this engineer owns are to be confirmed; the HM should complete the intake call before publishing this brief.

The founding codebase. You are among the first engineers in; what you build and how you build it sets the standard.
Early architecture decisions. The calls made now will shape the system for years; you will make them alongside the founders.
Engineering culture from zero. Hiring bar, code review norms, deployment practices: you help write them before they are written.
The product surface you own. Specific ownership to be confirmed in the full intake call.
The first-90-day technical roadmap. Priorities, sequencing, and the definition of done for the founding sprint.

You have shipped production software end to end. You have taken something from idea to deployed, and you own what happened after it shipped.
You are comfortable with ambiguity at the founding stage. No spec, no playbook, no senior engineer to escalate to: you have been here before and you did not freeze.
You have strong opinions on how to build well. You can articulate why you made the technical choices you made, and you have been wrong before and updated.
You move fast without leaving a mess. Speed and quality are not a trade-off you accept; you have held both at once.
You want to be a technical co-founder in everything but the title. Equity, ownership, and the long arc of the company matter to you as much as the immediate problem.

Build with conviction. Make the call, own the outcome, and update when the evidence changes.
Move fast and leave the codebase better than you found it. Velocity is not an excuse for debt you cannot pay back.
Default to doing. Write the code before you write the doc about the code.
Operate with full context. Everyone knows what is being built, why, and what is at stake.
Hold a high bar on craft. Good enough is a starting point, not a finish line.

Seed-funded, founding equity, and a technical seat that shapes the company from day one. The equity is real and the ownership is total.