Tech Resume: How to Write One for Any Tech Role (2026)

Most advice about a tech resume (CV) is written for software engineers and then reused for every other tech role. A product manager, a data analyst, a UX designer, an SRE, a sysadmin and a QA engineer all apply through the same portals and get screened by the same recruiters, but the reader looks for different proof on each page. This guide covers the format that works across tech roles, then goes role by role: what changes in the skills section, which links to include, which metrics count, and a short fictional snippet for each.

If you write software for a living, the software engineer resume guide is the better page for you. The sections below cover the roles around engineering.

What makes a tech resume different

Recruiters in tech screen for tools and outcomes before they read anything else. The posting names a stack, a platform or a method, and the first pass checks whether your page contains those words. The second pass, by the hiring manager, checks whether you did anything with them. A tech resume succeeds when both passes are quick: the skills section answers the first in five seconds, and the experience bullets answer the second with numbers.

The second difference is evidence outside the document. A designer’s portfolio, an analyst’s notebook, an SRE’s open-source Terraform module and a PM’s product that anyone can sign up for all carry more weight than adjectives. The resume’s job is to point at them.

How to format a resume for tech jobs

The format is the same across roles, so settle it once.

• One page through your first eight to ten years. Two pages for senior people with many products or systems to account for.
• Reverse chronological. Current role first. Functional resumes that hide dates invite questions about the gaps.
• Section order: contact, summary (optional, two lines), skills, experience, projects, education, certifications. Designers and analysts with a strong portfolio can move projects above experience when they are early in their career.
• Contact block in the page body, with name, city, email, phone and links. Keep it out of the Word header region; parsers can skip it there.
• Links as text, not icons alone: linkedin.com/in/name, github.com/name, name.design. The link should survive copy-paste.
• Text-based PDF. Export from your editor rather than printing to image. Select all and paste the result into a plain text editor once to check that every section comes out in order.
• Plain fonts, 10 to 11 point, single column for anything submitted through an application form. A two-column version is fine for a PDF you email to a person.
• No photo for US applications, and no date of birth anywhere.
• File name: Firstname-Lastname-Resume.pdf.

The vocabulary in the skills section should mirror the posting. The method for pulling terms from a job description and placing them is in the resume keywords guide; this page assumes you have done that and focuses on what each role needs the page to prove.

Tech resume examples by role

Each snippet below is fictional. People, companies and numbers are invented to show the shape of a strong entry.

Product manager

The reader wants to know what you shipped, who used it, and how you decided what to build. The weak PM resume lists responsibilities (“owned the roadmap”); the strong one lists outcomes with the method attached.

Skills section: discovery methods (interviews, surveys, usability tests), experiment tooling (A/B frameworks, analytics such as Amplitude or Mixpanel), SQL if you can run your own queries, the delivery tools (Jira, Linear), and domain knowledge (payments, healthcare, B2B SaaS). Keep programming languages off unless the posting is for a technical PM.

Links: LinkedIn, plus the product itself if the public can see it. A short public write-up of a launch is worth more than a Medium post about product philosophy.

Metrics: adoption, activation, retention, revenue, time to ship, scope cut, and the size of the team you worked with.

Example (fictional): Senior Product Manager, Lumen Ledger (B2B invoicing SaaS), 2024 to present

• Owned invoice reminders from discovery to launch; 1,200 paying accounts adopted the feature in its first quarter and late payments fell 18% for those accounts.
• Ran 32 customer interviews and a 400-response survey to rank the 2026 roadmap, cutting planned scope by a third before engineering started.
• Defined the activation metric (first invoice sent within 7 days) and raised it from 41% to 56% with onboarding changes.
• Wrote PRDs and ran two-week sprints with six engineers and one designer; shipped 11 releases in 12 months.

Data analyst and data scientist

The reader scans for SQL first, then the warehouse and BI tools, then whether your analysis changed a decision. For data science roles they add modelling libraries and look for a model metric and a deployment story.

Skills section: SQL with the dialect (BigQuery, Snowflake, Postgres), Python or R with the libraries you use (pandas, statsmodels, scikit-learn), transformation and BI tools (dbt, Looker, Tableau, Power BI), experiment design, and for data science the modelling work (gradient boosting, forecasting, NLP) plus deployment basics (Docker, Airflow, MLflow).

Links: GitHub with one or two cleaned-up notebooks, or a public dashboard.

Metrics: money or hours saved, decisions changed, reporting time cut, model performance (AUC, RMSE, precision at k) and what the model did in production.

Example (fictional): Data Analyst, Northbank Grocery (online grocery), 2023 to present

• Built the weekly retention dashboard in Looker on a dbt model over BigQuery; it replaced four spreadsheets and cut Monday reporting from six hours to twenty minutes.
• Analysed delivery-slot pricing with a difference-in-differences test across 14 cities; the pricing team raised peak-slot fees based on the result, adding an estimated £310k a year.
• Wrote the SQL definition of “active customer” that finance, marketing and the board deck now share.
• Trained a gradient-boosted churn model (AUC 0.84) that feeds a weekly win-back campaign; targeted customers churn 9% less than the control group.

UX designer

The portfolio does the heavy lifting, so the resume’s job is to get the reader to open it. Hiring managers look for the end-to-end process (research, flows, prototypes, handoff) and for proof that a design changed a metric after release.

Skills section: design tools (Figma, prototyping), research methods (usability testing, interviews, surveys), systems work (design systems, component libraries), accessibility (WCAG 2.1 or 2.2), and the analytics you read (Mixpanel, Hotjar). A line of front-end knowledge (HTML/CSS, basic React) helps for product teams.

Links: the portfolio URL at the very top, next to your name. Make sure it loads without a password, or state the password in the application. Add Dribbble or Behance only if the work there is current.

Metrics: task completion, conversion, time on task, support tickets, accessibility audit results, and adoption of a design system by other teams.

Example (fictional): Product Designer, Harbor Health (patient app), 2023 to present · Portfolio: harborwork.example

• Redesigned appointment booking from nine screens to four; completion rose from 63% to 81% in the month after release (Mixpanel).
• Ran 18 usability sessions across three rounds and turned the findings into a Figma component library that two squads now use.
• Partnered with engineering on an accessibility pass; 46 screens passed a WCAG 2.1 AA audit.

DevOps and SRE

This resume reads closest to a software engineer’s, with the emphasis moved to infrastructure, reliability and cost. The reader scans for the cloud provider, the orchestration and infrastructure-as-code tools, and whether you have carried a pager.

Skills section: cloud (AWS, GCP or Azure with the services you ran), Kubernetes and Helm, Terraform or Pulumi, CI/CD (GitHub Actions, GitLab CI, Argo CD), observability (Prometheus, Grafana, Datadog), scripting (Python, Bash, Go), Linux, networking basics and incident management.

Links: GitHub with a Terraform module, a Helm chart or an operator you maintain.

Metrics: deploy time, deployment frequency, change failure rate, mean time to recovery, SLO attainment, pages per week, and infrastructure cost.

Example (fictional): Site Reliability Engineer, Quillpay (payments), 2022 to present

• Moved 40 services from hand-built EC2 hosts to EKS with Terraform and Helm; deploy time fell from 45 minutes to 6 and monthly compute cost by 22%.
• Owned on-call for the payments API (99.95% SLO); cut pages from 31 a week to 8 by fixing alert thresholds and three recurring failure modes.
• Built GitHub Actions pipelines with canary deploys and automated rollback; change failure rate dropped from 14% to 4%.
• Wrote the incident process and ran 26 blameless post-mortems in a year; median time to recovery fell from 71 minutes to 24.

IT support and sysadmin

The reader checks the environment first (Windows or Linux, Microsoft 365 or Google Workspace, on-premise or cloud identity), then the scale (users, sites, tickets), then whether you reduced the work rather than only doing it.

Skills section: operating systems and directory services (Windows Server, Active Directory, Entra ID), endpoint management (Intune, Jamf), productivity suites, networking (VLANs, DHCP, DNS, firewalls), scripting (PowerShell, Bash), ticketing (Jira Service Management, ServiceNow), and frameworks (ITIL). Certifications matter more here than in most tech roles: CompTIA, Microsoft, Cisco and cloud fundamentals belong in a section of their own.

Links: LinkedIn is enough. A GitHub with PowerShell or automation scripts helps if you want to move toward DevOps.

Metrics: users and sites supported, tickets closed, same-day resolution rate, uptime, rollout time, setup time per device, and security incidents before and after a change.

Example (fictional): IT Systems Administrator, Castell Logistics (600 staff, four sites), 2022 to present

• Administered Microsoft 365, Intune and Active Directory for 600 users; closed about 2,400 tickets a year with a 94% same-day resolution rate.
• Rolled out MFA and conditional access to all accounts in eight weeks; account-compromise incidents fell from five a quarter to zero over the following year.
• Replaced the manual laptop build with an Autopilot image, cutting new-starter setup from three hours to thirty minutes.

QA and test engineer

The reader looks for automation first, then test design, then evidence that your testing caught things before customers did. Manual-only QA resumes still get interviews, but a framework name in the skills section moves you up the list.

Skills section: automation frameworks (Playwright, Cypress, Selenium) with the language (TypeScript, Python, Java), API testing (Postman, REST Assured), performance (JMeter, k6), test management (TestRail, Xray), CI integration, SQL for data checks, and ISTQB if you hold it.

Links: GitHub with a sample test suite, even a small one, shows how you structure tests.

Metrics: test count and coverage, suite runtime, regressions caught, defects found before release, manual regression time saved, and escaped defects after release.

Example (fictional): QA Engineer, Brightlane (edtech), 2023 to present

• Built the Playwright end-to-end suite from zero to 420 tests across checkout and classroom flows; it runs in CI in 11 minutes and blocked 37 regressions in a year.
• Wrote the test plan for the payments migration and found 23 defects before release, including a currency-rounding bug that affected 3% of orders.
• Cut manual regression from three days to one by automating 60% of cases and deleting duplicates.

Writing the skills section for any tech role

Group by category and label the rows, in the order the posting cares about. A data analyst applying to a Snowflake shop leads with SQL and Snowflake; the same analyst applying to a Python-heavy research team leads with pandas and statsmodels. Four to six rows is the usual range.

List what you can discuss in an interview. A recruiter will not test the list, but the hiring manager will pick the least familiar item and ask about it. Tools you have used once belong in a project bullet with context (“built a proof of concept in Grafana”), not in the skills block.

Years of experience per tool (“Python (5 years)”) add little and can hurt, because the reader compares the number against the posting’s requirement instead of reading the bullets.

Metrics when you do not ship code

Tech roles outside engineering sometimes struggle to find numbers. Try these sources before giving up:

• Time. Hours saved per week, cycle time, time to resolution, time to ship. Most roles can measure something that got faster.
• Scale. Users, accounts, tickets, screens, services, sites, cities. Scale tells the reader what size of problem you have handled.
• Rate. Completion, conversion, resolution, failure, adoption. A before-and-after pair is the strongest form.
• Money. Revenue added, cost cut, spend avoided. Use “estimated” when finance did not sign off on the figure.

If a number does not exist, use the scope: “the app’s 46 screens”, “a team of six engineers”, “four sites”. A scope beats an adjective.

Tech resume template: what to look for

A template for tech roles needs a skills block that can hold labelled rows, a projects section that can sit next to experience, and a clean text layer when exported to PDF. Decoration built from text boxes or layout tables can cost you, because parsers read those out of order.

Resume Matcher is a free, open-source app (Apache 2.0) that you run on your own machine with your own AI model; it is not a website you upload to. Its builder ships seven templates (Single Column, Two Column, Modern, Modern Two Column, LaTeX-style, Clean and Vivid). Each exports a text-based PDF printed from real web-page text by a headless Chrome browser, so every word is selectable, and the two-column layouts keep the main content first in reading order. You can set A4 or US Letter, margins, spacing and font size, pick serif, sans or mono fonts, and drag sections into the order your role needs, for example projects above experience for a designer. Previews and the full list of controls are on the PDF templates page.

Any template, from any source, should get the copy-paste test once before you send it anywhere.

Common mistakes on tech resumes

• A skills list longer than the experience section. Cut it to what the posting wants and what you can defend.
• Responsibilities instead of results. “Managed the on-call rotation” versus “cut pages from 31 a week to 8”.
• A portfolio link that needs a password or leads to a site that is not finished.
• A one-size summary. Two lines, rewritten for each application, or none.
• The same page for every posting. A PM resume for a payments company and one for a healthcare company should not share a skills section. The method for tailoring each copy is in how to match your resume to a job description.

FAQ

Is a tech resume different from a software engineer resume? The format is the same. The content differs in what the reader scans for: a PM is screened on outcomes and discovery, an SRE on reliability and cost, a designer on the portfolio. Software engineers have their own conventions for projects and open source; see the software engineer resume guide.

How long should a tech resume be? One page through your first eight to ten years. Senior people with a long product or systems history can use two.

Do I need a portfolio? Designers, yes, without exception. Analysts and QA engineers benefit from a small GitHub. PMs and sysadmins can do without one, though a public product or a script repo never hurts.

Should I list soft skills? Only the ones the posting names, and show them in a bullet rather than a list: “ran 26 blameless post-mortems” proves communication better than the word does.

If this guide helped, star Resume Matcher on GitHub. Saurabh Rai builds it; follow him on GitHub, X and LinkedIn.