Indian founder and engineer candidate test a prototype together during a focused work trial.

Hiring Your First Engineer in India

17 min read

The short version

  • Hire your first engineer in India only after you can define the first 90-day product outcome in one page.
  • Pay for ownership and speed, not for a famous company on the CV; a sensible early-stage range is often ₹12-30 lakh fixed CTC, with meaningful equity for the right person.
  • Run a paid, job-relevant work trial and two technical conversations instead of six rounds of algorithm theatre.
  • Close the candidate within 48 hours, document IP and confidentiality properly, and keep at least 12 months of post-hire runway.

To hire your first engineer in India, write a precise 90-day mission, source through founder networks and targeted outbound, test real product work, and close quickly with a credible cash-and-equity offer. Do not begin with a generic “full-stack rockstar” job description. That attracts noise, wastes weeks, and leaves you with an expensive employee who waits for instructions.

A Bengaluru startup once received 280 applications for a senior engineering role through a job portal. Three weeks went into screening. Six interview rounds followed. Two good candidates accepted elsewhere. The eventual hire joined after a 75-day notice period. From role definition to contribution: roughly 14 weeks.

Another startup looking for a similar engineer used a specialist search process. It saw three screened profiles in 10 working days, completed two interviews, made an offer within 48 hours, and had the engineer contributing by week nine.

The second company did not discover a secret pool of engineers. The candidates were probably visible to both companies. The difference was process. One treated hiring as a form to publish. The other treated it as a high-stakes sales process.

Your first engineer is not just another employee. This person will decide how quickly you learn, how much technical debt you create, and whether your next investor sees a product or a demo held together with duct tape. Get this hire wrong and you do not merely lose salary. You lose a quarter of runway.

What your first engineer must actually do

Most founders write a job description before deciding what the engineer must achieve. Reverse that order.

Your first engineer should convert a founder-level product thesis into working software while the requirements are still moving. That means writing code, making architecture choices, talking to users, instrumenting basic analytics, fixing production issues, and telling you when an idea is technically or commercially foolish.

In an early Indian startup, the role usually includes:

  • Building the first usable version of the product.
  • Choosing boring, affordable infrastructure.
  • Shipping weekly rather than polishing a speculative architecture.
  • Handling deployment, monitoring, backups, and security basics.
  • Working directly with customers and support.
  • Explaining trade-offs in plain language to a non-technical founder.

Do not hire someone who wants to be a narrow backend specialist if your product needs one person to own the whole loop. Do not hire a “CTO” who has not shipped recently. Titles are cheap. Shipped products are evidence.

The first hire is not always an engineer

If you have not spoken to enough customers, your next hire may be a contract developer, a technical co-founder, or a product-minded freelancer for six weeks. Hiring a full-time engineer before you know what to build is founder theatre.

You need a full-time first engineer when:

  • You have a repeated customer problem, not just a pitch deck.
  • You can describe the first product workflow clearly.
  • You have enough technical work for at least six months.
  • You can personally make product decisions every day.
  • You have cash for salary, tools, compliance, and a failed hiring attempt.

If you cannot answer “what must this person ship by day 30, 60, and 90?”, you are not ready to hire. You are outsourcing uncertainty.

Hire first engineer India startup: the role brief that works

Use a one-page brief. It should be sharper than your job description and more honest than your investor deck.

Write the mission

Bad: “Build a scalable fintech platform for millions of Indian users.”

Better: “In 90 days, build and launch a merchant onboarding flow for 20 pilot stores, including KYC capture, payment status, admin review, error tracking, and a weekly release process.”

The second version tells a candidate what success looks like. It also exposes your own confusion.

State the constraints

Tell candidates:

  • Current team size and who makes product decisions.
  • Whether the product is in prototype, pilot, or production.
  • Expected office, hybrid, or remote arrangement.
  • Current stack, if one exists.
  • Salary range and equity range.
  • Expected joining date.
  • What you will not build in the next six months.

Strong engineers do not need certainty. They do need an honest map of the uncertainty.

Define the must-haves

Keep this to three or four items. For example:

  • Has shipped and maintained a product used by real customers.
  • Can work across backend, frontend, database, and deployment.
  • Can make sensible trade-offs under incomplete requirements.
  • Can explain past failures without blaming everyone else.

“Five years of experience” is not a must-have. Neither is a particular framework unless the product truly depends on it.

Where to find your first engineer in India

Your first engineer will rarely come from the channel that produces the most applications. Volume is not a hiring advantage. It is a screening bill.

Source What it is good for Main risk How to use it
Founder and investor referrals High-trust, early-stage builders Small pool and social bias Ask 20 founders, operators, and angels for two names each
Targeted outbound Specific experience and domain fit Low response rate Send a personal note tied to the candidate’s shipped work
GitHub, product communities, meetups Builders who may not be actively searching Harder to assess context Review actual projects and ask about decisions
Job portals Reach and junior-to-mid-level volume Large irrelevant funnel Use a sharp screening question and a salary range
Recruiters Speed for hard-to-fill roles Fee and incentive to close quickly Use only with a written scorecard and replacement terms
Developer institutes and colleges Affordable early talent Requires founder coaching Hire for learning speed, not polished interview performance

Start with warm referrals. Send a short note to former colleagues, engineering leaders, founders, angel investors, and operators in your city. Ask for a specific profile, not “any good developers”.

Use targeted outbound next. Find engineers who built something close to your problem. Mention the product, the technical challenge, and why their experience is relevant. Do not send a paragraph about your “stealth startup” and ask for a call.

Recruiters can help when you need speed or access to a narrow skill set. But a 15-20% fee on annual CTC is a serious cost for a seed company. Negotiate a replacement period. Make the recruiter show the candidate’s notice period, current fixed pay, expected pay, location, and reason for moving before you spend founder time.

For broader team planning, see our guide to hiring your first 10 employees in India. Your first engineer needs a different process from your tenth employee, but the same discipline around role clarity applies.

How much should you pay your first engineer in India?

There is no single “startup salary”. There is a market, a candidate, a city, a stage, and a risk discount.

As a working planning range, many early Indian startups may see:

  • Junior engineer with strong evidence of ability: ₹8-15 lakh fixed CTC.
  • Product-minded engineer with roughly 2-5 years of relevant experience: ₹12-25 lakh fixed CTC.
  • Senior founding engineer with ownership and hiring responsibility: ₹20-40 lakh or more, depending on background and funding.

These are planning ranges, not a price list. A strong engineer in Bengaluru may reject ₹18 lakh if a funded startup offers ₹28 lakh and a clearer team. A capable engineer outside the major hubs may value ownership, learning, and flexibility more than a large brand premium. Do not pretend geography has disappeared. It has not.

Use cash and equity for different jobs

Cash pays for the work. Equity pays for risk and long-term ownership. Do not use equity to justify a salary that is plainly below market.

For an early employee, the equity conversation should specify:

  • Instrument: usually ESOPs, not vague “shares”.
  • Number of options and fully diluted percentage.
  • Vesting schedule, commonly four years with a one-year cliff.
  • Exercise price and what happens after resignation.
  • Whether the grant requires board or shareholder approval.
  • Tax treatment and the company’s current cap-table position.

In India, ESOP paperwork and tax outcomes can be confusing. Get a startup lawyer and chartered accountant involved. A verbal promise of “around 1%” is not compensation. It is a future argument.

Do not offer founder-level equity to an employee because you feel guilty about cash. Keep the cap table clean. Investors will inspect it during your seed or Series A round, and a sloppy early grant can become a negotiation problem when you need money most.

Investor rule: Never hire a person whose salary forces you below 12 months of runway after including founder salaries, cloud bills, compliance, and the cost of replacing them.

The interview process: test the work, not the theatre

Your hiring process should take 10-14 days from first conversation to decision. Longer processes do not prove rigour. They prove that you have not agreed on what good looks like.

Round one: founder conversation

Spend 30-45 minutes on motivation, past work, and working style. Ask:

  • What is the most important product you shipped?
  • What broke in production?
  • What did you choose not to build?
  • Tell me about a technical decision you changed your mind about.
  • What would you do in your first two weeks here?

Listen for ownership. “The product team gave us bad requirements” may be true. If every failure belongs to someone else, you have your answer.

Round two: paid work trial

Give a small problem that resembles the job. Pay for it. Keep it to four to eight hours. A good exercise might involve designing an API, fixing a broken flow, reviewing a small codebase, or explaining how they would ship a pilot feature.

Do not ask for free work that becomes part of your product. That is cheap and unethical. You are testing reasoning, communication, code quality, and speed, not extracting a week of development.

Round three: technical and product review

Ask the candidate to walk you through the work. Push on trade-offs:

  • Why this database?
  • What happens when the network fails?
  • How will you know this feature works?
  • What would you change if usage grows ten times?
  • What did you deliberately leave unfinished?

For a first engineer, practical judgement matters more than solving a difficult graph problem on a whiteboard. You need someone who can ship a payment reconciliation flow, not someone who can impress an interviewer with a puzzle.

References

Speak to two former managers or close collaborators. Ask what the person did when a deadline slipped, how they handled ambiguity, and whether you would hire them again. Do not ask only whether they were “good”. References become useful when you ask for specific behaviour.

How to spot the wrong first engineer

Some warning signs are obvious. Others appear attractive because you are desperate.

  • They want a large team before writing code. Your first engineer must tolerate unfinished systems and direct founder feedback.
  • They discuss architecture before understanding the customer. This is often a sign of solution attachment.
  • They have many projects but cannot explain outcomes. Ask who used the product, what failed, and what changed.
  • They demand a title before accepting accountability. “Founding engineer” is not a substitute for ownership.
  • They refuse a practical work sample. You should not hire purely on conversation and pedigree.
  • They are available immediately but vague about why. Check references and employment history.

Do not reject every candidate with a short tenure. Indian engineers move jobs for real reasons: layoffs, bad managers, relocation, family obligations, or a company that stopped building. Look for patterns, not one isolated event.

Closing the offer without losing the candidate

Founders routinely spend two weeks interviewing and then take five days to prepare an offer. That is irrational. The candidate is interviewing you throughout the process, and competing offers do not wait for your board meeting.

Once you decide:

  1. Call the candidate yourself and make the offer verbally.
  2. Send the written offer the same day.
  3. Explain fixed pay, variable pay, joining bonus, ESOPs, notice-period support, and work location clearly.
  4. Tell them what they will own in the first 30 days.
  5. Ask what could stop them from joining.
  6. Speak to them once a week during the notice period.

Do not promise a joining bonus casually. Put repayment terms in writing if the person leaves within the agreed period. Do not disguise variable pay as fixed compensation. Candidates remember the mismatch, and your reputation in a small hiring network travels quickly.

Notice periods are a serious Indian constraint. A candidate who can join in 15 days may be worth more than a slightly stronger candidate joining after 90 days, especially when your product has a real customer deadline. Put an explicit value on time:

Cost of delay = monthly burn during delay + lost customer learning + founder opportunity cost.

If the hire costs ₹2 lakh per month and joining is delayed by two months, the direct salary saving is not ₹4 lakh. You may lose a pilot, delay revenue, and keep the founders doing technical work instead of selling.

Employment paperwork and founder protection

Use a proper employment agreement. Do not download a random template and assume it protects you.

At minimum, cover:

  • Role, reporting line, place of work, and compensation.
  • Probation and notice period.
  • Confidentiality and protection of customer information.
  • Assignment of intellectual property created during employment.
  • Use of open-source software and third-party code.
  • Information security and access controls.
  • Leave, termination, and misconduct provisions.
  • ESOP grant terms in separate, approved documentation.

IP assignment deserves special attention. If the engineer built a side project before joining, identify it. If they use code from a previous employer, stop the process until ownership is clear. A future investor will ask whether your company owns the product it is claiming to own.

Also check statutory obligations based on your entity, state, salary structure, and headcount. Shops and Establishments rules, Professional Tax, Provident Fund, gratuity, sexual-harassment compliance, and state-specific employment rules can apply differently. Your company secretary, payroll provider, or lawyer should confirm the position. Early-stage does not mean exempt from paperwork.

Onboarding the first engineer for output

The first week should not be a parade of introductions. It should end with a small production change or a clear technical plan.

Day one

  • Give access to the repository, product analytics, issue tracker, cloud accounts, and customer notes.
  • Explain the product, target user, current traction, and the next fundraise milestone.
  • Share the 90-day mission and what you will measure.
  • Set up a daily founder-engineer check-in for the first two weeks.

Days two to seven

Ask the engineer to run the product as a user, inspect the codebase, document the top risks, and ship one small improvement. You are testing whether they can create momentum without waiting for a perfect specification.

First 30 days

Agree on measurable outputs. For example:

  • First pilot workflow live with five users.
  • Deployment process documented.
  • Basic error monitoring in place.
  • Critical customer feedback captured in the issue tracker.
  • Technical decisions recorded with reasons.

Do not measure only lines of code, tickets closed, or hours online. Measure customer-visible progress and learning speed.

First 90 days

At day 90, review:

  • What shipped?
  • What did customers use?
  • Which technical risks were reduced?
  • What should the team stop building?
  • Can this engineer now own a meaningful product area?

If the engineer has spent three months rewriting the prototype and has no customer evidence, you may have hired an architect for a product that does not yet exist.

Should your first engineer be a co-founder?

Do not call an employee a co-founder because you cannot afford the salary. Co-founder status means a different relationship, a different equity discussion, and usually a different level of control.

Consider a technical co-founder only if the person:

  • Has conviction about the problem, not just interest in the technology.
  • Will make a multi-year commitment.
  • Can handle product, hiring, fundraising support, and technical execution.
  • Is willing to share difficult decisions and personal financial risk.
  • Has a clear written agreement on vesting, roles, departure, and decision rights.

A senior employee may be the right answer. You retain founder control, pay market compensation, and grant meaningful ESOPs. That is cleaner than creating a fake co-founder arrangement that collapses six months later.

If you are unsure, speak to experienced operators and mentors before changing the cap table. Our guide on finding a startup mentor in India includes a useful filter: ask for help with a specific decision, not general encouragement.

Your seven-day hiring plan

You can improve your process this week without spending on an agency.

  1. Day one: Write the one-page role brief, 90-day mission, salary range, equity range, and joining deadline.
  2. Day two: List 30 people who can refer engineers. Message all of them with the exact profile.
  3. Day three: Identify 20 engineers whose shipped work resembles your product. Send personal outreach.
  4. Day four: Prepare one paid work trial and a scorecard with five criteria scored from one to five.
  5. Day five: Schedule founder conversations. Reject candidates who cannot show relevant shipped work or explain their decisions.
  6. Day six: Run the work trial and technical review. Call references for the top two candidates.
  7. Day seven: Make the offer to the best candidate. Keep the second candidate warm without making false promises.

Your scorecard should include product judgement, coding quality, ownership, communication, and learning speed. Weight product judgement and ownership more heavily than trivia. The first engineer must make decisions when you are unavailable.

Bottom line

Your first engineer is not a coding resource. They are the person who converts your assumptions into evidence. Hire slowly enough to test judgement, but fast enough to avoid losing the candidate. Pay fairly, document the equity, protect your IP, and give them a narrow 90-day mission. The expensive mistake is not paying ₹3 lakh more in annual salary. It is hiring the wrong person and discovering it after your runway has already paid for three months of elegant, useless code.

FAQs

How do I hire my first engineer in India?

Define a 90-day product mission, source through referrals and targeted outbound, run a paid practical work trial, complete two focused interviews and references, then make a written offer within 48 hours. Avoid generic job descriptions and six-round interview processes.

What salary should I offer my first engineer in India?

A rough planning range is ₹12-25 lakh fixed CTC for a product-minded engineer with relevant experience, with junior candidates often lower and senior founding engineers higher. Set the range using role scope, city, notice period, funding, and the candidate’s evidence of shipped work.

How much equity should a first employee get in an Indian startup?

There is no universal percentage. It depends on seniority, salary discount, timing, and responsibility. Document the ESOP number, fully diluted percentage, vesting, cliff, exercise price, approvals, and exit terms. Never rely on a verbal promise of “around 1%”.

Should I hire a CTO or a founding engineer first?

Usually, hire a founding engineer if you need someone to build and ship the product. Hire a CTO only when the role includes technical strategy, team building, security, architecture, and long-term ownership. Do not give a CTO title to an employee who only writes code.

Is a paid coding assignment necessary for the first engineering hire?

Yes, but keep it relevant and short, usually four to eight hours, and pay for it. A practical work trial reveals judgement, communication, and trade-offs better than algorithm puzzles. Never use unpaid candidate work in your product.

How much runway should I have before hiring my first engineer?

Keep at least 12 months of runway after including the new salary, founder compensation, cloud costs, compliance, tools, and a replacement or hiring delay. If the hire leaves you with six months of cash, you are taking a financing risk, not merely making a hiring decision.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top