Some seats fit in a sentence. “Senior back-end engineer, payments.” Everyone knows who you mean, and so does every job board.
Then there’s yours. You need a staff engineer who also manages two people. Or an AI engineer who’s half platform engineer, because somebody has to keep the models fed and the pipelines standing. You’ve rewritten the job description three times, and it still reads like two job descriptions stapled together.
Good. Bring it to me. I like these searches.
Why are these seats so hard to fill?
Because almost everything in hiring is built for boxes. Job boards sort by title. Filters match keywords. Applicants match themselves to half of your description and hope you skim the other half.
Meanwhile, the people who can truly do both jobs rarely call themselves either one. A staff engineer who’s been quietly running a small team for two years may still say “senior engineer” on her profile. The engineer who built a whole AI platform may describe himself as “back end.” They aren’t searching for your seat, and your seat isn’t finding them.
How do I describe a seat that’s two jobs?
Start with the work, not the titles. Write down what this person does in a normal week, honestly. How much of it is code? How much is people? Who do they answer to, and who answers to them?
Then decide which half matters more. Most two-in-one seats lean one way, even if nobody has said so out loud. If your staff engineer who manages would rather give up the managing than the engineering, you’re looking for an engineer who’s good with people, not a manager who still codes. Those are different people, and each is rare enough without mixing them up.
Be specific about the split, too. “About a third of your week with your two engineers” is something a person can picture. “Leadership responsibilities as needed” isn’t.
What should I ask for, and what should I let go?
Ask for the one or two things this seat can’t do without on day one. Let go of everything a strong engineer would pick up in a month. In a seat like this, every extra must-have turns a small pool into a puddle. I wrote more about that in my note on job posts.
And name the trade-off plainly. If the AI engineer will spend half the week on platform work, say so. The right person will be glad to hear it. The wrong one will bow out early, which saves you both an afternoon.
Who’s actually out there?
Fewer people than for a seat that fits a box. That’s fine. You only need one.
They’re usually happy where they are, doing a version of this job that nobody bothered to name. They don’t apply, because no job post has ever described what they do. They answer when someone who understands both halves of the seat reaches out and explains why it fits.
That’s the part I enjoy. I came out of a software agency and have spent twenty-five years inside engineering teams, so a seat with two halves doesn’t scare me. Tell me about yours, and I can usually picture the person, and often I know who to call. You’ll meet a small group of three to five, each with a custom-written vignette on which half they’re strongest in, and why I think they’d grow into the other.
How do I interview for it?
Interview both halves, with the right people for each. Let your engineers talk shop. Let someone who has managed people talk about managing. When one person judges both halves alone, the seat tends to go to whoever’s best at that person’s half.
And say early how the split might change. Seats like these grow. The staff engineer who manages two people today might manage six next year, or hand them off to a new manager. Say what you expect, so nobody’s surprised later.
The short version
- Describe the week, not the titles.
- Decide which half matters more, and say so.
- Ask for what day one needs, and let the rest go.
- The right people rarely apply, because no post describes them.
- Interview each half with the people who know it.
Weird roles aren’t something to apologize for. They’re usually where the interesting work is.
Got a seat that doesn’t fit a box?
I read these myself. Jonathan Soo Hoo, my partner at Mirror, does the first outreach on some searches; if you hear from him, that’s why.