You are hiring your third engineer and the candidate asks what title they will get. Your first engineer is "Software Engineer." Your second negotiated "Senior Software Engineer." The new candidate has an offer elsewhere as "Staff Engineer" and wants the same. You have never thought about levels, and suddenly titles are a bargaining chip.
The short answer: keep titles few, modest and tied to scope, and write down what each one means before you hand out the next one. At under ten engineers you need at most three engineering titles. Inflated titles cost almost nothing today and a lot later, when you hire someone genuinely more senior and have nowhere to put them, or when an early engineer with a big title cannot do the job the title now implies.
Why titles matter more than founders expect
Titles look free. They cost no cash, no equity, and they help close candidates. That is exactly why they inflate.
But titles carry three costs.
They set expectations you have to meet later. If your second engineer is "Head of Engineering" at four people, what happens at twenty, when the company needs an actual engineering leader? Either they get the job by default, possibly before they are ready, or you hire above them and have a painful conversation. Our post on whether your founding engineer should get the CTO title covers the most extreme version of this.
They signal to the market. Experienced candidates and investors read titles against scope. A "Staff Engineer" at a ten-person startup with two years of experience tells a good candidate your levelling is loose. Large-company levels do not map cleanly to startup titles anyway, which is why serious hiring managers compare scope and compensation, not the title on the resume.
They become the reference point for pay. Once titles exist, people compare pay within the same title. If titles were handed out by negotiation, pay will be inconsistent within them, and someone will notice.
A simple structure that holds up to about 15 engineers
Three titles are enough for most early teams.
Software Engineer. Delivers well-defined work independently once the direction is clear. Needs review and guidance on larger design decisions.
Senior Software Engineer. Owns an area of the system end to end. Makes sound design decisions without being asked, reviews others' work, and raises problems before they become incidents. Most of your first few hires should be at this level if you can afford it.
Lead Engineer or Staff Engineer. Sets technical direction across areas, mentors others, and makes the decisions that are hard to reverse. At an early startup there are usually zero or one of these, and often the role belongs to a technical founder or a fractional CTO rather than a hire.
Write one paragraph for each, describing scope and expectations, not years of experience. Share it with the team. When someone asks for a title change, the conversation becomes "here is what the next level means; here is the evidence we would look for" rather than a negotiation.
Titles worth avoiding early
"Head of", "Director", "VP". These describe management of teams that do not exist yet. Reserve them until there is a team to lead, and even then, consider whether the person will still fit the role at three times the size.
"CTO" for an early hire. It is the single most expensive title to give away early. See the difference between a CTO and a VP of Engineering for why the jobs diverge as you grow.
"Principal". At most startups it means nothing specific and creates an extra rung nobody can define.
"Founding Engineer". This one is fine, and often better than an inflated level, because it honours the early risk without implying a management scope. It describes when they joined, not their seniority.
How to handle a candidate who wants a bigger title
When a candidate asks for a title above what the role is, separate the title from what they actually want. Often it is pay, equity, or reassurance that they will grow. Address those directly: a stronger equity grant, a clear path to the next level with written criteria, or a review at six months.
If a competing offer has a bigger title, ask about the scope behind it. A "Staff Engineer" at a company with three engineers is often doing the same work as a senior engineer at yours. Say so honestly. Strong candidates usually respect a clear levelling system more than a title that will not mean anything in two years.
If you still want them and the title is the deal-breaker, give it with eyes open and write down what it means, so the title stays tied to scope.
Fixing titles you already inflated
If you have already handed out big titles, do not strip them abruptly. That reads as a demotion and damages trust. Instead, write the level definitions, map each person against them privately, and fix it going forward: new hires get the right titles, and future promotions use the written criteria. When you eventually hire above someone with an inflated title, have the conversation early and frame it around the company's growth, not their failure.
Where outside help fits
Levelling sounds like an HR task, but it needs technical judgment: what does "owns an area end to end" mean for your system, and who on your team actually does it? A fractional CTO can write the level definitions, map your current team, and sit in on the next hiring decisions. See pricing, or book a call if you are about to make an offer.
Frequently asked questions
How many engineering titles does an early startup need?
Usually three: Software Engineer, Senior Software Engineer, and Lead or Staff Engineer. Add more only when you have managers and enough people that the differences matter.
Should my first engineer be called Senior?
If they genuinely own an area end to end and make sound design decisions independently, yes. If the title is mainly a recruiting sweetener, use "Founding Engineer" instead and keep the level honest.
Is it bad to give a startup engineer a Head of Engineering title?
It is risky early. It implies managing a team that does not yet exist and makes it awkward to hire an experienced leader above them later. Reserve it for when the role really includes leading a team.
How do startup titles compare with big tech levels?
Loosely at best. A startup senior engineer may carry more scope than a big-company senior engineer in some areas and less in others. Compare scope and compensation, not titles.