An Applicant Tracking System (ATS) can parse uploaded documents into information a recruiting team can search and review. The exact workflow differs by product and employer. Treat clean parsing as a practical safeguard, not as proof that a system will automatically reject or accept you.
How ATS parsers actually work
Greenhouse documents resume parsing as extracting information from an uploaded file, and separately documents full text keyword search. That means two useful checks are: can the system read the file, and can a recruiter find the terms they search for?
Extract information from the uploaded document into the recruiting system.
Search resume text for terms such as job titles, skills, locations, and other keywords.
Return matches according to the employer's configured search or review workflow.
Send the file to human review or another stage according to the employer's process, which is not universal across ATS products.
The formatting choices that can disrupt parsing
Do:
Use a simple single column layout for key sections such as experience, education, and skills.
Name your sections exactly: 'Education', 'Skills', 'Projects', 'Work Experience'.
Use a legible font and consistent formatting throughout the document.
Submit a text based .doc, .docx, .pdf, .rtf, or .txt file when the employer allows it.
Keep important information in the main body rather than putting it in headers, footers, or text boxes.
List skills as plain comma separated text in a 'Skills' section.
Don't:
Do not use complex tables for key content. Greenhouse lists tables among formats that can parse unsuccessfully.
Do not put your name or contact information only in a header, footer, or text box.
Do not use a columned layout for the main content when reliable extraction matters.
Do not rely on graphics, photos, or word art to communicate qualifications.
Do not upload a scanned or image only resume when a text document is required.
Do not assume that a visually polished file is parser safe. Test the text layer and follow the employer's upload instructions.
Content choices that help search
Beyond formatting, your content should make the relevant evidence easy to find. Greenhouse documents keyword search across resume text, so use truthful terms that match the role and explain them with evidence.
A skills section that omits the truthful role terms an employer uses, leaving the recruiter to guess what your project involved.
Project descriptions that explain what the project is, not what you did or what impact it had.
Adding metrics you cannot explain. A number is useful only when it is accurate and you can describe how it was measured.
Burying relevant skills where a recruiter may not find them quickly.
Using an abbreviation without also giving the full term when the job description uses a different truthful form.
What human reviewers may look for
When a person reviews your resume, make the evidence easy to scan. There is no reliable universal timer for that review, so prioritise clarity over a claimed second count. A reviewer should be able to find:
Scannability: can they find your education, graduation year, skills, and relevant projects without searching through decoration?
Signal: one line that makes them want to read more, such as an internship at a known company, a high impact project, or a meaningful achievement.
Hygiene: no typos, no broken formatting, no unexplained gaps, and a consistent date format.
Parsing and search are not the same as rejection
An ATS is not one universal reject button. Greenhouse documents both resume parsing and full text keyword search, while employers configure their own review process. Your practical goal is to make the text extract cleanly and describe your experience with truthful terms a recruiter could search for. If a job description says 'backend developer' and your resume uses only 'server side engineering', consider including both terms when both accurately describe your work.
Why parsing fails: what happens to your file inside the system
Greenhouse lists several causes of an unsuccessful parse: graphics, photos, word art, image uploads, complex tables, headers, footers, text boxes, columned layouts, unclear sections, and inconsistent formats. That is why a simple text based document is safer when the employer does not require a designed template.
The India campus resume norm in one paragraph
There is no single India campus resume format that every employer requires. A practical low risk option is a concise, text based document with education, skills, and projects clearly labelled. Describe what you built, the technologies you actually used, and an accurate result or link when you have one. Follow the employer's requested file type and page guidance.
A 20 minute fix plan before your next application
You do not need to rewrite your resume from scratch. Copy the text from your submitted file into a plain text editor and check the reading order. Then move key content out of tables, columns, headers, footers, and text boxes, use clear section labels, and replace vague project bullets with truthful technology and outcome details. Finally, open the saved file and verify that it follows the employer's upload instructions before you submit.
Editorial evidence
Methodology: This guide distinguishes documented parsing behaviour from practical formatting advice. It uses Greenhouse support documentation for parse failures, supported uploads, and keyword search. ATS products and employer workflows differ, so a parsing issue is not presented as a universal automatic rejection rule.