How to write a job post senior engineers will read to the end

We ingest thousands of engineering job posts a day onto the board, from the companies' own career sites, so we see the full distribution: the posts that read like products and the ones that read like legal disclaimers. The difference is not writing talent. It is whether the company decided what it was offering before it started typing. Senior engineers scan for four things, in this order: the money, the stack, the scope, and the proof you are real. Here is how the good posts handle each.

1. The money, posted

On our board today, about 37 percent of live roles publish a compensation range, and they earn a disproportionate share of qualified applications. Senior engineers know the bands; hiding yours does not create negotiating room, it filters for people who do not know their value, which is the opposite of your shortlist. Post a real range you would defend on a call, not a $120K-to-$350K canyon that says you have not decided the level.

2. The stack, honestly

Write what they will touch in month one, not the wishlist. Two crisp lines beat twelve logo bullets: what the system is, what it runs on, where it hurts. The hurts are the credibility marker. "Rails monolith we are carving into services, Postgres at the edge of comfort, a queue that needs replacing" attracts exactly the person who has done it, and politely loses everyone else, which is the post doing its job.

3. The scope, with a year-one outcome

Senior people buy problems, not titles. One sentence that names the outcome, "own the path from one region to three", does more work than every adjective in the thesaurus. If the role exists because of a raise, say so and say what the round funds; candidates read funding the way you read CVs, and runway is the question behind their questions anyway.

4. The proof you are real

• Round, lead investor, and close date. Public facts; hiding them just sends people to look them up with less context.
• Team size and the number an engineer cares about: how many engineers, out of how many people.
• The process, named: how many steps, how long end to end. Then keep to it; the process is the product demo of working with you.
• A named human. Posts that read as from someone get answered like mail; posts from "the team" get treated like banners.

Before and after, one line

The whole difference fits in a single bullet. Here is the version that loses the reader:

We are looking for a rockstar engineer who thrives in a fast-paced environment and wears many hats.

And the version that earns the next thirty seconds:

You will own the path from one region to three on a Go and Postgres stack that is past comfortable at our scale. Series A, led by a top infrastructure fund, closed in March.

Same role. The first describes the company's mood; the second describes the work and the facts. Senior engineers buy the second every time.

The structure that works

1. 01A title that names the level and the domain, nothing cute.
2. 02The compensation range, real and defensible, in the first screen.
3. 03One sentence of year-one scope: the outcome this person owns.
4. 04The stack, honestly, including what hurts.
5. 05The round, the lead investor, and the close date.
6. 06Team shape: how many engineers, out of how many people.
7. 07The process, named and timed, and then kept to.
8. 08A human to reply to, with a name.

Eight elements, about 500 words, scannable in one screen. If a section cannot earn its place against that list, cut it.

What to cut

The rockstar-ninja register and every word like it. The eight-bullet values block, your values show up in the range you post. The years-of-experience arithmetic, name the judgment you need instead. And the requirements list longer than eight items, which reads as a committee, because it was one. A post is not a contract; it is an ad aimed at one person. Write it to that person and accept losing the rest.