Extract resumes to structured JSON
Resumes contain work history, education, skills, and contact details in thousands of format variations. No two look alike, but your ATS needs consistent data. Sensible turns resumes into structured JSON for candidate screening, matching, and ATS integration.
Why resumes confuse standard extraction tools
Infinite layout variation, creative formatting, and unstructured sections make resumes format-diverse.
Single-column, two-column, sidebar, creative: candidates use every layout imaginable. Section boundaries are identified regardless of visual structure, and contact info, experience, education, and skills all extracted consistently.
'Jan 2020 - Present'. '2018 to 2021'. 'Summer 2019'. Candidates express dates in dozens of formats. Sensible normalizes them all and calculates employment duration, giving your ATS structured tenure data.
Skills appear as bulleted lists, inline mentions within job descriptions, or dedicated sections with varied formatting. LLM parsing identifies skills regardless of where they appear and returns them as a structured array.
Fields we extract
Contact, experience, and education fields ship by default. Customize the schema for your ATS integration.
Full name, email, phone, location, LinkedIn URL, portfolio URL, professional summary/objective
Company name, job title, start date, end date, duration, location, description/responsibilities, achievements
Institution name, degree, field of study, graduation date, GPA, certifications, skills (categorized), languages
Extended curriculum vitae with publications, research, grants, and teaching history.
Skills-based resume format emphasizing capabilities over work history.
Traditional resume format organized by work history in reverse chronological order.
Supported resume formats
Sensible processes resumes in any layout, language, or file format. Hybrid extraction handles the unlimited variation in resume design while outputting a consistent candidate data schema.
Single-column, two-column, creative/infographic, academic CV, federal resume, chronological, functional, combination
PDF, Word (DOCX), scanned/image PDFs, Google Docs exports, plain text



Common Questions
Answers about layout support, date normalization, and skills extraction.
Yes. Sensible processes single-column, multi-column, and creative resume layouts. PDF and image formats are both supported.
Yes. Sensible extracts listed skills as an array, including technical skills, languages, tools, and certifications. Skills mentioned within job descriptions can also be captured.
Sensible captures company name, job title, start and end dates, location, and description for each position. Education entries include institution, degree, field of study, and graduation date.
Sensible identifies standard resume sections including contact information, summary, work experience, education, skills, certifications, and languages regardless of formatting or layout.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
