IR Engineer Resume: Complete 2026 Guide

From the author

Emmanuel Gendre, ex-Google recruiter

My experience with IR Engineer resumes

Twelve years recruiting in tech, with a long run inside Google, and the IR Engineer resume is the one where strong defensive work most often reads as a stack inventory on the page. The actual job lives at the seam between every team that builds something and the threat models that should already be in their heads: the architecture review, the detection rule, the incident bridge at 3 a.m., the audit defense. The drafts that hit my desk hand it over as a tool list.

What hiring teams in 2026 want is the program behind that tool list, and a IR Engineer resume reading as "Splunk, Tenable, Burp" without an attack surface you reduced, a high-sev CVE class you retired, or a real incident you led never makes it to a screening call.

Closing that gap is what this guide is for. We walk the 5 sections that decide a IR Engineer screen, with one outcome in mind: screening calls landing in your inbox again, market softness or not.

Want it written for you? My Tech Resume Writing Service rebuilds it from a blank page. Already have a draft? Send it in for a free review; the notes come back from me.

Let's put your IR Engineer resume back on recruiters' desks. Ready?

What the IR Engineer resume guide covers

How I rewrite an IR Engineer resume

IR Engineer drafts hit my resume writing service intake most weeks, and I rework each line until the IR work shows clearly to a recruiter who has never read a memory dump. The bit nobody says out loud: only a small handful of sections actually decide whether the screening call lands. Doing the rewrite solo? Sort these 5 first. The rest of the page barely moves the dial, so we keep that part brief.

We walk each one below, in order. Treat it as a checklist, run top to bottom, and the resume that comes out the other side is far stronger. Here's the structure:

Want to see the full method? My step-by-step tech resume rewrite process covers everything else.

Step 1 · IR Engineer Resume Format

The format to use for a
IR Engineer resume

Easy first step: a layout an ATS handles cleanly without crashing on it.

Nothing complicated at this stage, whatever the internet keeps trying to sell you. The aim: the software hands your content and structure back out to the reviewer in the same shape you typed them in.

Keyword work happens later, in the filtering step (Technical Skills, Step 5). Right now: when the parser fails on the file, you're already eliminated from 95% of openings before any reviewer touches the page.

Just 3 rules at this step:

Use a text editor (Word, Google Docs)

ATS systems read text, not the rendered picture of it. Put the resume through Canva, Figma, or any other design tool, and the words leave the file as a flat image. The parser sees nothing where your security stack should sit, and the application that reaches the recruiter shows up blank.

Single column, plain layout

Skip two-column templates outright. Sidebars, tables, and icons fall into the same bucket. Even in 2026, parsers still mangle every one of them, and it's the single biggest reason resumes fail the scan, on the order of one in three drafts that hit my desk. Move to a clean one-column layout flowing top to bottom, and most of the failures vanish.

Simple section titles

Label them Profile Summary, Technical Skills, Work Experience, Education. Not "Security Posture", not "Compliance Track". ATS parsers and human readers both look for those exact standard names; a creative rename pulls you straight out of the running. Fold any fuzzy headings into the same buckets: "Core Competencies" goes under Profile Summary or Technical Skills, and "Selected Projects" under Work Experience.

Want to see how yours fares? Drop it into the ATS resume checker and read what the parser hands back. If the output comes back garbled, the layout broke the read, not the words you typed, which is the whole story behind how ATS systems really work.

Starting from a blank file and want clean parsing on save one? Begin from the IR Engineer resume template.

Step 2 · IR Engineer Profile Summary

Writing a profile summary
for an IR Engineer

Plenty of IR Engineers skip past the Profile Summary as filler. It runs the other way: this is the first block a recruiter lands on the page.

If yours is thin or missing entirely, fixing it is the fastest gain you can put on the page today.

I broke the mechanics down in how recruiters screen resumes. Short version: a two-pass read. Pass one drops anyone who doesn't register as a match for the role; pass two builds the shortlist out of whoever survives.

That first pass is the recruiter ripping through the stack at seconds per resume, which is where the "10-second screen" phrase comes from.

The Profile Summary is your one window to land the exact details a recruiter screens for inside those seconds, which is what earns the page a deeper read.

Each bullet has one job. Below: the order I work through, what each bullet carries, and a worked example for an IR Engineer profile summary.

Target job title, overall experience & IR-program scope

Bullet 1 sets the marker: the role you're aiming at, your seniority, plus the IR program you run (organization size, on-call model, regulated industry). Drop in your IC role on a recent high-severity incident and a known 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 Security-program scope Compliance frame

Example Senior IR Engineer (DFIR) 7 years IR for a 12,000-employee fintech

Domain expertise

Bullet 2 covers your domain expertise: the slots that make up the Security role profile (laid out in Step 3, IR Engineer Work Experience). For this role those slots are CI/CD security integration, secrets management and key rotation, container and supply-chain security, infrastructure and cloud security, and policy-as-code and compliance automation. 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 CI/CD security Secrets & PKI Supply chain IaC & cloud security Policy as code

Example SAST/SCA in CI Vault secrets program Cosign & SBOM Checkov on IaC OPA admission

Your tech stack

Bullet 3 names your daily stack: the scanners, the secrets manager, the policy engine, and the cloud-security tooling you actually run. The full inventory lands further down under "Technical Skills" (covered in Step 5, Security Engineer Technical Skills); up here you only call out the daily drivers. For a IR Engineer that means: SAST/SCA scanners, secrets layer, container and supply-chain tooling, IaC scanners, and the policy-as-code engine that backs admission.

Info for recruiters Scanners Secrets Supply chain IaC scanning Policy

Example Snyk, Semgrep, Trivy Vault, AWS Secrets Manager Cosign, Syft, in-toto Checkov, tfsec OPA, Kyverno

Collaboration

Bullet 4 covers your cross-functional partnership. Security work sits between Platform Engineering, Application Engineering, SecOps, and Compliance; the controls you wire in are what every service team ships through, so the threat model, the security review, the audit evidence, and the developer-friction feedback loop all live across those handoffs. A hiring manager checks you carry the security side cleanly without slowing down delivery, so call out the partner teams and what they get from your program.

Info for recruiters Partner teams Security contracts Audit support

Example Platform Engineering App Engineering SecOps Compliance SOC 2 evidence

Leadership

Bullet 5 surfaces your technical leadership. Even pure-IC Security Engineers have a line worth showing here. Leadership runs through the security program and the people: chairing threat-modeling sessions, owning the secrets and policy standard, running secure-code office hours, and coaching engineers new to shift-left practices.

Info for recruiters Standards you define Engineers you coach Reviews you chair

Example Threat-modeling reviews Secrets & policy standard Secure-code office hours

IR Engineer Profile Summary Example

Senior, IR for a 12,000-employee fintech

Profile Summary

Senior IR Engineer (DFIR) with 7 years running digital forensics and incident response for a 12,000-employee fintech across hybrid AWS and on-prem.
Strong on Major Incident Response & Command, Digital Forensics, Malware Analysis & Reverse Engineering, Threat Intelligence & TTPs, and Containment & Eradication.
Day-to-day across SIEM (Splunk ES, Sentinel), EDR (Crowdstrike Falcon, SentinelOne), Forensics (Volatility, Velociraptor, KAPE), Malware analysis (Ghidra, IDA Pro, Cuckoo), and Cloud forensics (CloudTrail, Cado, GuardDuty).
Cross-functional partner working with SOC tier-2/3, Legal, and Executive teams, taking a major incident from page to containment to eradication with court-admissible evidence preserved.
Authors the IR playbook library, runs quarterly executive tabletops, owns the IR on-call rotation, and mentors SOC tier-3 analysts on investigation craft.

Want more depth? My fuller writeup on how to write a killer profile summary walks the same idea line by line.

Want a recruiter's read on your IR Engineer resume?

Months in the queue with zero interviews, zero feedback.
No employer owes you the reason, leaving you to guess what's off about the draft. Keep guessing, or hand it to someone who screened thousands of Security and security-engineering resumes at Google.

Pass it over and I'll take it apart.

I'll run a simulated recruiter screen over your IR Engineer resume and send back a short list of what to repair. Free, inside 12 hours.

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

Step 3 · IR Engineer Work Experience

Work experience on a
IR Engineer resume

This is where the second pass actually plays out, the last gate before an interview hits your inbox. The recruiter slows down right here, and even then your current role still drives around 95% of the decision.

Makes sense: nothing tells a hiring team what you can run in production right now the way your current job does. To clear that "yes", this section has to walk the full IR Engineer role profile, one bullet per slot you listed in Domain Expertise above. Every bullet has to come off something you actually held in production, not a Jira card that wandered past your queue.

Major Incident Response & Command

You take command when a real breach is unfolding. The response is chaos without someone running it, so leading a Sev-0 cleanly tells a hiring manager they can put you in the chair. Talk about how you used incident command and severity declaration, against NIST 800-61, to lead Sev-0 events and cut MTTR.

Techniques Incident command (IC role) Severity declaration Bridge facilitation Executive briefings

Tools PagerDuty, FireHydrant, Rootly NIST 800-61, SANS PICERL Slack War Rooms

Metrics Major incidents led as IC MTTR Severity-0 events handled

Digital Forensics (Memory, Disk, Cloud)

You reconstruct exactly what an attacker did, from the artifacts they left. The truth of a breach lives in memory, disk, and control-plane logs, so hiring managers want forensics you actually ran. Show them how you used live memory forensics and disk timelining, with Volatility and Velociraptor, to recover artifacts and surface IOCs.

Techniques Live memory forensics Disk imaging & timeline Control-plane log analysis Artifact triage

Tools Volatility, Rekall Velociraptor, KAPE, FTK EnCase, X-Ways, Autopsy

Metrics Hosts triaged Artifacts recovered IOCs surfaced

Malware Analysis & Reverse Engineering

You tear malware apart to see what it really does. YARA rules published and IOCs operationalized are concrete, so hiring managers want samples you reversed, not "familiar with Ghidra". Point out how you used static disassembly and sandbox analysis, in Ghidra and Any.Run, to reverse samples and publish YARA rules.

Techniques Static disassembly Dynamic / sandbox analysis YARA rule authoring Packer & obfuscation defeats

Tools Ghidra, IDA Pro, Binary Ninja x64dbg, OllyDbg, Frida Cuckoo, Any.Run, Joe Sandbox

Metrics Samples reversed YARA rules published IOCs operationalized

Threat Intelligence & TTPs

You map an attacker's moves to known techniques and hunt the rest. Knowing the actor's playbook tells you where they go next, so hiring managers want intel that drives detection. Mention how you used ATT&CK mapping and kill-chain analysis, with MITRE Navigator and OpenCTI, to cover TTPs with detection and disrupt campaigns.

Techniques ATT&CK technique mapping Actor attribution Kill-chain analysis Intel-driven hunting

Tools MITRE ATT&CK Navigator MISP, OpenCTI, ThreatConnect VirusTotal Intelligence, Mandiant

Metrics Actors tracked TTPs covered by detection Campaigns disrupted

Incident Containment & Eradication

You cut the attacker off and clear them out for good. Hiring managers look here to see whether you contain fast, or leave a door open for re-infection. Walk them through how you used blast-radius mapping and credential rotation, with Crowdstrike RTR and Tines, to cut time-to-containment and stop re-infection.

Techniques Blast-radius mapping Network segmentation Credential rotation IOC blocking at scale

Tools Crowdstrike RTR, MDE Live Response AWS IAM, Okta lifecycle Tines, Splunk SOAR

Metrics Time-to-containment Dwell time reduced Re-infection rate

Postmortem & Lessons Learned

You turn a breach into controls that stop the next one. An incident you don't learn from just recurs, so hiring managers read preventive controls shipped as real closure, not a doc. Spell out how you used blameless postmortems and root-cause analysis, in Confluence and Jira, to ship preventive controls and cut repeat incidents.

Techniques Blameless postmortems Timeline reconstruction Root-cause analysis (5 Whys) Control-gap closures

Tools Confluence, Notion Jellyfish, Howie Jira, ServiceNow IRM

Metrics Postmortems published Preventive controls shipped Repeat incidents down

Tabletops, Playbooks & IR Readiness

You get the org ready before the breach, not during it. Two things ride on it for a hiring manager: playbooks people can follow under pressure, and readiness gaps you found in a drill. Lay out how you used playbook authoring and executive tabletops, with Atomic Red Team and CALDERA, to run drills and close readiness gaps.

Techniques Playbook authoring Executive tabletops Engineering tabletops Readiness drills

Tools Atomic Red Team, CALDERA SCYTHE, AttackIQ FireHydrant, Rootly drills

Metrics Tabletops/quarter Playbooks maintained Readiness gaps closed

Tooling & Workflow

You build the tooling that makes the next response faster. Teams keep the responders who leave reusable playbooks behind, not the heroes who improvise every time, so this signals maturity. Tell them how you built IR runbooks and response automation, in Git with Python, to speed the next response and cut setup time.

Techniques Secure-by-default templates Internal CLI / runbooks Inner sourcing Self-serve docs

Tools Git, GitHub Bash, Python, Go Backstage TechDocs

Metrics Templates maintained PR cycle time Secure-onboarding ramp cut

Done right, your current role can easily run to 8 or 10 lines. Perfectly fine, whatever the one-page mantra LinkedIn keeps pushing. Recruiters don't care about length; two pages of real platform work beat one bloated page outright. What a recruiter will not read is empty filler. Cutting that is what comes next.

Step 4 · IR Engineer Bullet Points

Bullet points for a
IR Engineer resume

Bullet points carry the bulk of the rewrite, so I built them their own dedicated framework: the Level System.

Nothing magic about it: it picks up where Google's XYZ formula stops and adds a few tiers tuned for technical engineering resumes. The full breakdown lives in my guide on how to write resume bullet points.

Fastest way to learn it: take a flat Security-resume bullet and walk it up. There are 5 tiers in all; each one asks a single question, and the answer you give slides in as the next fragment of the bullet.

Climb all five and a bare "built a deploy pipeline" line turns into a shipped delivery platform with real numbers attached, which is the kind of line that puts a DevOps Engineer on the shortlist.

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

Level 1, Just the task. Open with a security program or control that was yours to ship across the company. This is the opening phrase, not the finale; most resumes stop right here on the bullet, which is exactly why so many wash out at this point.

Level 1
Just the task

Led the digital forensics and incident response function.
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
+ Engineering Techniques

Led the digital forensics and incident response function using live memory forensics and blast-radius containment.
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 the digital forensics and incident response function using live memory forensics and blast-radius containment on Volatility, Velociraptor, CloudTrail, and KAPE.
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 NIST 800-61 IR methodology to lead the digital forensics and incident response function using live memory forensics and blast-radius containment on Volatility, Velociraptor, CloudTrail, and KAPE.
Level 5, Add the metric. The number is the lever that pushes a bullet into top-tier territory. For Security work, reach for figures the business cares about: MTTR for high-sev CVEs cut, risky changes blocked, audits cleared, dwell time reduced, risk dollars retired. Skip the metric and the line sits flat alongside every other resume whose author stopped at "ran security scans".

Level 5
+ Metric

Adopted NIST 800-61 IR methodology to lead the digital forensics and incident response function using live memory forensics and blast-radius containment on Volatility, Velociraptor, CloudTrail, and KAPE, cutting incident MTTR from 14 days to 18 hours.

My longer piece on writing resume bullet points works the rewrite tier by tier and shows how to pull figures out of work that looked like it had none. Most IR Engineers already know the numbers; they sit in Splunk, the vuln-management dashboard, or the quarterly risk report. Nobody ever told them that MTTR for high-sev CVEs, detection coverage, audits cleared, dwell time reduced, and risk dollars retired belong on a resume.

Step 5 · IR Engineer Technical Skills

Technical skills for an IR Engineer resume

The Technical Skills section is where most ATS setups run their keyword filtering, so the wording here should mirror the JD you're after: identity platform, SIEM, EDR, vulnerability tooling, and cloud-security stack named, not just "Security" on its own.

This is the final 10%. Cleaning it up helps the resume slip past the automated screen and the recruiter's quick skim, but the real lift still comes from your Profile Summary, Work Experience, and Bullet Points upstream.

Either way, keywords compound across the page, and knowing the exact ones a parser and a recruiter look for is worth the time. The list below covers the IR Engineer must-haves the way recruiters in 2026 actually scan for them.

Incident Response

NIST 800-61 SANS PICERL PagerDuty, FireHydrant, Rootly Incident command (IC role) Severity declaration Blameless postmortems Tabletop facilitation
Digital Forensics

Volatility, Rekall Velociraptor, GRR KAPE, FTK, FTK Imager EnCase, X-Ways Autopsy, Sleuth Kit Plaso, log2timeline Sysmon, osquery
Malware Analysis

Ghidra, IDA Pro, Binary Ninja x64dbg, OllyDbg Cuckoo, Any.Run, Joe Sandbox Frida, Wireshark YARA, Sigma rule authoring PE analysis (CFF Explorer) Python, C, x86/ARM assembly
Threat Intel & TTPs

MITRE ATT&CK Navigator D3FEND, Diamond Model MISP, OpenCTI, ThreatConnect VirusTotal Intelligence Mandiant, Recorded Future Anomali, Crowdstrike Falcon X Atomic Red Team, CALDERA
Cloud Forensics & Tooling

AWS CloudTrail, GuardDuty, Detective Azure Sentinel, Defender for Cloud GCP Cloud Audit Logs, SCC Cado Response Splunk ES, Microsoft Sentinel Tines, Splunk SOAR, XSOAR Python, PowerShell, Bash

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 IR Engineer and DFIR resumes telling you what to fix.

That is the free review.

Drop the draft in. Back come a simulated recruiter screen, a graded checklist, plus a specific action list. Free, inside 12 hours.

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

Frequently asked

IR Engineer resume FAQ

How long should an IR Engineer resume be?

Just into the field, hold it to one page. Once you have led real high-severity incidents as IC, run live forensic acquisitions, reversed malware in a real engagement, and authored postmortems that drove control changes, two pages start earning their keep: the second sheet gets read when the IR work behind it actually holds up. The blanket one-page rule misses that a senior IR Engineer career covers a long line of incidents led, forensic findings recovered, and preventive controls shipped worth showing. Save three pages for staff or principal DFIR level where that track really fills them.

Should it be one page?

Comes down to what incidents are actually running with your name on them, not a fixed rule. New to the role: one page covers it. A few years in, with major incidents you led as IC, forensic findings you recovered, and YARA rules you published, squeezing it all onto a single sheet cuts the very numbers earning the screen. Operational scope beats page count on this resume.

What is the most important section?

Your current role, by a long way. Roughly 95% of the read sits there, since that is where the recruiter checks whether you have actually led incidents at the severity this team handles. The profile summary lands one beat earlier, and the recruiter uses that line as the lens over everything below.

How do I get my resume past ATS?

A plain layout: one column, no graphics, no sidebars, no icons. Use the standard labels (Profile Summary, Technical Skills, Work Experience, Education); export PDF, not DOCX. Then run the file through my free ATS parser tool and check that DFIR, Volatility, KAPE, Velociraptor, CloudTrail, MITRE ATT&CK, Ghidra, and the rest of your IR stack parse cleanly. If any of those drop out, the layout broke the read, not your keyword list.

What keywords should I include?

For a 2026 IR Engineer search the must-haves are an IR framework (NIST 800-61, SANS PICERL), forensic tools (Volatility, Velociraptor, KAPE, EnCase, X-Ways), an EDR with live-response capabilities (Crowdstrike, SentinelOne, Defender for Endpoint), a SIEM (Splunk, Sentinel), MITRE ATT&CK fluency, and at least one cloud-forensics workflow (CloudTrail + GuardDuty + Cado). Strong backups: malware analysis tools (Ghidra, IDA Pro, Cuckoo, Any.Run), YARA rule authoring, threat-intel platforms (MISP, OpenCTI), SOAR (Tines, XSOAR), and Python or PowerShell for scripting. The full list, each paired with a sample bullet, sits in the Technical Skills section above.

Should I lead with deep forensics or broad IR coordination?

Lead with whichever the JD emphasizes. A forensics-leaning posting (DFIR consulting, malware reversing, memory analysis) wants the deep technical work up front: the binaries you reversed, the memory analysis you ran, the YARA rules you published. An IR-coordination-leaning posting (incident commander, IR program manager, security operations leader) wants the leadership work up front: the incidents you led as IC, the tabletops you ran with the executive team, the playbook library you maintain. Pure DFIR roles default to forensics depth; in-house IR program roles default to coordination. A resume splaying both equally reads as junior; pick the spine.

Do I need DFIR certifications (GCFA, GCIH, GREM, GCFE) in 2026?

Yes, more than in other security disciplines. GIAC certs are the gold standard for DFIR: GCFA (Certified Forensic Analyst) for disk and memory forensics, GCIH (Certified Incident Handler) for IR command, GREM (Reverse Engineering Malware) for malware analysis, GCFE (Forensic Examiner) for Windows forensics, GNFA for network forensics. CompTIA CySA+ helps at entry. CISSP gives broader security context. Past 4-5 years on the job, the incidents you led and the malware you reversed outweigh the badge, but DFIR hiring leans more cert-friendly than other security specialties. Top-tier GIAC + matching production track is the strongest pairing.

How long should my profile summary be?

Five or six bullets, no more. A heavy paragraph forces slow reading at the moment the recruiter intends to skim, and on an IR Engineer role what they scan for is the identity platform, the SIEM and detection stack, the EDR, the compliance frame, and the program scope you cover. As bullets the recruiter can match you against the role at a glance and decide whether the rest of the page is worth more time.

Who wrote this

Built by an ex-Google recruiter

Emmanuel Gendre

1,500+ tech resumes rewritten · 4.9 on Fiverr from 419 reviews

Hi there! I'm Emmanuel, a tech recruiter with 12 years of experience, including many years at Google. I founded TechieCV to help candidates pass recruiter screens and land top-paying jobs. This guide is the process I use on real client resumes.

Read my full story →

More resources

Other IR Engineer Resume Resources

Service

IR Engineer Resume:The Complete 2026 Guide

My experience with IR Engineer resumes

How I rewrite an IR Engineer resume

The format to use for aIR Engineer resume

Use a text editor (Word, Google Docs)

Single column, plain layout

Simple section titles

Writing a profile summary for an IR Engineer

Target job title, overall experience & IR-program scope

Domain expertise

Your tech stack

Collaboration

Leadership

Profile Summary

Want a recruiter's read on your IR Engineer resume?

Work experience on aIR Engineer resume

Major Incident Response & Command

Digital Forensics (Memory, Disk, Cloud)

Malware Analysis & Reverse Engineering

Threat Intelligence & TTPs

Incident Containment & Eradication

Postmortem & Lessons Learned

Tabletops, Playbooks & IR Readiness

Tooling & Workflow

Bullet points for aIR Engineer resume

Technical skills for an IR Engineer resume

Incident Response

Digital Forensics

Malware Analysis

Threat Intel & TTPs

Cloud Forensics & Tooling

Stop guessing. Ask a recruiter directly.

IR Engineer resume FAQ

Built by an ex-Google recruiter

Tech Resume Writing Service

IR Engineer Resume Template

IR Engineer Resume Skills & Keywords

Incident Response Engineer Resume Metrics

Free ATS Checker

Incident Response Engineer Cover Letter

IR Engineer Resume:
The Complete 2026 Guide

The format to use for a
IR Engineer resume

Writing a profile summary
for an IR Engineer

Work experience on a
IR Engineer resume

Bullet points for a
IR Engineer resume