The Leadership Roles That Keep You Technical

I put a sentence at the top of a job posting last month that wasn’t about the job at all.

It was about a fear. Some leadership roles take you further and further from the technical work. This one doesn’t.

I wrote it because that fear is the most common reason a strong engineer turns down a management conversation. Not money. Not title. The work.

The Sentence I Put in the Posting on Purpose

The role was Manager, Design and Drafting, with a Calgary manufacturer whose department was going through a period of change. They needed someone who could set drafting standards and hold a team to them, and they needed that person to give technical direction the team would take seriously.

Those two needs pull in opposite directions if you scope the job carelessly. Hire a pure people manager and the standards get set by committee. Hire a pure technical expert and nobody develops.

So I put the reassurance in the posting itself, before the responsibilities list, because I knew who I wanted to reach. Some leadership roles take you further and further from the technical work. This one doesn’t.

The people best suited to that role were the ones most likely to assume it would take the work away from them.

It did what I hoped. Two of the strongest applicants mentioned that line unprompted when we first spoke, which almost never happens with anything in a posting.

Why Good Technical People Say No to Management

I have had this conversation dozens of times, and it goes almost the same way every time.

Someone in year ten or twelve of a technical career gets tapped for a leadership role. They’re pleased. Then they start doing the arithmetic and they get quiet.

The fear is specific, and it isn’t vanity. Two years of meetings and budget cycles and your hands-on skills are stale. The software has moved and the codes have changed.

And if the management role doesn’t work out, or the company restructures, you’ve lost the thing that made you employable in the first place. I’ve placed people who took that risk and had to rebuild the technical side afterwards. It takes longer than anyone expects, and it is a demoralising two years.

That fear is rational. It’s also built on one version of management, the version where leadership means distance from the work, and plenty of people have watched that version happen to someone they respected.

None of which means technical depth alone carries a career forever. It doesn’t, and I’ve written about why technical expertise alone isn’t enough. The question is what you add to the depth, and management is only one of the answers.

What a Player-Coach Role Actually Looks Like

The Design and Drafting role is a good example because the balance is written into the job rather than promised in an interview.

The person leads and develops the team. They also stay close enough to the output to be credible about it, which in practice means:

• Still working in SolidWorks and Inventor. Not supervising people who use them.
• Still able to look at a model and know it will be a problem in fabrication. The kind of judgement that goes stale fast if you stop using it.
• Still understanding how a drawing lands on the shop floor, and what happens when the tolerance stack is wrong.

Day to day, the split usually settles somewhere around two-thirds leadership and one-third hands-on once the person is established.

The hands-on third is not filler. It’s the reviews, the difficult drawings, the standards work, the problems that come back from the floor.

The tell that a posting means it is that it describes technical deliverables and not only team outcomes. If everything in the responsibilities list is about headcount, performance reviews and cross-functional alignment, the technical half is decoration no matter what the intro paragraph says.

The Other Fork: Technical Authority Without a Team

The second option gets less attention and suits more people than it reaches.

Both Senior Electrical Engineer searches I ran this month were shaped this way. Ten or more years of experience, P.Eng registered with APEGA, working across high, medium and low-voltage systems.

Modelling in ETAP or SKM. Reliability work sitting alongside project execution. The person becomes the site authority on electrical systems, which is a heavier job than the title suggests.

No direct reports. Considerable influence. When that person says a design won’t hold up, the project changes.

Seniority in these roles comes from depth and authority rather than headcount, which is a real career track and not a consolation prize for people who didn’t want to manage. Heavy industry supports it better than most sectors, because the assets are complicated enough that genuine expertise is scarce and expensive to replace.

It belongs to the same family as the other roles that hold a project together without appearing on the org chart in the way you’d expect, which I’ve written about in the roles that quietly make projects work.

Where the Player-Coach Model Breaks

I’d be doing you a disservice if I sold the hybrid role without saying how it fails, because it fails in a predictable way.

The first failure is time. Nobody protects either half. The leadership work fills the calendar because it’s scheduled and other people are waiting on it, so the technical work moves to evenings. Six months in, the person is doing two jobs badly and resenting both.

The second failure is worse and quieter. The technical half makes the manager the bottleneck. Every drawing waits on their review, the team stops developing judgement because judgement lives in one person, and the role that was supposed to build capability has concentrated it instead.

What has to be true for it to work is unglamorous:

• A team small enough to lead properly, usually under eight.
• A senior designer or deputy who can carry reviews when the manager is unavailable.
• An employer who understands the split well enough to defend it when a deadline comes.

Ask about all three before you accept one. The most useful version of the question is direct: who covers my reviews in a busy week, and what gets dropped when the schedule tightens?

An employer who has thought about the role will have an answer ready. One who hasn’t will tell you it’ll work itself out, which is the answer that should worry you.

Those questions sit alongside the wider ones worth asking about any employer in how to know if a company is worth joining.

What Employers Get Wrong When They Post These Roles

Four errors, and I see all four regularly.

• Writing a people-leadership posting for a hybrid job. The responsibilities list is all team outcomes, so the applicants are administrators, and then the hiring manager wonders why nobody in the pool can read a drawing.
• Requiring a P.Eng out of habit. On a design and drafting leadership role, hands-on depth is often what the job needs, and the designation gets listed because it was on the last posting. That single line removes a large share of the strongest candidates before they read the second paragraph.
• Not saying which half dominates. A posting that’s vague about the balance loses both audiences at once. The technical people assume it’s a management job, the managers assume it’s too hands-on, and the applications come from whoever read it least carefully.
• Attaching the wrong title to the shape of the work. A Manager title on what is genuinely a senior individual contributor role, or a Senior Engineer title on a job with six direct reports and a budget.

That last one has a full treatment already in why clear job titles attract top talent, and it applies here with force.

How to Tell Which One You Actually Want

I’m not going to tell you which fork to take. I will give you the question I ask, because it works better than the ones people usually ask themselves.

Think about the last month of work. What was the best part of it? Solving something difficult yourself, or watching someone on your team solve something difficult because of how you’d set them up?

Most people answer that quickly and then apologise for the answer. There’s nothing to apologise for.

Both answers describe a legitimate senior career, and neither one is further up the ladder than the other.

The fork usually arrives somewhere between year eight and year fifteen, which is also when people have the least time to think about it. Choosing wrong is recoverable, and it’s expensive, mostly in the two or three years it takes to correct.

That timing sits alongside the wider question of what seniority looks like later on, which I’ve covered in what senior careers look like after 15+ years.

If You’re at the Fork

If you’re weighing a first leadership role and you can’t tell whether it will take you away from the work, that’s worth talking through with someone who recruits both shapes of role and has no stake in which one you pick. I’d be happy to have that conversation confidentially, whether or not there’s a live role attached to it.

And if you’re scoping a hybrid role right now, decide which half dominates before the posting goes out. That decision is much harder to make afterwards, with a shortlist in front of you and a team waiting.

Technical Leadership Roles FAQs