Tech Resume Guide — Get Past the Screen

A recruiter decides in under a minute whether to keep reading. This guide shows how to structure a one-page resume for AI, data, software, cloud and security roles so the right evidence is impossible to miss.

Est. 15 min November 2026

What a resume is for

A resume does not get you a job. It gets you a conversation. Its only job is to make a recruiter or hiring manager think “this person can probably do the work — let's talk.” Everything on the page should serve that one goal.

Many companies filter applications with an applicant tracking system (ATS) before a person skims them. You need a format that software can parse and a layout a busy human can scan in seconds.

The structure that works

  1. Header — name, city or “Remote”, email, phone, LinkedIn, GitHub or portfolio. No photo, date of birth, or full address.
  2. Summary (2 lines, optional) — the role you want and your strongest proof. “Data engineer with 2 years building Spark and Airflow pipelines on Azure; cut a daily batch from 4 hours to 35 minutes.”
  3. Skills — grouped by category (Languages, Data, Cloud, Tools). Only list what you could discuss in an interview.
  4. Experience — reverse chronological, 3–5 bullets per role.
  5. Projects — 2–3 projects with links. For freshers this section goes above Experience.
  6. Education and certifications — degree, institution, year. Certifications only if relevant to the role.

Keep it to one page early in your career. Use a plain single-column layout: no tables, text boxes, icons, or skill bars — ATS parsers often scramble them.

Write impact bullets, not duty lists

Each bullet should answer: what did you do, with what, and what changed because of it? A reliable pattern is action verb + what you built + tools + measurable result.

  • Weak: “Responsible for ETL pipelines.”
  • Strong: “Rebuilt 12 nightly ETL jobs as incremental Spark pipelines on Databricks, cutting run time by 70%.”
  • Weak: “Worked on a chatbot.”
  • Strong: “Built a RAG support assistant (FastAPI, pgvector, an LLM API) with a 120-question evaluation set; answer accuracy rose from 61% to 84%.”

If you do not have exact numbers, use honest estimates you can explain (“about 2 million rows a day”) or scale words (users, rows, services, latency). Never invent numbers — interviewers will ask how you measured them.

No work experience yet?

Projects are your experience. Pick projects that look like the job:

  • Finish the capstone from your career path and describe it like a job: problem, architecture, tools, result.
  • Link the GitHub repository and a live demo or short video. A README with an architecture diagram matters more than extra projects.
  • Include internships, freelance work, open-source contributions, hackathons, and teaching assistant roles.

For a data-specific walkthrough, read How to Write a Data Engineer Resume When You Have No Work Experience.

Tailor it for every application

  • Read the job description and highlight the skills it repeats. Use the same words where they are true for you (“Azure Data Factory”, not just “ADF”).
  • Reorder bullets so the most relevant ones come first.
  • Keep a long “master resume” and cut a one-page version per role family — AI, data, backend, and so on.

Final checklist

  • One page, single column, exported as PDF with a clear file name (Firstname-Lastname-Data-Engineer.pdf).
  • Every bullet starts with an action verb and most include a result.
  • Every skill listed is one you could answer questions about.
  • Links work and the GitHub repositories have READMEs.
  • No spelling mistakes — read it aloud and ask someone else to read it.
  • Consistent dates, tense, and formatting throughout.

Next steps

Back up every resume claim with a project people can open — see the portfolio guide. Then practise talking about each bullet with the mock interview guide.

Share

Discussion

0

Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.

Continue with GitHub
Loading...