Tagged “seniority”
-
The Questions a Technical Reviewer Is Trying to Answer
An engineer reading your resume is answering a short list of questions. Knowing which ones tells you where the page is failing them.
-
What Belongs on an Engineering Resume
Which sections earn their space on a technical resume, which are habit, and how to order them so a reviewing engineer finds what they need fast.
-
Scope, Not Years: The Seniority Signal in a Resume
Seniority on a technical resume is read from the size of what you owned, not from time served. What scope consists of, and how to show it honestly.
-
The Staff-Level Resume Problem
Past senior, most of your impact runs through other people. How to put influence work on a resume without it reading as management.
-
When Nobody Reviewed Your Code
If your whole career has been unsupervised engineering, reviewers worry about calibration, not ability. Three signals that answer the worry honestly.
-
Moving From a Big Company to a Startup, and Back
Company size changes what your bullets are evidence of. What a small team reads as a risk in a big-company resume, and the reverse.
-
A Selected-Work Block for the System You Know Best
One system described in five lines, with its constraints and trade-offs, does more for a senior application than fifteen scattered bullets.
-
Design Documents, RFCs, and What They Show
Written artefacts are the physical output of senior engineering work. How to cite a design doc or postmortem on a resume without attaching one.
-
A Specialism the Reader Wasn't Looking For
Embedded, compilers, geospatial, protocols, simulation. How to write a niche technical specialism so a generalist reviewer can evaluate it.
-
The Project That Got Cancelled
Work that never shipped is still engineering. How to put a cancelled project, an abandoned rewrite, or a deprecated system on a resume.