No process import
The nice engineering exec is how shipping stalls
Freeze the offer. Run cadence and incident hours. You still sign by hand.
A charming Head of Engineering from a company that ships twice a quarter is not a gift to a shop of twenty. It is a new approval chain with a warm smile. The first month feels like relief. Someone finally owns the people stuff. Then a one-line fix waits on a working group, a retro, and a staff meeting that did not exist last Tuesday.
You will like them. The team will like them. That is not a signal. Rapport is how the stall arrives.
The welcome is the stall
You know this desk. A recruiter sent a VP with a logo everyone recognizes. Your senior engineer had coffee and said they were kind. The board likes the resume. The offer sits in drafts, and you can feel the pressure to be "serious" about engineering leadership.
Jason Lemkin (@jasonlk), who built SaaStr by sitting with the operators who actually make these offers, has never seen that hire work.
@jasonlkOne thing I have never, ever, never seen work: hiring an SVP Eng, CTO, or Head of Engineering from an old, slow moving tech company. Usually they are really nice, and a good "people person". At first, the team welcomes them. And everything just slows down. So, so fast.
Jason Lemkin
He is not scorning kindness. He is scorning the import of a slow machine into a business that still has to ship on Thursday.
If you already gave a verbal, you are not stuck. You have not signed. Money, scope, and the call of builder versus import still sit with you. The current lead still owns this week's deploys. None of that transfers at a handshake.
Who holds the pen, who holds the pager
You do not need a new hiring stack. You need names on a sequence, this week, before anyone celebrates.
The owner freezes every unsigned Head of Engineering, CTO, or VP Eng offer. The person who still ships this week runs a cadence hour. The person who holds the pager runs an incident hour. You sit the last fifteen minutes and say, out loud, builder-leader or process import. Nobody else "aligns" the team into a life cycle they brought from the last campus.
Figure 1
Comp stays human. Title stays human. Whether this person is here to build with the people you have, or to install the company they left, stays human. The recruiter does not get a vote on that last point. The candidate does not get to pause the queue while they "get the lay of the land."
If you are not in an active search, the same sequence still has a home. Open the hiring doc you will hand the next recruiter. Write the two hours in before anyone books culture fit. That is the work object: the next offer, not a vibe.
Three tests that beat coffee
Coffee told you they are pleasant. Pleasant is how Lemkin says the slowdown starts. If an engineering-lead offer is in motion this week, stop adding fit chats. Run these three, in order, with the people named above in the room.
- Cadence. Ask for the last three things they personally merged, shipped, or closed. Dates. Names of the people who were in the room. If they speak only in org charts and operating models, they are importing process.
- Incident. Ask for the last break they owned from page to the note after. Who they woke. How long until a customer heard a true sentence. If the answer is a committee, that committee is coming with them.
- Kill. Ask for the last process they inherited and shut down. A builder can name one and the date it died. An import can only name the ritual they added.
You listen. The shipping lead listens. You do not outsource the judgment to a scorecard. If they will not sit a live staging bug with your current lead for twenty minutes, you already have the answer. Decision latency is the job. A person who needs a week to "socialize" a one-line fix will need a week on yours.
What you do not test this week: whether they remember your values slide. Whether they "get" the culture. Whether they would be fun at the offsite. Those are how the welcome happens. Lemkin already told you what comes next.
What Friday can actually see
Nobody has a credible figure for how often a slow-company engineering exec freezes a team this size. Dinner stories are not a rate. Count the offer on your own desk.
| Measure | Count |
|---|---|
| Unsigned eng-lead offers with no cadence hour | |
| Hours the candidate took to decide a live staging call | |
| People who had to approve a one-line fix at their last shop |
Put those three on one sheet. A blank in the staging column is a count. Blank means they would not decide in the room. That is the latency you would be buying.
If there is no candidate this week, still fill the first row. Zero unsigned offers is a real number. Then lock the two hours into the hiring doc so next month's recruiter cannot skip them.
Run the three tests before Friday
Open the draft letter before you open Slack. The sequence is short on purpose. You can do it between now and the next board packet.
- Freeze every unsigned Head of Engineering, CTO, or VP Eng offer until cadence and incident hours are on the calendar
- Put the shipping lead on cadence, the pager owner on incident, and yourself in the last fifteen minutes
- Say builder or import out loud, then sign or kill. Comp and scope do not move without you
Keep the current lead on this week's deploys while you decide. The hire is not allowed to become a freeze. If you kill the offer, tell the candidate the reason in one sentence: we need someone who still ships, not someone who installs the last company's calendar.
You already have the unsigned letter and the people who still ship. Use both.
Sources
If one workflow is eating your week, tell me which one. I'll tell you if it's worth deploying — and if it isn't.
Message Mikko on LinkedIn