Key Takeaways

  • 75% of U.S. employers use automated applicant tracking systems to screen resumes before a human reviews them (Harvard Business School & Accenture, 2021)
  • The most common ATS failures are missing keywords, incompatible formatting, and incorrect file types
  • ResumeGeni scores your resume across 8 parsing layers — modeled on the same steps enterprise ATS platforms like Workday, Greenhouse, and Taleo use to evaluate candidates

How ATS Resume Scoring Works

Applicant tracking systems parse your resume into structured data — extracting your name, contact info, work history, skills, and education — then score how well that data matches the job requirements. Many ATS rejections happen because the parser couldn't extract critical fields, not because the candidate wasn't qualified.

LayerWhat It ChecksWhy It Matters
Document extractionFile format, encoding, readabilityCorrupted or image-only PDFs fail immediately
Layout analysisTables, columns, headers, footersMulti-column layouts break field extraction
Section detectionExperience, education, skills headingsNon-standard headings cause sections to be missed
Field mappingName, email, phone, dates, titlesMissing contact info is a common cause of immediate rejection
Keyword matchingJob-specific terms, skills, certificationsKeyword overlap affects recruiter search visibility and ATS scoring
Chronology checkDate ordering, gap detectionReverse-chronological order is expected by most ATS
QuantificationMetrics, numbers, measurable outcomesQuantified achievements help human reviewers and some scoring models
Confidence scoringOverall parse quality and completenessLow-confidence parses get deprioritized in results

Frequently Asked Questions

Is ResumeGeni free?
Yes. ResumeGeni is currently in beta — ATS analysis, scoring, and initial improvement suggestions are free with no signup required. Full guidance and saved reports may require a free account.
What file formats are supported?
PDF, DOCX, DOC, TXT, RTF, ODT, and Apple Pages. PDF and DOCX are recommended for best ATS compatibility.
How is the ATS score calculated?
Your resume is processed through an 8-layer parsing pipeline that extracts structured data the same way enterprise ATS platforms do. The score reflects how completely and accurately your resume can be parsed, plus how well your content matches common ATS ranking criteria.
Can ATS read PDF resumes?
Yes, but not all PDFs are equal. Text-based PDFs parse well. Image-only PDFs (scanned documents) and PDFs with complex tables or multi-column layouts often fail ATS parsing. Our analyzer will flag these issues.
How do I improve my ATS score?
Focus on three areas: use a clean single-column format, include keywords from the job description naturally in your experience bullets, and ensure all sections (contact, experience, education, skills) use standard headings.

ATS Guides & Resources

Built by engineers with 12 years of experience building enterprise hiring technology at ZipRecruiter. Last updated .

Security Engineer - Argentina

Senseon · Argentina

SenseOn is building the next generation of security operations, one where AI doesn't just assist analysts but actively drives detection engineering. We're looking for a Security Engineer who can do two things simultaneously: write high-quality detection rules that stop real adversaries today, and help us build the platform infrastructure that lets AI write and evolve those rules tomorrow.

The threat landscape is shifting in kind. Adversaries are increasingly using AI to accelerate attack development, automate reconnaissance, generate convincing phishing at scale, and adapt tradecraft faster than traditional detection cycles can follow. We need someone who understands this emerging class of AI-driven attacks, and can build detections that are specifically designed to identify their signatures: anomalous automation patterns, LLM-generated content in phishing chains, unusually fast and broad enumeration, and AI-assisted lateral movement. Detecting AI requires thinking like AI.

This is not a pure analyst role. It is not a pure developer role. It's the bridge between them and the person who builds that bridge.

What You'll Actually Be Doing

Detection Engineering (The Foundation)

  • Author and maintain detection rules across SenseOn's dual-engine architecture:
    • Real-time streaming detections evaluated in milliseconds, written as YAML compiled to binary rulesets
    • Batch behavioral detections backed by parameterised ClickHouse SQL, running on a seconds-to-minutes cadence
  • Write aggregations and materialised views in ClickHouse that power statistical anomaly baselines
  • Build and extend our hunting query library. MITRE-mapped ClickHouse queries that analysts use daily for threat hunting
  • Map every rule precisely to MITRE ATT&CK techniques and tactics, including subtechnique granularity
  • Instrument your own rules: measure false positive rates, define confidence scores, build test datasets, and own the quality of what ships
  • Tune detections against real-world telemetry. Understanding why a rule fires is as important as making it fire

AI-Driven Detection Platform (The Mission)

  • Extend our existing LLM driven rule writing engine to have much wider coverage
  • Design and build pipelines where LLMs can propose detection rules from threat intelligence, CVE disclosures, or analyst hunt findings, with structured output, YAML validation, and human-in-the-loop approval gates
  • Build feedback loops: when a detection fires or produces a false positive, that signal should flow back to improve future AI-generated rules
  • Define the prompt engineering and evaluation harness for detection generation. Pass@k metrics, FP/TP scoring, MITRE alignment validation
  • Work with engineering to make the detection data model AI-legible: schemas, annotations, and context structures that LLMs can reason over reliably
  • Think about our hunting interface: how does an analyst describe a threat in natural language and get a validated ClickHouse query back?

The Technical Stack

You don't need to be expert-level across all of this on day one. But you need to be comfortable working in it and honest about where you'll need to ramp.

Requirements

What We're Looking For

Essential

  • 3+ years writing detection content: SIEM rules, EDR detections, YARA, Sigma, or equivalent; you understand the craft of reducing noise without missing signals
  • Strong working knowledge of MITRE ATT&CK: Not just citing technique IDs but reasoning about adversary tradecraft and tactic chaining
  • SQL proficiency: You write analytical queries comfortably and understand how query performance affects detection latency at scale
  • Hands-on experience with LLMs in a production or engineering context: You've written prompts, evaluated outputs, and built something that used an LLM API (not just chatted with one)
  • Python fluency: Enough to read, write, and debug the kind of Python that runs detection pipelines, builds API endpoints, and processes security telemetry
  • Ability to evaluate AI-generated output critically: You understand where LLMs hallucinate in security contexts and how to build guardrails
  • Clear, precise written communication in English: Detection rules, prompt templates, and eval criteria all live in text

Strong Advantage

  • Experience with ClickHouse or other columnar / OLAP databases
  • Familiarity with Protocol Buffers or binary serialisation formats
  • Background in threat hunting: Building hypotheses, writing queries, and operationalising findings as detections
  • Experience designing or contributing to AI evaluation frameworks (eval harnesses, golden datasets, pass@k scoring)
  • Exposure to network or endpoint telemetry at volume: DNS, NTLM, Kerberos, process execution, network flows
  • Prior work at a security vendor, MDR, or SOC where detection quality had direct customer impact

What We Offer

  • The opportunity to define how AI-native detection engineering actually works in practice: Not as a future roadmap item, but as your primary job
  • A platform with real telemetry, real adversarial signals, and real stakes: Your rules protect organisations
  • Direct collaboration with engineering on the product infrastructure your workflow depends on
  • A team that treats documentation and knowledge capture as engineering hygiene, not overhead
  • SenseOn offers unlimited access to the latest LLM models for experimentation and research. Be at the bleeding edge of AI development as part of your role
  • The creation of new attack vectors is soon to become even more of a machine scale problem thanks to LLM’s, SenseOn will build the machine scale solution to Detection & Response

A Note on What This Role Is Not

This is not a role for someone who wants to write detections by day and leave AI integration to "the ML team." There is no ML team: You are the person who bridges these two capabilities. Equally, it's not a role for a pure AI engineer who has never tuned a real detection against adversarial telemetry. Both halves matter equally.

Benefits

What we’ll offer you:

  • Competitive salary
  • Unlimited holiday allowance
  • Bi-annual career progression review
  • Learning and development investment (certs, conferences, etc)
  • Work MacBook
  • Enhanced pension
  • Private healthcare with vitality offering rewards and discounts from Amazon Prime to Gym Membership

Belong at SenseOn:

At SenseOn, we define Talent as employees who are ❤️ customer obsessed, 🌟 pursuing excellence. They are 🦁 courageous, 🦸‍♀️🦸🏽‍♂️ good people, doing good things, powering our 🚀 rocketship. If this resonates with you, then you will always belong. Nothing else matters. We are an Equal Opportunity Employer and do not discriminate against any qualified employee or applicant. Difference is what makes us stronger.

Prior to the next stage in our recruitment process, please don’t hesitate to confidentially let us know if you require any support to allow you to fully participate in our process

Originally posted on Himalayas