A startup needs a manager when improving other people's work is a substantial, ongoing part of the job. It needs an individual contributor when the immediate gap is work someone must personally deliver. Write the weekly responsibilities before selecting the title.
This decision matters when a founder asks for someone “senior enough to take ownership.” Ownership might mean implementing a system, setting direction, coaching a team, or making cross-functional decisions. Those are different assignments.
Map the work that is waiting
List the tasks currently falling to the founder. Beside each task, write whether the new hire would execute it, coordinate it, or make the final decision.
| Work waiting to be done | Likely mandate | Evidence to seek |
|---|---|---|
| Build and maintain a missing capability | Individual contribution | Personally delivered comparable work |
| Help an existing team plan and improve | People management | Coaching, prioritization, and team development |
| Resolve decisions across teams | Functional leadership | Decision rights and cross-functional judgment |
| Establish a small function while delivering | Explicit hybrid role | Both execution and building a repeatable process |
Use the table to describe the role, not to generate an automatic hiring decision. A technical leader may contribute directly, but the responsibilities must fit within a realistic working week.
Test whether a management role exists
Ask who the person would manage, what decisions that team needs, and what support already exists. If the answers depend on future hiring that has not been approved, describe that future as a possibility rather than a current mandate.
A fictional example: a software team needs a customer integration shipped, but its job description asks for a department head. There is no team to lead yet. A senior engineer with clear delivery authority may address the immediate problem more directly.
The opposite mistake is also possible. Hiring another strong contributor will not resolve unclear priorities across an existing team if nobody owns those priorities.
Make a hybrid role understandable
For a hybrid role, agree which responsibility wins when delivery and management compete. Name the founder who will resolve conflicts. Explain what would trigger a change in the balance, such as an approved team expansion.
Do not promise a management promotion merely to make an execution role attractive. Discuss the work someone would join to do today.
Use the decision in interviews
Ask candidates to describe a period when they divided time between direct work and supporting others. What did they stop doing? Which responsibilities did they delegate? What became harder as the team changed?
Evaluate that evidence against your actual assignment. A preference for management is not a weakness; it may indicate that the current role is unsuitable.
Finish with a written mandate: “This person owns ___, directly delivers ___, supports ___, and escalates ___.” The hiring brief template gives you a place to record it.
For senior technical searches, use the hands-on engineering leadership guide to define technical involvement without turning every responsibility into a full-time job.