Resume guides by role
One guide per role, written against the postings currently in the JobCues directory. Each one lists the keywords a scanner matches literally, the parent terms it never infers, and three bullets rewritten line by line.
Why a resume needs to change per role
An applicant tracking system scores a resume by matching the job description's literal terms against the document. The terms differ per role, and the scanner infers nothing: PostgreSQL does not register as SQL, React does not register as JavaScript, and Figma does not register as prototyping. Each guide below is the keyword list and the bullet structure for one role, so the tailoring starts from the right baseline.
- Software Engineer resumeA software engineer resume passes an applicant tracking system when its work bullets contain the job description's literal technology names, not synonyms or parent concepts.21 keywords · 3 bullet rewrites · 4 questions
- Frontend Developer resumeA frontend developer resume is screened on framework names, browser platform terms, and increasingly on accessibility and performance vocabulary.20 keywords · 3 bullet rewrites · 3 questions
- Backend Developer resumeA backend developer resume is screened on language, datastore, API style, and infrastructure keywords.21 keywords · 3 bullet rewrites · 3 questions
- Full Stack Developer resumeA full stack developer resume has to clear two keyword lists on one page, which is why it fails more often on dilution than on omission.18 keywords · 3 bullet rewrites · 3 questions
- Data Analyst resumeA data analyst resume is screened on SQL first, a business intelligence tool second, and a statistics vocabulary third.18 keywords · 3 bullet rewrites · 3 questions
- Data Scientist resumeA data scientist resume is screened on modelling vocabulary, an experimentation vocabulary, and evidence that a model reached production.19 keywords · 3 bullet rewrites · 3 questions
- DevOps Engineer resumeA DevOps engineer resume is screened on a named cloud, an infrastructure-as-code tool, a CI/CD system, and an observability stack.20 keywords · 3 bullet rewrites · 3 questions
- Product Manager resumeA product manager resume is judged on decisions, not on features shipped.20 keywords · 3 bullet rewrites · 3 questions
- QA Engineer resumeA QA engineer resume is screened on automation framework names first and process vocabulary second.20 keywords · 3 bullet rewrites · 3 questions
- Machine Learning Engineer resumeA machine learning engineer resume is screened as an engineering resume with modelling on top.20 keywords · 3 bullet rewrites · 3 questions
- Mobile Developer resumeA mobile developer resume is screened per platform, and the platform strings are not interchangeable.20 keywords · 3 bullet rewrites · 3 questions
- UI/UX Designer resumeA UI/UX designer resume is read alongside a portfolio, which means its job is to state outcomes the portfolio cannot: what you researched, what you decided, and what the metric did afterwards.17 keywords · 3 bullet rewrites · 3 questions
Skip the general case
These lists cover what postings ask for on average. The score that decides your application is the one against the specific description you are answering. Paste it and get the matched terms, the missing terms, and a rewritten resume in about 15 seconds.