Tagged “skills-list”
-
Building Evidence for a Term You Don't Have
A technology is everywhere in your target roles and nowhere in your record. Side projects are the fourth-best answer — here are the first three.
-
What a Requirements List Is Evidence Of
Requirements are written by someone who isn't doing the job. What a single line entitles you to conclude, and what only frequency across postings can.
-
Auditing Your Stack List Against Real Postings
Your skills section records where you've worked. How to measure it against what your target roles actually ask for, and the traps in the count.
-
Name the Problem, Not Just the Tool
Bullets that list technologies read as a stack inventory in the wrong place. How much tool-naming a sentence can carry, and what to do with the rest.
-
The Tech Stack List Problem
Every engineer's skills section is too long, badly grouped, and quietly overclaiming. A method for cutting it down to what you can defend.
-
The Frontend Engineering Resume
Frontend work is the most visible engineering there is and the easiest to under-describe. What to write instead of a list of frameworks.
-
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.