Joining a 7-Person Engineering Team: What Nobody Tells You in the Interview

We've helped build founding tech teams for companies like CRED, Zepto, Teleparty, and a dozen others. I've watched this process play out from both sides - placing the candidates and hearing from them 6–12 months later. Here's what nobody tells you in the interview.

What the job actually looks like

Forget your title. At a company with fewer than 10 engineers, you're not a "Senior Backend Engineer." You're the person who does whatever needs doing. In week one, you might set up CI/CD pipelines. In week two, you're debugging a payment integration. In week three, you're interviewing the next hire. In week four, you're on a call with a customer.

"I learned more about building software in my first year here than in 4 years at my previous company. I also aged about 5 years."

The upsides

Outsized impact

At a 10,000-person company, your contribution is a rounding error. At a 7-person company, your code is running in production within days and directly affecting revenue.

Real skills

Not "I optimised a component in a larger system" skills. "I architected the entire backend from scratch, chose the database, designed the API, set up monitoring, and was on-call when it broke" skills.

Equity that could matter

Early employees typically get 0.1–1% of the company. If the company reaches a $100M valuation, that's $100K–$1M. If it reaches $1B, do the math.

Relationships that last a career

The bonds formed amongst the founding members, in the chaos of building something from nothing, are different from any other professional relationship. Ten years from now, these are the people you'll call when you need a co-founder, a reference, or a job.

The downsides

The salary will be lower

If the salary gap is more than 15–20% below your market rate, think carefully about whether you can sustain that for 2–3 years.

The processes don't exist yet

No sprint planning. No code review standards. No incident response playbook. No HR for when you have a problem with a co-worker. You'll be building these processes from scratch.

The founders' personality is the culture

At a 7-person company, culture is whatever the founders are like on a Tuesday morning. If they're anxious, the company feels anxious. You're signing up for an intimate working relationship with them.

It might not work out

Most startups fail. If the company shuts down in 18 months, your equity is worthless, and your resume shows a stint at a company nobody's heard of.

How to evaluate the opportunity

1. The founders

Have they built something before? More importantly, are they people you'd want to work for 12 hours a day when things are going badly? Because things will go badly. Meet them in person. Have dinner. Watch how they treat the waitstaff. Ask what went wrong at their last company.

2. The funding

At minimum, you want 12–18 months of runway. A company with 6 months of runway is asking you to take a risk they can't cover.

3. The problem

Do you believe in what they're building? Not because it's "cool," but because you've thought about the market and the customers, and it makes sense. Genuine belief in the mission will carry you through the hard months.

Practical advice for the first 90 days

• Set up the basics immediately - version control, CI/CD, staging environment, monitoring, logging

• Document as you build - the engineer who joins in 6 months won't know why you made that decision

• Push back on scope - founders always want more features faster; be honest about what's possible

• Take care of yourself - sustainable pace beats heroic sprints