What an engineering manager does at a startup

At a startup, an engineering manager is a player-coach. You still write code (often 30 to 60 percent of your week early on), you run hiring almost end to end, and you own whether the team ships. The title means something different from the same title at Google or Meta, where a manager may run 8 to 15 reports, write zero production code, and spend the day in coordination. The smaller the company, the more the EM job is doing the work and clearing the path, and the less it is pure people management.

This post is about that specific job: the day-to-day of an EM at a company under roughly 50 engineers, how it differs from big tech, what the comp looks like, and who actually thrives in it. If you are deciding between the IC track and management, start with IC vs management track for engineers and come back here for the startup-specific version.

Do engineering managers still code at a startup?

Yes, almost always, and the share scales inversely with team size. If you are the first EM at a 10-person company, you are likely committing real features. By the time the org is 40 engineers across three teams, your hands-on time drops toward zero and your job becomes mostly people and delivery. The mistake new startup EMs make is picking up critical-path work, then becoming a bottleneck the week three other things catch fire.

A useful rule: take the work that is important but not on the critical path. Bug fixes, internal tooling, the gnarly migration nobody wants, code review, pairing with a struggling engineer. That keeps your hands in the codebase (so your technical judgment stays current and your team respects it) without making the release depend on you. The moment you own a launch-blocking feature, your management duties will slip, or the feature will, usually both.

What does an engineering manager actually do all week?

There is no single answer, but at a startup the week clusters into five buckets. The proportions move with headcount, but the buckets are stable.

• 1:1s. Weekly 30-minute conversations with each report. This is the core of the job, not a chore to fit in. With 5 reports that is 2.5 hours of meetings plus prep and follow-up.
• Hiring. Sourcing, screening, running loops, and closing. At a fast-growing seed or Series A company this can eat 30 to 40 percent of the week. See how to run a fast engineering interview loop.
• Delivery. Knowing what is in flight, what is stuck, and what ships this week. Unblocking, not assigning. Cutting scope when the date is real.
• Coding and review. The hands-on share, weighted toward off-critical-path work and reviewing others' pull requests.
• Glue. Talking to the founders, product, sometimes the first customers. Translating company priorities into team priorities and back.

On a calm week at a 6-person team you might spend 40 percent coding, 20 percent in 1:1s and people work, 20 percent hiring, 20 percent glue and delivery. During a hiring push for two senior roles, coding can drop to 10 percent for a month. That swing is normal and you should plan for it rather than resent it.

How many engineers does a startup EM manage?

Span of control at a startup is usually 4 to 8 direct reports. Below 4, the company often does not need a dedicated manager yet; the most senior engineer or a founder absorbs it. Above 8, the quality of 1:1s and feedback degrades fast unless you stop coding entirely, which most early companies do not want. The sweet spot for a hands-on EM is 5 to 6: enough to justify the role, few enough that you can still touch the code and know everyone's work in detail.

How is the startup EM job different from big tech?

The titles match. The jobs do not. At big tech the manager role is more specialized, more insulated from the code, and more about navigating a large organization. At a startup the role is wider and flatter, with fewer people to hand things to and a much shorter line to the people who set the strategy.

The biggest practical difference is support. At a startup there is no program manager to chase status, no dedicated sourcer filling your pipeline, no internal mobility team. You do those things, or they do not happen. If you are weighing the move in general, switching from big tech to a startup covers the broader trade, and this is the management-track slice of it.

What does a startup engineering manager get paid?

In San Francisco and New York, a startup EM at a funded seed to Series B company typically lands in the $190,000 to $260,000 base range, with equity that scales down by stage and up by how early and senior you are (illustrative, not advice). At seed, expect a lower base and a larger equity grant, often 0.5 to 1.5 percent for an EM who is also a founding-level technical leader. By Series B the base rises and the grant compresses toward 0.15 to 0.5 percent (illustrative, not advice).

Management does not reliably pay more than a strong senior or staff IC at a startup, and sometimes pays the same. The premium, when it exists, is small. Do not move into management for the money. For the IC comparison, see senior software engineer salary in SF and NYC for 2026, and for how the equity side actually pays out (or does not) read how startup equity makes money or not.

Who thrives as a startup engineering manager?

The people who do well share a few traits. They are comfortable being good at several things rather than the best at one. They get satisfaction from a teammate shipping something hard, not only from shipping it themselves. They can hold ambiguity without freezing: the spec is thin, the priorities shift, and they still get the team moving. And they like hiring, because at a startup hiring is not a side task, it is half the job in a growth year.

The people who struggle tend to miss the coding too much, or expect the clean reporting lines and support functions of a larger company. If your favorite part of the week is a long uninterrupted block of deep work, management at a small company will feel like a series of interruptions, because it is. That is not a failing. It is a sign the staff IC track might fit you better. How to become a staff engineer is the other path up.

At a startup the EM job is doing the work and clearing the path. The smaller the company, the more it is doing, and the less it is pure management.

Should you take a first-EM role at a startup?

Ask three questions before you say yes. First, why do they need a manager now: is the team genuinely too big for a founder or lead to run, or is the title a retention patch? Second, will you still code, and does that match what you want? Third, who do you report to, and do they understand engineering well enough to support you? A founder who has never managed engineers will lean on you heavily, which is either a great opportunity or a trap depending on how much air cover you get.

Timing matters too. The strongest startup EM roles open right after a raise, when the company has runway and a real mandate to grow the team you would lead. You can watch which companies just closed a round on our recent raises page, and why funding recency is the best hiring signal explains why that window is the one to target.