← Writing / tag

resume

2 posts

  1. Every number on my resume has to survive one follow-up questionI audited my resume the way I audit a pipeline: every claim is a row, every number needs provenance, and a build check decides what is allowed on the public copy.
  2. A resume review checklist for data engineersThe checks I now run on any data engineering resume, mine included: the six-second read, the X-Y-Z bullet, scope over tools, one claim per number, and what an ATS really does.