Most pre-seed companies in our portfolio spend more on Engineer #1 in the first year than they spend on any other line item except compute. The companies that get this hire right typically reach a fundable seed; the companies that get it wrong almost always either bridge or shut down. The reason it matters more than any subsequent hire is structural: Engineer #1 sets the velocity, the standard, and — almost always — the culture of the eight engineers that follow.
Who Engineer #1 actually is
There is a recurring failure mode in pre-seed hiring: the founder hires the engineer they would have wanted to work with at their previous company. That is the wrong frame. The right Engineer #1 is the engineer who can do four very specific things in your specific company. The job description below is the one we hand to founders, with edits.
What Engineer #1 actually spends their time on (months 1–6)
- 38%
Customer-facing shipping
Features driven directly by design-partner asks.
- 22%
Production reliability
Observability, on-call, fixing what breaks.
- 14%
Recruiting + interviewing
Sourcing, screening, closing the next 2–3 hires.
- 16%
Architecture + foundations
The 'real engineering' that founders over-estimate.
- 10%
Internal tooling + DX
Making the rest of the team faster.
Composite from 12 portfolio companies. Note: 'green-field building' is much smaller than founders assume going in.
If your job description focuses entirely on the 16% — distributed systems, architectural rigour, foundational design — you will hire well for the wrong role. The other 84% is what most early-engineer time actually looks like, and the engineer who is excited about all of it is the one you want.
The four things they have to do well
- Ship to customers, weekly, on partial information. The engineer who needs full requirements is not your Engineer #1.
- Hold a production system on their shoulders for the first six months. They will be on-call. They will fix things at 2am. The engineer who treats this as beneath them is not your Engineer #1.
- Be present in customer conversations. Not as an attendee — as an active listener and follow-up source. The engineer who 'doesn't do customer stuff' is not your Engineer #1.
- Recruit the next two engineers. They will source, interview, close, and onboard. The engineer who hates hiring is not your Engineer #1.
What to pay
The pre-seed-to-seed range for Engineer #1 in India in 2026 is wider than at any prior stage. We see a real distribution from ₹40 L cash + 1% equity at the low end to ₹120 L cash + 2.5% equity at the high end. The variance is mostly driven by repatriated senior engineers (who command global comp) versus India-trained mid-level engineers (who do not).
Engineer #1 total comp — India, pre-seed, 2026
India-trained mid-level
Typical 0.5–1.2% equity
₹40 · ₹70
India-trained senior
Typical 1.0–2.0% equity
₹70 · ₹120
Repatriated / ex-FAANG
Typical 1.5–3.0% equity
₹110 · ₹180
₹L total comp (yr 1)
Cash + ESOP at face value. Excludes joining bonus. Range reflects market across India-trained, returning-senior, and ex-FAANG profiles.
Which slice you pick is a strategy decision, not a budget decision. If your company will live or die on technical depth in year one (FM training, novel infrastructure, latency-bound systems), the senior/repat slice is correct and the cost is justified. If your company will live or die on velocity and customer iteration in year one (most application-layer companies), the India-trained mid-to-senior slice is correct and the additional senior comp is over-spend.
The interview loop we recommend
Three rounds. Each round is designed to test one of the four things above. The loop is short by Silicon-Valley standards because the candidates worth hiring are also being courted by global labs and Indian unicorns; a six-round process loses you the candidates you most want.
- Round 1 (90 min, founder-led): Walk-through of the product, the customer, the company doc. Then 30 minutes on a real technical decision you are currently wrestling with. You are testing: do they engage with the actual problem or perform on a generic one?
- Round 2 (120 min, take-home in advance + 60-min live review): A small, real codebase task — extending an actual feature, not a leetcode pattern. You are testing: do they ship pragmatic code or theatrical code?
- Round 3 (90 min, customer + ops): Bring them into a 30-min live customer conversation, then debrief. Then 30 minutes on their last on-call story. You are testing: do they meet the four-things bar?
How to close
Closing Engineer #1 is mostly about three things: a clean cap-table conversation, a credible 18-month plan they have read, and a founder who picks up the phone on Saturday. We have lost candidates to other companies for many reasons; the reasons we have lost them to founders we respect are always one of those three.
“The right Engineer #1 is the engineer who, on their first day, behaves like a founder who took less equity. The wrong Engineer #1 is the engineer who, on their first day, behaves like an employee who took more cash.”
What we do as a fund
On average, each Pratyaya partner has 80–120 senior engineers in their personal network who would take a call about a portfolio company. For every founder we back, we typically source 4–7 first-look candidates for Engineer #1 in their first 60 days, and we sit in on at least the first round of each. The hire is too important to leave to the founder alone. It is also too important to take out of the founder's hands. We are the second voice in the room.