QA Manager Resume: Complete 2026 Guide

From the author

Emmanuel Gendre, ex-Google recruiter

My experience with QA Manager resumes

Twelve years in tech recruiting, including a long stretch at Google, and the QA Manager resume has a recognizable failure mode: it reads as a senior QA Engineer with one extra bullet about "mentoring juniors." Hiring directors and VPs of Engineering can spot it instantly. What they want is a program leader: the 20-person QA org you built and grew, the release-gate process you defended at exec reviews, the vendor relationship you managed across three offshore teams, the audit you led through an ISO 9001 recertification, the defect-escape rate you held below 1% across four product lines. None of that lands when the resume reads like an individual contributor with a manager title.

What hiring teams actually want in 2026 is the program story behind the team. A QA Manager resume reading as "managed QA team, ran sprints, owned JIRA" without an org size you grew, a release process you owned, or a defect-escape number you defended gets dropped before any conversation happens.

That gap is exactly what this guide closes. Five sections decide whether the QA Manager screen even starts, and the rest of this guide goes through them one at a time. The single goal: interviews back on the calendar, regardless of how soft the market feels right now.

Want the rewrite done for you? My Tech Resume Writing Service rebuilds the page from a blank file. Already have a draft and just want trained recruiter eyes on it? Drop it into the free review; every one passes through me directly and the notes come back from me.

Time to get your QA Manager resume opening calls instead of getting filtered. Let's start.

What the QA Manager resume guide covers

How I rewrite a QA Manager resume

A QA Manager resume crosses my desk regularly, through both the resume writing service and the free reviews. The pattern holds: roughly nine-tenths of the page contributes nothing, and the decision rides on five sections only. Going solo? Concentrate effort on those five, leave everything else alone.

Each step has a self-contained section below. Move through them sequentially, apply the edits as you go, and the resume you end up with reads as a different document entirely. The structure:

Want the method behind it? Here's how I rewrite resumes, laid out in full.

Step 1 · QA Manager Resume Format

The format to use for an
QA Manager resume

Knock this one out first: the ATS has to be able to ingest the page.

Most online advice on layouts is noise. The work boils down to one thing: a text parser has to pick up your content and structure exactly as you wrote them, with nothing dropped along the way.

Keywords matter for filtering further down the funnel (that's Technical Skills, Step 5), but parsing failures are what eliminate 95% of resumes before anyone reads a word.

Three short rules cover most of it:

Use a text editor (Word, Google Docs)

An ATS pulls text and nothing else. If the file isn't actually text on the page, the parser comes back empty-handed. Lay the resume out in Canva or Illustrator and every line becomes a flat raster image, so the automation frameworks and CI tools you spent hours listing simply vanish. From the parser's view, you submitted a blank document.

Single column, plain layout

Pull every column, sidebar, table, and image out of the layout. ATS engines in 2026 still chew them up, and this is the single most common parsing failure I catch in reviews (about three drafts in ten land here). Switch to a clean single-column layout and most of the parsing damage corrects itself.

Simple section titles

Use Profile Summary, Technical Skills, Work Experience, Education. Not "Bugs I've Caught", not "What I Bring to Quality". ATS and recruiters both look for standard headings, and a clever label just drops you out of the bucket. Avoid fuzzy ones too: "Core Competencies" lives inside Profile Summary or Technical Skills; "Career Highlights" lives inside Profile Summary or Work Experience.

Unsure how your current PDF holds up under parsing? Run it through the ATS resume checker and look at the extracted output side by side with the page. When the extracted version comes out broken, the bullets aren't the problem, the layout is, and layout is most of how an ATS scores you.

Want a clean slate that parses correctly out of the box? Grab the QA Manager resume template, designed for exactly that.

Step 2 · QA Manager Profile Summary

Writing a profile summary
for a QA Manager

Whatever you've read elsewhere, no resume should skip the Profile Summary. Juniors included.

If yours is missing, or it's there but weak, fixing it is the biggest single win on the table today.

All the mechanics sit inside how recruiters screen resumes. Quick version: a recruiter runs your resume twice. Pass one prunes the pile to anyone who looks credible for the role. Pass two distills that group into the actual shortlist for interviews.

Pass one is the punishing one: a recruiter cycles through file after file at a sprint, spending only seconds on each. That is where the well-known "10-second screen" stat comes from.

The Profile Summary is your only opportunity to land every cue a recruiter looks for inside that tight window. Stick it and the rest of the page gets opened; whiff it and nothing else carries weight.

Every bullet has a defined role. Below is the playbook I use when rewriting a QA Manager profile summary: what each line is on the hook for, plus a worked example tied to a real product.

Target job title, overall experience & product scope

Bullet 1 sets the marker: the role you're aiming at, your seniority, plus the org size and product breadth (engineer count under you, product lines covered, MAU or revenue scope). Add a regulated industry (fintech, healthcare, e-commerce) and a recognized employer if either lifts weight. Read this sentence as the page's top headline: a recruiter clocks it before anything else, and on rushed days it is sometimes the only line they reach.

Info for recruiters Target job title Years of experience Org size & product breadth Domain & employer

Example Senior QA Manager 12 years 20-engineer QA org, B2C SaaS, 5M MAU ISTQB Advanced + CSM, e-commerce

Domain expertise

Bullet 2 covers your domain expertise: the slots that make up the QA Manager role profile (laid out in Step 3, QA Manager Work Experience). For this role those slots are quality strategy and roadmap, QA org design and hiring, test process and methodology, release quality gates and go/no-go authority, and quality metrics and executive reporting. A non-technical screener walks that scorecard line by line and ticks off your entries. Treat this bullet as your own scorecard and leave no row empty.

Info for recruiters Quality strategy & roadmap QA org design & hiring Test process & methodology Release quality gates & go/no-go Quality metrics & exec reporting

Example 3-year quality roadmap, 4 product lines Hired 12 engineers, 88% retention 24 months Risk-based test management, ISTQB-aligned Release-gate authority, weekly go/no-go Quality scorecard reported to VP weekly

Your tech stack

Bullet 3 names your daily toolset: the test management platform, the methodology, the certification, the release-gate framework, and the reporting tool. The full inventory lands further down under "Technical Skills" (covered in Step 5, QA Manager Technical Skills); up here you only call out the daily drivers. For a QA Manager that means: test management, methodology, certification, gate framework, and reporting.

Info for recruiters Test management platform Methodology Certifications Release-gate framework Reporting & dashboards

Example Jira + TestRail + Xray, Allure Risk-based, BDD, shift-left, ISO 25010 ISTQB Advanced, CSM, PMP Quality scorecards, exit criteria, RACI Power BI, Tableau, Looker

Collaboration

Bullet 4 covers your cross-functional partnership. A QA Manager sits between Engineering leadership (who owns delivery), Product (who owns the roadmap), DevOps and SRE (who run the pipeline you gate), Customer Support (who feeds you real-world defect signal), Finance (who approves QA headcount and tool budget), and the audit team (who watches your compliance evidence). A hiring director checks whether you carry those relationships cleanly, so name the partner teams and the touchpoints you owned.

Info for recruiters Partner teams Release-gate authority Budget & headcount ownership

Example Engineering Leadership Product Management DevOps & SRE Customer Support Finance & Audit

Leadership

Bullet 5 surfaces your people and program leadership. This is where a QA Manager separates from a senior QA Engineer with a title bump. Leadership shows up in the org you built (engineers hired, retention rate held), the QA career ladder you defined, the offshore vendor relationship you managed, and the cross-functional reviews you chair: release gate, audit prep, capacity planning, and quality budgeting.

Info for recruiters Engineers hired & retention rate QA career ladder you authored Vendor + audit reviews you chair

Example Hired 12, retained 88% over 24 months QA career ladder + interview loop owner Release-gate & audit-prep review chair

QA Manager Profile Summary Example

Senior, 20-engineer QA org, B2C SaaS (web + iOS + Android, 5M MAU)

Profile Summary

Senior QA Manager with 12 years leading a 20-engineer QA org on a B2C SaaS platform across React web, native iOS, and Android (5M MAU), ISTQB Advanced + CSM.
Strong on Quality Strategy & Roadmap, QA Org Design & Hiring, Test Process & Methodology, Release Quality Gates & Go/No-Go, and Quality Metrics & Executive Reporting.
Day-to-day across Test management (Jira + TestRail + Xray, Allure), Methodology (risk-based, BDD, shift-left, ISO 25010), Certifications (ISTQB Advanced, CSM, PMP), Gate framework (quality scorecards, exit criteria, RACI), and Reporting (Power BI, Tableau, Looker).
Cross-functional partner across Engineering Leadership, Product, DevOps and SRE, Customer Support, and Finance and Audit, owning the quality program that cut production defect escape rate from 3.2% to 0.6% across four product lines.
Built a 20-engineer QA org with 88% retention over 24 months, authored the QA career ladder and interview loop, chairs the release-gate and audit-prep reviews, and coaches managers through their first quality program rollout.

Want to go deeper on this one? I cover it end to end in my guide on how to write a killer profile summary.

Want a recruiter's read on your QA Manager resume?

Weeks of applying and no interviews, no feedback.
No company owes you the reason, so you're stuck guessing what's off in the draft. Keep guessing, or hand it to someone who screened thousands of QA Manager resumes at Google.

Let me pull it apart for you.

I'll run a simulated recruiter screen on your QA Manager resume and send back a tight list of what to fix. Free, within 12 hours.

Want to read more first? See how the resume review works →

Step 3 · QA Manager Work Experience

Work experience on an
QA Manager resume

Now back into round two. This is the section that determines whether you get the call at all, and a recruiter actually slows down here. Even so, 95% of the decision still comes from your most recent role.

The logic is simple. Your current job is the truest signal of how you operate today, what you actually run hands-on, and where your seniority genuinely sits. To turn the screen toward an interview, that role has to cover every line in the full QA Manager role profile, one bullet per area you already named in the Profile Summary's Domain Expertise block.

Quality Strategy & Roadmap

Most QA Manager resumes stop at "ran QA for product X" right here. Hiring directors want the strategic judgment behind it: the multi-quarter quality roadmap you authored, the test pyramid you reset, the automation-versus-manual ratio you defended at the leadership review. Name the roadmap, the decision, and the outcome you owned.

Techniques Multi-quarter quality roadmap Risk-based test prioritization Test pyramid reset & rebalancing Automation-vs-manual ratio defense

Tools Confluence, Notion, Miro Jira Roadmaps, Aha! ISO 25010, ISTQB syllabus

Metrics Roadmap initiatives shipped Quality budget vs forecast Automation ratio trend

QA Org Design & Hiring

This is where mid-level candidates stay vague. Show that you actually built the team: the engineers you hired, the retention rate you held, the interview loop you designed, the QA career ladder you authored, the offshore-onshore split you balanced. Name the org size, the retention number, and the hiring outcome.

Techniques QA career ladder design Interview loop & rubric ownership Onshore / offshore team balance Performance review framework

Tools Greenhouse, Lever, Ashby Lattice, 15Five, CultureAmp Workday, BambooHR

Metrics Engineers hired per year 12-24 month retention rate Time-to-productive-hire (days)

Test Process & Methodology

Hiring teams want a real process story, not hand-waving. Name the methodology you standardized across teams (risk-based test management, BDD program, shift-left quality), the playbook you authored, and the framework adoption rate you defended. A concrete cycle-time or coverage number lands every time.

Techniques Risk-based test management BDD / Specification by Example Shift-left quality program ISO 25010 quality model

Tools Cucumber, SpecFlow, Gherkin ISTQB syllabus & templates Atlassian Compass, Backstage

Metrics Methodology adoption % across teams Cycle-time variance Test coverage growth

Release Quality Gates & Go/No-Go

Two stakes here: the gate criteria you defined and the go/no-go authority you held. Show the release-readiness scorecard you built, the exit-criteria standard you defended at release reviews, the no-go call you made under pressure. A real defect-escape number you held lands hard.

Techniques Quality scorecards & exit criteria Release-gate authority (go/no-go) Change-board representation Rollback & canary review

Tools Jira release dashboards ServiceNow change boards PagerDuty, Opsgenie

Metrics Defect escape rate (%) Release cycle time Go/no-go calls held

Vendor & Outsourced QA Management

Prove you can run the contract. The offshore QA partner you onboarded and ramped, the crowdtest program you ran for device coverage, the SLA you set and held quarterly. Name the partner, the program scope, and the cost or coverage number you moved.

Techniques Vendor selection & RFP SLA / SOW negotiation Crowdtest program design Onshore + offshore split

Tools Testlio, Applause, Rainforest QA BrowserStack, Sauce Labs SAP Ariba, Coupa for contracts

Metrics Vendor QA cost per release SLA attainment % Device matrix coverage delivered

Quality Metrics & Executive Reporting

This is one of the clearest mid-versus-senior tells. Show the quality scorecard you built for the leadership team, the weekly defect-escape and MTTR dashboard, the board-deck section you owned every quarter. A real metric you reported and moved lands hard.

Techniques Executive quality scorecard DORA + QA metrics blend Trend reporting & root-cause review Cost-per-release modeling

Tools Power BI, Tableau, Looker Jira, TestRail, Allure dashboards Datadog APM, Sentry release health

Metrics Production defect escape rate MTTR for severity-1 defects Quality cost per release

Cross-Functional Partnership

Few things separate mid from senior as sharply as this. The release-readiness review you chair every Friday, the audit-prep working group you lead, the product-roadmap quality input you provide every quarter, the SRE partnership you maintain on incident review. Name the forum, the cadence, and a real outcome you drove.

Techniques Release-readiness review chair Audit-prep working group Roadmap quality input Incident review (SRE partnership)

Tools Asana, Linear, ClickUp Slack, Teams, Loom RACI templates, MoSCoW

Metrics Forums chaired per week Quality risks logged + closed Audit findings cleared

Coaching & QA Career Development

Companies hire QA Managers who actually grow people. The 1:1 cadence you held with every direct, the promotion case you wrote and won, the technical workshop series you started, the QA Engineer who became a senior on your watch. A real promotion or engagement number lands.

Techniques Weekly 1:1 cadence & growth plans Promotion case authoring Internal workshop series Certification sponsorship (ISTQB)

Tools Lattice, 15Five, CultureAmp Notion / Confluence growth pages Coursera, Udemy Business

Metrics Promotions per year Team engagement score Certifications earned in-team

Once you address all of the above, the most recent role lands at roughly eight to ten bullets. That depth is on target, not bloat, no matter what the single-page rhetoric on LinkedIn keeps repeating. Recruiters do not grade pages; two dense pages of real content win against a thin single page every time. The thing killing the screen is padding: lines that take up room without saying anything, and cutting padding is what the next section is entirely about.

Step 4 · QA Manager Bullet Points

Bullet points for an
QA Manager resume

On any rewrite, the bullet section consumes the largest share of my hours. The disciplined method I built to handle it, the Level System, came out of that work and now runs across every guide on the site.

The underlying base isn't fictional: it builds on Google's XYZ formula, then pushes further for power-electronics specificity. The mechanics in full live at how to write resume bullet points.

Best way in: pick any ordinary QA bullet and rebuild it one layer at a time. The framework runs 5 questions, and each answer adds the next layer of engineering depth onto the line.

Walking them in sequence drives the bullet out of generic description and into the framework, CI, and coverage specifics that hiring managers actually evaluate when picking the QA interview shortlist.

1 Task “What did I work on?” What you did
2 + Techniques “How did I do it?” How you did it
3 + Tools “What tools did I use?” Frameworks, data stores, infra
4 + Method “What method did I follow?” Named methodology
5 + Metric “What was the result?” Quantified impact

Level 1, Just the task. Pick one specific thing you actually built or owned. This is the base layer, not the final line. Plenty of QA Manager resumes never move past it, and that's a big reason so many get filtered before a screening call.

Level 1
Just the task

Led QA across a 20-engineer org on a B2C SaaS platform.
Level 2, Add the techniques. Name the specific engineering practices the work used: the testing types, rendering modes, scaling tactics, design patterns. This is where the bullet starts proving you understand how the work was done, not just that it shipped.

Level 2
+ Techniques

Led QA across a 20-engineer org on a B2C SaaS platform using risk-weighted regression and release-gate ownership.
Level 3, Add the tools. Drop in the named products and versions you used: the framework, the database, the build tool. Recruiters search resumes with technology queries, so the bullet stays invisible without the named stack.

Level 3
+ Tools

Led QA across a 20-engineer org on a B2C SaaS platform using risk-weighted regression and release-gate ownership in Jira and TestRail with weekly steering reviews.
Level 4, Add the method. Name the methodology, framework, or design pattern that guided the work: TDD, DDD, BDD, GitOps, MVVM, CQRS, progressive enhancement, and so on. The hiring manager is usually the one enforcing the methodology on the team, so naming yours shows you fit how they actually operate.

Level 4
+ Method

Adopted risk-based test management to lead a 20-engineer QA org on a B2C SaaS platform using risk-weighted regression and release-gate ownership in Jira and TestRail with weekly steering reviews.
Level 5, Add the metric. A number is what lifts a bullet into the top 1%. It pulls double weight: it shows the impact was real, and it shows you measured it on purpose. Skip the number and the line reads identical to every other candidate's.

Level 5
+ Metric

Adopted risk-based test management to lead a 20-engineer QA org on a B2C SaaS platform using risk-weighted regression and release-gate ownership in Jira and TestRail with weekly steering reviews, cutting defect escape rate from 3.2% to 0.6%.

For the full walkthrough, including the trick I use to extract numbers from work that looked unmeasured, see writing resume bullet points. Most QA Managers already have the data: production defect escape rate, release cycle time, MTTR for severity-1 defects, QA cost per release, engineer retention rate, audit findings cleared, vendor SLA attainment, releases shipped per quarter. It just never made it onto the page.

Step 5 · QA Manager Technical Skills

Technical skills for a QA Manager resume

The ATS parses your Technical Skills section, and some systems use it for keyword filtering. That's why it needs to echo the language on the job description you're targeting.

By now, though, we're down to the fine details. Nailing this section gives you a nudge through filtering and screening, but the real weight is carried by your Profile Summary, Work Experience, and Bullet Points.

Still, the skills and keywords accumulate over the whole resume, so it pays to know what an ATS and a recruiter both watch for. That's why a separate page exists covering every QA Manager skill that matters, technical and soft, with a built-in keyword parser that tunes it to a specific posting.

Test Management & Reporting

Test management: Jira + TestRail, Zephyr, qTest, Xray, TestLink Reporting: Allure, ReportPortal, Power BI, Tableau, Looker Docs & ADRs: Confluence, Notion, Backstage, Atlassian Compass Scorecards: quality dashboards, executive briefings, DORA + QA blend Traceability: requirements-to-test linkage, audit evidence trails Defect tracking: Jira workflows, severity / SLA frameworks
QA Process & Methodology

Frameworks: ISTQB, ISO 25010, ISO 9001, TMMi, Test Pyramid Strategy: risk-based test management, shift-left quality, exit criteria BDD & spec: Cucumber, SpecFlow, Gherkin, Specification by Example Agile: Scrum, SAFe, Kanban, sprint quality routines Certifications: ISTQB Advanced, CSTE, CSM, PMP, Six Sigma Compliance: SOC 2, HIPAA, PCI DSS, GDPR test mandates
Automation Oversight

UI: Selenium, Cypress, Playwright, WebDriverIO, TestCafe API: Postman, REST Assured, Karate, Pact, SoapUI Mobile: Appium, Espresso, XCUITest, Detox, BrowserStack Non-functional: JMeter, k6 oversight, Axe / WCAG, OWASP ZAP Patterns: Page Object Model, BDD, data-driven, contract testing Languages reviewed: JavaScript / TypeScript, Python, Java
Release Governance & CI/CD

CI / CD: Jenkins, GitHub Actions, GitLab CI, CircleCI, Buildkite Change governance: ServiceNow, Jira Service Management, RFC boards Gates: quality scorecards, go/no-go criteria, exit-criteria templates Release health: Sentry, Datadog APM, PagerDuty, Opsgenie Feature flags: LaunchDarkly, Split, ConfigCat, Unleash Audit prep: ISO 9001, SOC 2 evidence collection
People & Program Management

Hiring: Greenhouse, Lever, Ashby, interview-loop & rubric design Performance: Lattice, 15Five, CultureAmp, calibration cycles Program tracking: Asana, Linear, ClickUp, Smartsheet Vendor management: Testlio, Applause, Rainforest QA, RFP / SOW Budgeting: SAP Ariba, Coupa, headcount & tool-cost planning Career growth: QA ladder, ISTQB sponsorship, 1:1 cadence, growth plans

Stop guessing. Ask a recruiter directly.

You now have the format, the profile summary template, the role profile, the bullet system, and the skills categories. All that's left between your draft and the interview is a set of eyes that screened thousands of QA Manager resumes telling you what to fix.

That's the free review.

Send the draft over. Back comes a simulated recruiter screen, a graded checklist, and a specific action list. Free, within 12 hours.

Want to read more first? How the resume review works →

Frequently asked

QA Manager resume FAQ

How long should a QA Manager resume be?

Maps to the size of the org you have led and the breadth of the program behind you. Below 8 years, a single page usually fits. At senior QA Manager or QA Director, with a 15-30 person QA org you have built, multiple product lines under your gate, a vendor program you have run, ISTQB or CSM credentials, and a defect-escape number you defended at the board, two pages is the correct call. The "one-page rule" from generic career advice doesn't apply to QA management. Padding hurts, but so does compressing a decade of quality program work into a single sheet. My tech resume length framework grows with seniority instead of locking to a page total.

Should it be one page?

Not by default. The real question is content density. First-time QA Managers fit on one page because there is not enough program history to fill more. At senior level, with a 20-person QA org you have built, a quality program you have run across multiple products, a vendor relationship you have managed, and a release-gate process you have defended at exec reviews, forcing it onto one page deletes the exact evidence that would open the screening call.

What is the most important section?

Your most recent role, hands down. Roughly 95% of the screening conversation comes from that one role, because hiring teams open it first to check the org size you have led, the product breadth (web, mobile, API, multiple product lines), the release cadence you have held, and the defect escape rate you have defended. The profile summary is second only because it sits above and gets read on the way down.

How do I get my resume past ATS?

Keep it single-column: drop the header icons, sidebars, and images, use plain section titles (Profile Summary, Core Competencies, Work Experience, Education), and export to PDF instead of DOCX. Then run it through my free ATS parser tool and check it is pulling out the test management platform, the methodology, and the certification. If "TestRail" or "ISTQB" or "risk-based testing" vanishes from the output, the layout is what is broken, not the content.

What keywords should I include?

For 2026, the ones you can not skip are a test management platform (Jira + TestRail, Zephyr, or qTest), a methodology (ISTQB, risk-based testing, or shift-left), a release-gate framework (go/no-go criteria, exit criteria, quality scorecards), a CI / governance system (Jenkins, GitHub Actions, GitLab CI, change boards), and a certification (ISTQB Advanced, CSTE, or CSM). Strong supporting keywords are quality strategy, defect escape rate, release cycle time, QA cost-per-release, vendor management, hiring, and capacity planning. Senior candidates add terms like quality program ownership, audit defense (ISO 9001, SOC 2), executive reporting, and budget ownership where relevant. The full list of QA Manager resume skills, ranked by demand, includes a bullet example for each.

Do I need a GitHub or portfolio link?

GitHub matters less for QA Manager than for hands-on QA Engineer. What lands instead is conference talks and writeups: STARWest, EuroSTAR, Agile Testing Days carry weight in this niche. For senior managers, the orgs you built, the release-gate processes you owned, and the defect-escape numbers you held at past employers carry the proof, so LinkedIn plus a one-paragraph program summary per role covers it. ISTQB Advanced, CSM, or PMP certifications are worth mentioning when present.

Should I list ISTQB, CSM, and PMP if I have all three?

List all three when they are current and a real reflection of how you operate. ISTQB Advanced signals QA depth, CSM signals delivery process, PMP signals program scale. The combination tells a hiring manager you can sit across QA strategy, agile execution, and large-program oversight. Where it backfires: stale certifications (expired CSM you have not renewed, an ISTQB Foundation from 2014) read worse than not listing them. If a cert is current and earned, list it.

How long should my profile summary be?

Target five bullets, treat six as the hard cap. A paragraph asks a hiring manager to read carefully inside a window that exists only for scanning, which never happens on a first pass. As bullets, they pattern-match you against the org size, the methodology, and the certifications in under a second and decide whether the page deserves more attention.

Who wrote this

Built by an ex-Google recruiter

Emmanuel Gendre

Former Google recruiter · 12 years · 1,500+ tech resumes rewritten

I screen QA Manager resumes the same way I did at Google: against the role profile, against the JD, and against the bar real hiring managers set. Everything in this guide is the field manual I use with my own clients.

Read my full story →

More resources

Other QA Manager Resume Resources

Service

QA Manager Resume:
The Complete 2026 Guide

My experience with QA Manager resumes

How I rewrite a QA Manager resume