Your Job Posting Promises Hard Problems, and Senior Engineers Can't See a Single One

Clinton De Young Ghostwriting

A hiring manager has had a senior backend role open for four months. The posting promises "hard problems at scale," "a strong engineering culture," and "the chance to shape our architecture." Recruiters send outreach every week. The replies that come back are polite declines, or nothing at all, and the few candidates who make it to a first call ask the same question in different words: what would I actually be working on?

That question is the problem. Every job posting for a senior engineer makes the same promises, so the promises carry no information. A strong candidate who already has a good job isn't choosing between your posting and unemployment. They're deciding whether your problem is more interesting than the one they have now, and nothing you've published lets them judge that.

Senior engineers evaluate the work, not the pitch

Think about how an experienced engineer decides whether a team is worth a conversation. They want to know what the system looks like, what constraints it operates under, what the team has already tried, and whether the people there think clearly about trade-offs. Those are the same things they'd want to know before joining a new project inside their current company.

A posting can't answer those questions. It's a list of requirements and adjectives, reviewed by several people and written to offend nobody. Your careers page can't answer them either. What can is a technical article about a real problem your team is working on, published under the name of the person the candidate would report to.

That's a different thing from a general engineering blog. A blog is published for whoever finds it. A hiring article has one reader in mind: the engineer you want to hire, deciding whether to reply.

What a hiring article has to show

Most "how we built it" posts are written to impress. A post written to hire has a harder job, which is to let a skeptical expert see the work clearly enough to want in. In practice, that means:

  • The actual problem, at its actual size. Not "scaling challenges," but the workload, the bottleneck, and why the obvious fix doesn't work. If you can't publish exact figures, publish ratios or orders of magnitude. Vague is worse than approximate.
  • The decision and what you gave up for it. Senior engineers trust a team that names the cost of its choices. A post that presents every decision as obviously right reads as either naive or edited by marketing.
  • What's still unsolved. This is the part most companies cut, and it's the part that hires people. The open problem is the job. If the post ends with everything fixed, the reader has no reason to join.
  • How the team works. How the decision got made, who argued for what, how the design was reviewed. Candidates are evaluating colleagues as much as code.
  • The hiring manager's voice. The byline should belong to someone the candidate would work with directly, and the post should sound like that person talking to a peer.

The third point deserves emphasis. Companies instinctively sand off the mess: the migration that's half-finished, the service everyone wants to rewrite. But an engineer who joins and discovers the mess six weeks in feels misled. An engineer who reads about it beforehand and still applies is someone who wants to work on exactly that.

Put the article where candidates already are

A hiring article that only lives on the blog does a fraction of its job. Build it into the hiring process deliberately:

  1. Link it from the job posting, near the top, with one sentence about why it matters: "This is the system you'd own. Here's what we've learned so far."
  2. Give it to recruiters to use in outreach. "Here's a post from the team about the problem this role works on" gives a candidate something real to respond to, which another paragraph about culture never does.
  3. Use it in the interview loop. Send it before the first technical conversation. The discussion starts at the interesting part instead of thirty minutes of context-setting, and the candidate's reaction tells you a lot.
  4. Ask every candidate whether they read it and what they thought. That's how you find out whether it's working, and their answers will tell you what to write next.

Write it from the hiring manager's head, not their keyboard

The obstacle is predictable: the hiring manager who could write this is the same person stretched thin because the role is open. That's where a ghostwriter earns the fee. The working process I described in Your Engineering Blog Didn't Run Out of Ideas. It Ran Out of Writers. applies here too: start from a design doc or decision record, interview the named author, keep their words, and clear review early.

For a hiring article, add three questions to that interview:

  • "What would a new senior engineer work on in their first three months?" That answer is the spine of the post.
  • "What's the one thing you'd most want a candidate to push back on?" It surfaces the open problem and signals that disagreement is welcome.
  • "What's wrong with the system that you'd tell a friend but not a customer?" Not all of it belongs in the post. Some of it should.

Then send the draft to legal and security with a specific list of the details you need to keep, not a request to approve "the post." Reviewers handed a vague request will remove every specific, and the specifics are the only reason a senior engineer will read past the first paragraph.

Start with the role you've had open longest

You can test this without hiring anyone. Pick the role that's been open the longest. Ask the hiring manager to describe, out loud, the hardest problem the person in that role will face. Write down the answer, then compare it with the job posting. If the posting doesn't mention that problem at all, you've found the gap, and probably the reason good candidates aren't replying.

Why this takes an engineer

A hiring article fails the moment a candidate can tell the writer didn't understand the system. Getting it right means following the hiring manager into the details: why the queue backs up, what the data model can't express, why the rewrite keeps slipping. Then it means choosing the details a senior engineer will find interesting and explaining them correctly. I spent decades as a software engineer before co-founding Inkwright, Inc., and that conversation is the part of the work I know best.

If you have a senior role that's been open too long and a team with a real problem worth showing, I'd be glad to help you write the article that shows it. You can reach me through the contact page.