Study an illustrative Security Operations Center Analyst resume built around the decisions, technical depth, operating scope, and measurable outcomes expected in the role. Replace every sample employer, metric, and detail with your own verified experience.
San Francisco, CA | (415) 555-0148 | julian.mercer@email.com | linkedin.com/in/julianmercer
Professional Summary
Security Operations Center Analyst with 5+ years in 24x7 SOC environments handling SIEM alerts, threat triage, and incident escalation. Known for accurate severity calls, tight handoffs, and detection feedback that reduces analyst noise.
Professional Experience
SOC Analyst II
CrowdStrike, Austin, TX
Triaged 90+ daily SIEM and EDR alerts on rotating shifts, meeting a 15-minute initial-response target 96% of the time.
Investigated confirmed intrusions using host, DNS, and proxy evidence, escalating nine incidents with complete timelines.
B.S. in Cybersecurity, George Mason University, Fairfax, VA
Certifications
CompTIA CySA+ | Splunk Core Certified User
Illustrative sample resume. Company names and performance figures are examples to replace with your own verified information.
Writing strategy
How to write a Security Operations Center Analyst resume
A strong Security Operations Center Analyst resume makes ownership and outcomes easy to find. Show the problem, the action you personally drove, the scale or constraint, and the result. Use role-specific language only when the surrounding bullet proves that capability.
Lead with threat triage
Show where threat triage changed a customer, product, revenue, or operating result.
Prove investigation quality
Name the decisions, methods, systems, and constraints behind the result—not just the activity.
Quantify alert noise reduction
Use scale, speed, quality, adoption, or financial measures that a hiring team can evaluate.
Make ownership explicit
Separate what you personally led from what the wider team delivered and name key partners.
Security Operations Center Analyst summary examples
Keep your summary to two or three lines. Name your level, strongest area of ownership, and the outcomes you are equipped to improve.
General
Security Operations Center Analyst with evidence across SIEM triage, Splunk, Microsoft Sentinel, EDR investigation, and measurable business outcomes.
Execution
Security Operations Center Analyst experienced in Threat intelligence, Incident escalation, Phishing analysis, Log correlation, cross-functional delivery, and operating at scale.
Impact
Security Operations Center Analyst who connects threat triage and investigation quality to time to triage and escalation accuracy, incidents investigated and audit pass rate, false-positive reduction and alert volume.
Experience section
Security Operations Center Analyst experience bullet examples
Choose bullets that match your actual work. Replace every sample number with a result you can explain and defend.
SOC Analyst II impact
Triaged 90+ daily SIEM and EDR alerts on rotating shifts, meeting a 15-minute initial-response target 96% of the time.
Investigated confirmed intrusions using host, DNS, and proxy evidence, escalating nine incidents with complete timelines.
Wrote shift-handoff templates and runbooks for ransomware and credential-theft alerts adopted across three SOC teams.
Trained six new analysts on triage workflow and evidence standards, shortening their onboarding to independent shifts by two weeks.
Mapped 25 recurring alert types to MITRE ATT&CK techniques, helping detection engineers prioritize coverage gaps for the next quarter.
Ran monthly threat-hunting sessions on unusual PowerShell and login activity, surfacing three misconfigured service accounts for remediation.
SOC Analyst I impact
Monitored Splunk and Sentinel queues for managed-defense customers, escalating validated threats with clear impact statements.
Enriched indicators with threat-intelligence feeds, improving true-positive classification accuracy to 91% in QA reviews.
Documented 60+ closed investigations in the case system, passing 98% of internal quality audits.
Collaborated with customer IT teams on containment steps, helping isolate compromised endpoints in under 30 minutes.
Wrote customer-facing incident summaries for 20 managed-defense accounts, earning positive review notes on clarity from two client security leads.
Triaged phishing reports from customer mailboxes, analyzing 150 messages and sending confirmed indicators to detection engineers.
Documented repeatable triage steps for common login-anomaly alerts, cutting escalations that lacked evidence by about 20%.
Keywords and evidence
Skills and metrics to include
Prioritize skills that appear in the target job description and that your experience section can support with evidence. For a Security Operations Center Analyst, the strongest skill section balances domain judgment, execution, measurement, and cross-functional work.
Business impacttime to triage and escalation accuracy
Executionincidents investigated and audit pass rate
Quality and scalefalse-positive reduction and alert volume
LeadershipScope, stakeholders, adoption, and decision velocity
Hiring signals
What recruiters look for
Credible threat triage ownership
Hands-on investigation quality
Measured alert noise reduction
Clear progression and scope
Role-specific tools used in context
Claims that can be defended in an interview
Weak bullets versus stronger rewrites
Weak
Responsible for threat triage.
Stronger
Triaged 90+ daily SIEM and EDR alerts on rotating shifts, meeting a 15-minute initial-response target 96% of the time.
Why it works: Replaces a duty with scope, action, and a measured outcome.
Weak
Helped improve investigation quality.
Stronger
Investigated confirmed intrusions using host, DNS, and proxy evidence, escalating nine incidents with complete timelines.
Why it works: Shows the specific lever, operating context, and result.
Quality check
Common Security Operations Center Analyst resume mistakes
01
Repeating the job description
02
Listing tools without evidence
03
Using metrics with no baseline or timeframe
04
Hiding personal ownership
05
Overloading bullets with several unrelated outcomes
06
Copying illustrative employers or numbers
ATS-friendly checklistThe downloadable resume follows these rules.
Single-column reading order
Standard section headings
No tables, graphics, or skill bars
Selectable text in PDF and DOCX
Conventional dates and job titles
Keywords used in natural context
Frequently asked questions
Security Operations Center Analyst resume FAQ
How long should a Security Operations Center Analyst resume be?
Use one page when your most relevant experience fits without crowding. Two pages are reasonable for a senior candidate with substantial scope, but every bullet should still earn its place.
Which keywords belong on a Security Operations Center Analyst resume?
Mirror accurate language from the job description. Relevant examples include SIEM triage, Splunk, Microsoft Sentinel, EDR investigation, Threat intelligence, Incident escalation. Do not add a keyword unless your experience can support it.
What should a Security Operations Center Analyst quantify?
Quantify the measures closest to the role's decisions: time to triage and escalation accuracy; incidents investigated and audit pass rate; false-positive reduction and alert volume. Include the baseline or timeframe when it changes the meaning.
Should a Security Operations Center Analyst resume list tools?
Yes, when the tools are relevant to the target role. Place the most important ones in the skills section and show how you used them to make a decision, ship work, improve quality, or produce a measurable result.
Can I copy the employers and numbers in this example?
No. The employers, projects, and metrics are illustrative. Replace them with accurate details from your own work and keep only claims you can explain in an interview.
Write it well
Writing your own Security Operations Center Analyst resume