⚡️ asmbld · Issue #001

Written for engineers on the job search, EMs building teams, and founders hiring them.

01 · STAND-UP

“The system is not broken. It was built this way.”

• common observation from anyone who has been inside one long enough

Most engineers on the job search eventually ask the same question:

What am I doing wrong?

They optimize their resume. Rewrite their summary. Practice their behavioral answers. Apply again. Wait again.

And the system — silent, inconsistent, weirdly personal — gives them nothing back.

Ten years in this profession and the problem still remains: the process isn’t failing you because of you. It’s failing because it was never designed around candidates to begin with.

---

02 · SPRINT

Engineers are some of the most systems-minded people I’ve ever worked with.

They debug before they fix.

They ask why something broke — not just how to patch it.

They know that bad outputs usually mean a broken system, not a broken user.

And then the job search starts. And somehow, all of that thinking gets turned inward.

Maybe my resume isn’t good enough. Maybe I didn’t interview well. Maybe I need more certifications.

But here’s what’s actually happening on the other side of that application portal.

The hiring process is an extension of the company itself — its brand, its internal tools, its communication culture, its priorities, its politics. When a hiring process feels cold, chaotic, or opaque, it usually is. That’s the product working as designed.

Consider what candidates are actually up against:

Fragmented tooling. An ATS that was chosen by finance. A take-home that was built by the last engineering manager. A panel interview format that nobody has audited since 2019. The left hand doesn’t know what the right hand is evaluating — and neither does the candidate. It’s reasonable to feel lost inside a process that was never coherent to begin with.

Brand confusion. Companies say they want culture-adds, then screen for culture-matches. They post values on their careers page that contradict how the interview panel actually behaves. The job description was written by HR. The hiring manager has different criteria. The skip-level has different criteria still. When the signals conflict at every turn, of course it feels impossible to get it right.

Tech stack as identity. Hiring decisions are often less about what you can build and more about whether you’ve touched the same tools they already use. Engineers who don’t make the cut here often walk away wondering what they missed — when really, the decision was made before they said a word.

People as proxies. Every recruiter you talk to is carrying the invisible weight of the company’s priorities, the hiring manager’s preferences, and their own quarterly targets. They’re not obstructing you. They’re navigating the same fragmented system from a different seat, doing their best inside constraints they didn’t design either.

None of this is the candidate’s fault.

The engineers who move through this process with the least damage aren’t the ones who figured out how to optimize for it. They’re the ones who stopped internalizing its failures.

1. When a process ghosts you, that’s signal about the company’s communication culture — not your worth.
2. When a recruiter goes silent after a strong screen, something broke upstream — a headcount freeze, a reorganization, a hiring manager who changed the criteria mid-search. The system stalled.
3. When a technical screen feels arbitrary or disconnected from the actual role, it probably is. Someone inherited that rubric. Nobody reviewed it. It’s been running on autopilot.

The job search doesn’t need you to be better at absorbing a broken process. It needs you to stop mistaking the system’s failures for your own.

What actually works — building relationships before roles are posted, making your work legible on your own terms, targeting companies where the hiring process reflects the kind of environment you actually want to work in — none of that is about gaming the system. It’s about recognizing that the process is the product, and choosing accordingly.

---

03 · RETROSPECTIVE

✅ What went well

The most memorable engineers I've interviewed shared a shifted approach to their job search: they stopped trying to fix themselves and started reading the hiring process as data about the company. That reframe changes everything, and removes the emotional attachment to self worth.

🔧 What could be improved

The narrative around job searching still centers the candidate as the problem. Advice content — mine included — can reinforce that without meaning to. The story needs to name the system more honestly, earlier.

⚡ One action item before next week

The next time a process stalls, ghosts, or gives you confusing feedback — write it down. Not to vent. To audit. What does this tell you about how the company communicates internally? What does it tell you about whether you’d want to work there?

The process is the preview.

Hit reply if this lands differently than what you usually hear. I read every response and am building asmbld for you, the engineer.

I'm glad you're here,

Henry ⚡️