⚡️ asmbld · Issue #006
Written for engineers on the job search, EMs building teams, and founders hiring them.
01 · STAND-UP
"Feedback is the breakfast of champions." — Ken Blanchard
Most teams serve cold coffee and call it a meal.
The debrief happens. Someone types two sentences into the ATS. The candidate gets a rejection email written by a lawyer in 2019.
"Unfortunately, we moved forward with someone with {insert variable reason}..."
And everyone wonders why the next search starts with the same problems.
02 · SPRINT
I've been working with a handful of startups for the last 3 months. All of it has been contingent work and the feedback from some of the founders and teams have been brutal.
Last week (literally a few days ago) here's what I received our shared operations dashboard.
Eleven words.
"Hasn't used AI but is a solid engineer. Not sure if they're a fit."
I read it three times. Not because it was confusing.
Because I kept waiting for the rest of it.
There wasn't a rest of it.
I've been contingency recruiting for nearly three months now, but have been an internal recruiter, fractional recruiter, and agency recruiter for over ten years.
I've seen every flavor of debrief feedback. The two-sentence rejection. The single word — "pass" — with no period. The one that just says "no top startup experience" as if that's a complete thought and a full explanation rolled into one.
And for a long time, I accepted it.
I'd take the two sentences, translate them into something I could actually say to a candidate, and move on. It was painful, but it needed to be done to close the loop.
Next search. Same friction. Same vague brief. Same debrief conversations that went exactly nowhere.
I told myself: this is just how it works.
But here's what I was actually doing.
I was taking someone's ambiguity and converting it into false clarity. Dressing it up. Making it sound like a considered decision when it was really just a gut feeling with no words attached to it.
And then I'd pass that dressed-up ambiguity on to a candidate who deserved something better.
Here's what I started noticing.
Every weak debrief was a signal. Not about the candidate.
About the team.
"No top startup experience" — what that actually means: we don't know how to onboard someone who hasn't already done this exact job at a company that looks exactly like ours, and we're not ready to figure that out.
"Hasn't used AI" — what that actually means: we have no idea what our AI proficiency bar actually is. We didn't define it before the search opened. So we're using it as a vibe check and calling it a standard.
"Not a culture fit" — I'll leave that one where it is.
The two-sentence rejection doesn't protect the candidate from bad feedback.
It protects the team from having to articulate what they actually need.
And here's the part that never made it into any ATS note but I have to share with you here: when a team can't say why someone isn't a fit, they usually can't say what a fit actually looks like either.
The brief becomes the problem. The search becomes the symptom.
And six weeks later, everyone's frustrated — the founder, the EM, the recruiter, and definitely the candidate sitting at home with "not moving forward" in their inbox and no idea what to do with it.
How have we gotten this far in the search and still have these issues?
Well, the problem isn't the debrief.
It's everything that happened before it.
Most searches open without a real calibration conversation. The founder says they need a senior engineer. The account team ask a few questions. I get a job description that was written in forty-five minutes and hasn't been touched since.
And I go source.
Nobody stops to ask: what does good actually look like here? What's the specific gap we're trying to close? What would make us say yes on the spot, and what would make us walk away no matter how strong the resume is?
That conversation almost never happens before the search opens.
So it happens in the debrief. Badly. In eleven words.
That's why I built asmbld.
Not to fix the debrief. To fix what happens before it.
The calibration that should happen at intake — between the recruiter, the hiring manager, and the founder — is the same conversation that makes every step after it easier.
The sourcing. The screen. The debrief. The offer.
When you know what you're actually looking for, you can tell a candidate what the gap was. You can tell me what to search for next. You can tell your team what to evaluate in the room.
When you don't, you type eleven words and hope nobody asks follow-up questions.
I started building that calibration layer into every search I run.
Not a long intake form. Not a two-hour kickoff call.
Just the right questions, asked before sourcing opens, documented somewhere both sides can see.
What are we solving for? What's the growth path for this person? What would a yes look like in the first ninety days?
Those questions take twenty minutes.
They save months.
The searches that fail — the ones that drag, that churn through slates, that end in a hire that doesn't stick — almost never fail because the recruiter sourced wrong or the candidate wasn't strong enough.
They fail because nobody had that conversation at the start.
The debrief is just where the bill comes due.
And I'm tired of paying for it.
03 · RETROSPECTIVE
✅ What went well
Improving the calibration conversation into intake — before sourcing opens — should become the new standard for hiring. The debrief gets easier when the expectations are already written down and discuss thoroughly. The candidate gets a real answer because we already knew what we were looking for.
🔧 What could be improved
I still let some searches open without a full calibration pass. A founder moves fast, I move with them, and six weeks later we're back to eleven-word debriefs. I'm building asmbld partly to fix that — in my own practice first.
⚡ One action item before next week
Before your next search opens — as a founder, an EM, or a recruiter — write down the answer to this one question: "What would make us say yes on the spot?" Not the job description. Not the requirements list. The real answer. If you can't write it in two sentences, the search isn't ready to open yet.
❓ Open question for readers
Has a hiring manager or recruiter ever taken the time to calibrate with you before the process started — and did it change how the search felt from your side?
⚡️ When you're ready, here are three ways I can help:
The Career Playbook — DIY ($64)
The system, handed to you. You run it.
The Career Playbook — DFY ($256)
Resume, LinkedIn, comp benchmark — delivered in 5 business days.
The Career Playbook — DWY ($512)
30 minutes. We work through it together, with your real materials.
See you next Sunday!
⚡️ asmbld · Issue #006
Written for engineers on the job search, EMs building teams, and founders hiring them.
