Career guidance for engineers, from people who have done it.

How compensation is actually decided, what is negotiable beyond base salary, and the specific words to use when an offer arrives. A few hours here routinely returns more than a year of side projects.

A sequenced path through the engineering management loop, covering people scenarios, project execution, technical depth and the coding round that many managers are still asked to pass. A very different loop from an engineering one.

The management interview in detail: people scenarios, hiring, performance conversations, project execution and stakeholder work, with the structures that keep an answer from wandering. Manager answers fail on structure more often than on substance.

Aimed above the first management rung, at directors and senior leaders, covering organisational design, strategy, cross functional influence and the scope questions that separate levels. The questions change shape at this level rather than getting harder.

An automated review of your resume against what technical recruiters screen for, returning specific changes rather than a score. Useful as a first pass before you ask a human to look at it.

A curated set of articles, talks and books about the part of the job that is not writing code: scope, influence, communication and ownership. Useful when you are technically solid, keep getting good reviews, and still cannot work out what is missing for the next level.

Negotiation from an FBI hostage negotiator, and far more practical than that sounds. The useful parts for engineers are listening techniques and how to ask a question that gets a real answer, which apply to salary conversations, scope discussions and disagreements with a tech lead.

Writing is most of a senior engineer's job: design docs, incident reports, pull request descriptions, the message that convinces a team to change direction. This is the standard book on writing clear non fiction, and applying even a third of it will make you noticeably better at the part of the job nobody trains you for.

The argument that most software problems are people problems wearing a technical costume: interruptions, office layout, turnover, teams that never got to gel. Useful long before you manage anyone, because it gives you language for why a workplace feels productive or does not.

Written in 1975 and still the best explanation of why adding people to a late project makes it later. Short essays on communication cost, second system syndrome and why estimates go wrong. If you have ever watched a team grow and slow down at the same time, this tells you what you were looking at.

Stories and guidance from people who reached staff engineer, covering the archetypes of the role, how they got promoted and what the job actually involves. Free, and the clearest available answer to what the senior plus track is.

The practical companion to the staff engineer question: how to pick what to work on, how to influence without authority, and how to lead technical work across teams you do not manage. Specific rather than inspirational.

The standard book on engineering management, structured by level from being mentored through tech lead, manager, director and beyond. Read the chapter one level above where you are.

A free, detailed and unusually honest account of how to negotiate an engineering offer, written by someone who did it from a bootcamp background and documented the numbers. The single most useful free article on this list.

Crowdsourced compensation data by company, level and location, with the level mappings that let you compare titles across employers. Walking into a negotiation without this is negotiating blind.

Reporting on how technology companies actually work: how teams are run, how promotions and compensation are decided, what hiring looks like right now. The best available source on the industry as an industry.

A moderated community for engineers past the early career stage, where the discussions are about scope, management, difficult teams and career decisions rather than how to get a first job. Substantially higher signal than the general forums.

Conference talks and writing on engineering leadership, covering team health, technical strategy, incident culture and the practical mechanics of leading engineers. A large free archive of talks from people doing the job.

A free framework describing what each engineering level means across technology, system ownership, people, process and influence, as radar charts you can compare yourself against. Makes the promotion conversation concrete.

A specific, free guide to writing an engineering resume, including what to cut, how to phrase an achievement and how the automated screening actually works. Rewriting a resume against this takes an evening and changes response rates.

A startup job platform where listings show salary and equity ranges upfront and applications often go straight to a founder. Worth a profile even when you are not looking, because the inbound is qualified.

An anonymous, work email verified community where compensation, levels, layoffs and internal conditions get discussed frankly. Valuable for the data and worth approaching with caution for everything else.

A free map of what engineering management involves, covering people, process, delivery, technical judgement and the business side. Useful mainly for finding out whether you actually want the job.