Hire in this order: the founders cover product and sales, then a strong generalist engineer, then a designer or a design-minded product person, then a second engineer, and only then specialists such as data, DevOps or growth. Use freelancers for bounded work and salaried people for anything you will be maintaining in two years.
People are the largest line in a startup budget, far above cloud or laptops. This page covers roles, estimated pay by city tier, where to find candidates, a vetting task that works, contracts, and how ESOPs are generally used. The overall playbook covers incorporation and the founder agreement.
The founding team comes before the first hire
Two or three founders usually split roughly into building, selling and operating. If nobody on the team can build, a build partner or early engineer carries the product's quality, and you must decide who owns technical decisions. If nobody can sell, you will lose months waiting for demand to arrive on its own.
Put the split on paper before anyone is hired: equity, vesting with a cliff, roles, what happens if a founder leaves, and who owns the code and the domain. Sign it with a lawyer's help and keep every founder's work in company-owned repositories from day one. An employee who joins a company with an unresolved founder dispute rarely stays.
Roles in the order you probably need them
| Order | Role | What they do early | Signal to hire |
|---|---|---|---|
| 1 | Generalist engineer | Ships the first version end to end: API, database, a web or mobile client, deployments | The founders are writing code instead of talking to users |
| 2 | Designer or product designer | Flows, wireframes, a small component library, user testing | Users drop out in the same screen repeatedly |
| 3 | Second engineer, often mobile or frontend | Takes the app or web client so the first can own the backend | Releases slow because one person is the bottleneck |
| 4 | Customer success or operations | Onboarding, support, collections, pilot tracking | Founders spend half the week on support |
| 5 | Product manager | Prioritisation, specs, analytics | More than six people and conflicting requests |
| 6 | QA or SDET | Regression checks, release gates | Releases break old features regularly |
| 7 | DevOps or data engineer | Reliability, cost, pipelines | Downtime or cloud bills affect customers |
Resist hiring a head of anything early. A senior title with no team and no budget attracts people who want to manage, not to build.
Pay by city tier: ranges to budget against
| Role and experience | Bengaluru, Mumbai, Delhi NCR, Hyderabad, Pune | Tier-2 cities or remote |
|---|---|---|
| Fresher engineer | ₹4–8 lakh a year | ₹3–6 lakh |
| Engineer, 2–4 years | ₹10–24 lakh | ₹7–16 lakh |
| Senior engineer, 5–8 years | ₹25–50 lakh | ₹16–35 lakh |
| Designer, 2–4 years | ₹8–20 lakh | ₹6–13 lakh |
| Customer success or ops executive | ₹3.5–8 lakh | ₹2.5–5 lakh |
| Product manager, 3–6 years | ₹18–40 lakh | ₹12–28 lakh |
Add roughly 15 to 25 percent on top of salary for employer provident fund, insurance, equipment, a payroll tool and the cost of the hire itself. Remote hiring from tier-2 cities often widens the pool, but it works only if your team writes things down and works on shared tools; if you rely on whiteboard conversations, you will pay for the commute anyway.
Salary bands, provident fund and ESIC thresholds and professional tax change by state and year. Confirm the current rules with your CA before you make offers.
Where to find people, and a vetting task that works
- Your network and referrals: the best early hires usually come through people who have seen them ship.
- Open-source contributors and personal projects: a repository with real commits beats a long list of certificates.
- Campus and bootcamps: useful for freshers, but plan for two to three months of mentoring before they are productive.
- Professional networks and job boards: wide reach, heavy screening, so use a short written filter.
- Startup communities and founder groups: posts to WhatsApp or Slack groups of other founders often yield warm referrals.
- Agencies and recruiters: worth it for a senior role only; fees are typically a share of first-year pay and vary by agency.
Use a paid, small, realistic task. For an engineer: build a tiny endpoint plus a screen, or review a short pull request you wrote with planted bugs, three to four hours at most. For a designer: redesign one broken screen from your own app. Pay the candidate for the time, pair with them for thirty minutes afterwards, and watch how they take feedback. A shorter, paid task keeps strong candidates in the process.
Check the signals a task cannot show: how they describe a past failure, whether they ask about users before asking about stack, and whether previous colleagues will speak to their reliability.
Freelancer, contractor or salaried hire
| Work | Better as | Reason |
|---|---|---|
| Landing page, brand identity, one-time illustration | Freelancer | Defined output, no maintenance |
| A payment or notification integration | Freelancer or small agency, with a handover | Clear scope, but you must own the code |
| Core product, data model, authentication | Salaried or an equity-linked founding engineer | Context compounds; this code lives for years |
| Customer support during launch | Part-time or contract | Volume is uncertain |
| Security review before a big customer | Specialist consultant | A periodic need and an outside view helps |
| Growth experiments | Founder first, a hire later | Nobody should run growth who does not know customers yet |
With freelancers: write the scope, acceptance test, the licence and IP transfer into the contract, hold code in a repository you own, and pay milestones against working releases. For classification, whether someone is an employee or an independent contractor depends on facts like control and exclusivity, so take advice rather than labelling people as contractors to avoid provident fund.
ESOPs and equity: the general picture
An employee stock option plan reserves a pool of shares so you can offer employees the right to buy shares at a fixed price after a vesting period. A common arrangement is four-year vesting with a one-year cliff, and a pool set aside before you raise money, but pool size, strike price and terms are negotiated and are not fixed by any rule I can quote.
- Write down the plan: the board and shareholders approve the plan; each grant is documented with a vesting schedule, exercise price and what happens on leaving.
- Be honest about value: options in an early company can end up worth little. Never describe them as guaranteed money or give a valuation you cannot support.
- Tax treatment: options are taxed at points such as exercise and sale, and DPIIT-recognised startups have had special treatment; the rules change, so check current treatment with a CA before you tell an employee anything.
- Companies Act rules: rules on who can receive options, such as promoters and large shareholders, and on recognised startups differ; confirm the current position on the official MCA and Startup India sites and with a company secretary.
I have not verified the current ESOP, Companies Act or tax rules against official sources. This is general information, not legal or tax advice.
Offers, notice periods and keeping people
Write offers with salary split, probation, notice period, IP assignment, confidentiality and a clear job title. Notice periods of one to three months are common in Indian tech, so a hire you make today may start a quarter later; plan for the gap and keep a backup candidate warm.
Keep people by giving them real ownership of a customer-visible piece of the product, a fortnightly one-to-one, and honest numbers about runway. Early engineers leave when they stop learning, when pay lags the market by a lot, or when founders reverse decisions every week. For what specific products demand from a team, see the fintech and marketplace pages.
Before you hire anyone
More on starting a tech startup
- Start hereThe full playbook →Models, licences, startup costs and the steps to your first customer.
- Go deeperWhat to buy →Laptops, test phones, cloud and tool seats for a software startup, and what to leave for later.
- Go deeperGetting customers →B2B and consumer routes to first users, launch channels, pilots, pricing and retention.
- Go deeperFinding suppliers →How to choose dev shops, cloud, payments, KYC, messaging APIs, CA and lawyer, and what to ask each.
Questions people ask
Who should a tech startup hire first?
Usually a strong generalist engineer who can ship the whole first version, if the founders cannot build it themselves. After that, add a designer or a design-minded product person, then a second engineer. Delay managers, specialists and heads of function until you have users and a clear bottleneck. Customer success often matters earlier than people expect.
How much should I pay an early engineer in India?
As a rough estimate, a 2 to 4 year engineer in a metro may cost around ₹10 to 24 lakh a year, and a senior engineer ₹25 to 50 lakh, with lower ranges in tier-2 cities or remote roles. Budget 15 to 25 percent more for benefits and tools. These are planning ranges, so check current postings for your city and skills.
Freelancers or full-time employees for an MVP?
Use freelancers or an agency for bounded work such as design, a landing page or an integration, and keep the core product with people you employ. If you do use outside builders for the MVP, insist on code in your repository, written IP assignment, weekly demos and a handover with documentation so you are not locked in.
How do ESOPs work for a startup in India?
A company reserves a pool of shares and grants employees the right to buy them at a set price after vesting, commonly over four years with a one-year cliff. Grants are documented and approved by the board and shareholders. Tax and eligibility rules, especially for recognised startups, change, so confirm them with a CA or company secretary.
Do I need a CTO if I am not technical?
You need someone who owns technical decisions and quality, whether that is a co-founder, an early engineer or a trusted advisor reviewing your build partner. A full CTO title is not necessary on day one, but equity, vesting and code ownership must be clear. Without someone accountable, build costs and technical debt tend to grow unseen.
