Greenhouse resume: write for the preview and for search

Sam Okonkwo is a backend engineer applying to “Senior Backend Engineer – Payments” on Harbor Ledger’s Greenhouse board. The requisition sits behind Apply and a resume upload. After submit, two objects exist. The hiring manager — usually an eng manager between standups — opens the PDF on the candidate scorecard. A recruiter or sourcer types “Kafka” and “PCI” into Greenhouse search. If the extract is empty, Sam never appears in that list. The PDF can still sit on the profile. Search will not find it.

This is the split people miss. They design for the manager and hide the email in a sidebar. The manager can still squint at a designed page. The sourcer cannot find the profile. Or they dump every noun from the posting into a footer for the parser, and the manager closes a wall of tools. You write one file that is human in the PDF and tokenizable in the parse. Greenhouse is not choosing one view for you. It keeps both.

Greenhouse is a recruiting ATS. It is not an HRIS form first. That is why it feels kinder than Workday: fewer named widgets after upload, more “attach a file and answer a few questions.” Kindness is not safety. Headers, footers, text boxes, and icon rails still drop email and phone from the extract. The profile then has a handsome attachment and a blank Email field. Outreach bounces. The next req in the same org “uses last resume” and repeats the blank. Fix the source file. Do not only type the address into a box and leave the PDF broken.

Workday, for contrast, tries to hang tokens on First Name, Employer, Job Title, and dates, then makes you confirm every row. Greenhouse stores the file and indexes text. Same single-column layout serves both. For the field map and date widgets, keep Workday resume format next to this page. For the click path on a tenant that still makes you walk Experience rows, how to upload a resume to Workday. General parse hygiene lives in ATS resume. What a human actually sees after any parse: recruiter preview.

What “stored” means on the candidate

• The original PDF or .docx on the profile and scorecard — this is what most hiring managers open.
• Parsed contact: name, email, phone, sometimes LinkedIn if the URL was real text.
• Searchable employer, title, and date tokens the sourcer can filter.
• A free-text index of bullets. “Kafka” in a skill bar image is not in that index.
• Custom answers (years of payments, on-call, visa) sit beside the resume. They are not extracted from it.

Sam’s Canva export can look sharp in Preview on a laptop and still fail both stores. The viewer on the scorecard may flatten columns so “Harbor Ledger” sits under the wrong year. The parse may read the right rail first and store a graduation year as an employer. Select-all on your export is the five-second test: if you cannot highlight the Gmail and “Mar 2021,” Greenhouse cannot index them. Then run the ATS checker so you are not guessing which heading failed. An ATS resume is not a keyword dump. It is a document that still contains contact data after the parse and still reads like a person when a manager opens the PDF.

Here is the field list we watch in edits, because these are the tokens Greenhouse search and the candidate profile actually use. First Name and Last Name usually split on the first space — “Mary Ann Okonkwo” can become First Name “Mary” and Last Name “Ann Okonkwo,” which then fails background-check matching later. Email must be a real address in the text layer, not an envelope icon. Phone should include area code; international applicants should include the country code in the body so the Phone field does not store a truncated local number. LinkedIn belongs as a full URL under the name. A header icon that “looks like LinkedIn” is a picture.

Experience is not a repeating Workday widget you confirm line by line. It is still a set of tokens: company, title, location, start, end. Greenhouse needs “Stripe,” “Backend Engineer,” “Austin, TX,” “Mar 2021,” and “Present” in an order a parser can tokenize. Education is school, degree, field, dates. Skills become searchable words, not tags you drag in a UI. Certifications (AWS, PCI SAQ language you can defend) should appear as text under Skills or a Licenses line. A logo row of vendor badges is decoration. The sourcer searching “Postgres” will not find a elephant icon.

Dates belong beside the role, month and year: “Mar 2021 – Present” or “03/2021 – Present.” Do not hide them in a thin sidebar. Do not write “’21–now” in a script font. If Sam contracted through an agency at a payments client, put the client and the agency in the same block so the employment graph does not look like a gap and so search can hit both names. “Present” in the file should match the fact that you still work there. Mismatches confuse humans on the scorecard more than they confuse Greenhouse, but they still split jobs when the parser cuts “Harbor Ledger” and “Payments platform” into two employers.

What the parser does not take from the file

• How did you hear about this job, employee referral name, and source codes — you type these.
• Work authorization, visa, and relocation willingness — application questions.
• EEO, veteran, and disability self-ID — legally separate from the resume parse.
• Job-specific screens: years of payments, on-call rotation, “have you built an idempotent ledger.”

Those answers must agree with the PDF. If Sam’s resume says “four years payments” and the dropdown is “1–2,” a coordinator will trust neither. Cover letters are a separate slot on many Greenhouse boards. Put the parse-safe resume in the Resume field. Do not upload a designed portfolio PDF there. If you include a letter, tie it to this payments req — Kafka, PCI scope, on-call — not a generic “I am excited about your mission.” For noun placement without lying, the same rules as any ATS resume apply. If you prefer to type inside a known-good layout first, start in the Enhance CV builder.

File type: .docx or a tagged, selectable-text PDF. A scanned image of a diploma as page one is a brick. Calibri, Arial, Georgia, or the system font in Enhance CV. Body 10.5–12 pt. No photo in a US Greenhouse pipeline unless the company explicitly asks — and even then, not as a header image that kills text extract. File name: Okonkwo_Backend_Payments.pdf, not ResumeFinal3.pdf. Two-column tables that put tools on the left and dates on the right are how PDFs shuffle order. Greenhouse may read the right column first. Use one column, left-aligned, standard headings in the language of the country you are applying in: Work Experience or Professional Experience, Education, Skills.

After you attach the file, Greenhouse shows a preview. Open it. This is closer to what the hiring team will see than your Canva tab. Two checks matter. First: the parsed contact. If Email is empty, the address lived in a header, footer, text box, or sidebar. Cancel. Move name, city, phone, email, and LinkedIn into the first lines of the body as real text. Re-export. Re-upload. Typing the Gmail only into the form leaves the next “use last resume” broken and leaves sourcers with a profile they cannot email from search.

Second: the document viewer. Select text. If you cannot highlight “Kafka,” “Mar 2021,” and the Gmail, the scorecard may show a flattened picture. Some managers still open the attachment in a laptop PDF app and see your design. Many open it on a phone inside Greenhouse. Columns collapse. Sidebars jump. A two-column “visual system” becomes a jumble. The preview is the cheap place to learn that. Waiting for a silent week after Submit is the expensive place.

“Update resume” is a trap. If Sam already exists in this org from a 2024 application, attaching a new file does not always replace the old one. The scorecard can still show last year’s title. Open the candidate view after submit — or the confirmation screen if the board shows the file name — and confirm Okonkwo_Backend_Payments.pdf is the object that landed. Internal referrals have the same problem: a teammate dropped an old PDF into a prospect profile. You still replace it and check the preview. For the human side of extracts across ATS brands, what recruiters see after the parse is the companion page.

A five-second preview audit

• Email and phone visible as text in the viewer, not only as icons.
• Latest job shows month and year next to employer and title.
• File name matches this requisition, not an old download.
• Select-all works. If it does not, you uploaded an image.

Decline “Apply with LinkedIn” if that import has ever emptied dates. LinkedIn is a different parser and a different document. One parse-safe file, tailored nouns for this req, then the Greenhouse questions. After the preview looks honest, still run the ATS checker on the same export so the next board is faster. A green checker does not replace opening the Greenhouse viewer. It tells you the text layer exists before you burn an apply.

Hiring managers do not score the parse. They score the PDF and the answers on the scorecard. Recruiters live in search. You need the email in the extract so outreach works, and you need bullets a tired manager can finish on a phone. That is why “pretty for Greenhouse, plain for Workday” is a bad split. The pretty file is the one the Greenhouse manager opens. If it is a two-column image, you failed the scorecard. If the plain file hid contact in a header, you failed search. One column, contact in the body, human bullets. Preview confirms both.

These three edits come from Sam’s drafts and from files like them. Steal the structure. Do not invent a payments platform you did not ship.

Line-level proof still matters after the parse works. “Responsible for payments” does not help a Senior Backend Payments req. “Wrote idempotent ledger posts for Stripe webhooks; p95 under 200ms on the Kafka consumer; on-call for PCI-scoped services” does. Keep the parse-friendly layout, then write like an engineer who was in the room. If you want a layout that already keeps contact in the body, build it in Enhance CV and export selectable text. Then score the same file in the checker before you touch Harbor Ledger’s Apply button.

A fourth failure we see, even when the three transforms above are done: a keyword footer that repeats the whole qualifications block. Greenhouse can index it. The manager reads it as noise and stops at the summary. Put Kafka and PCI in the payments bullets you can defend. Leave the footer for a URL or nothing. Search will still hit the nouns. The scorecard will still look like a person wrote it.

This is the path Sam follows on Harbor Ledger’s board. Companies change labels, not the idea: attach a file, read the preview, answer questions the PDF never contained, submit. If you prefer to type inside a known-good layout first, start in the Enhance CV builder.

1. Open the requisition from the company career page or the Greenhouse board, not a random Indeed scrape that may point at a stale req ID.
2. Create the account with the same email you put on the resume. A second Gmail is how you lose status mail and split into two candidates.
3. If you already exist in this org, open the old profile mentally: you will replace the resume. Do not assume last year’s PDF updated.
4. Upload .docx or selectable PDF. Decline “Apply with LinkedIn” if that import has ever emptied your dates; the LinkedIn extract is a different parser.
5. Wait for the preview. Do not click Submit until you have opened the viewer and glanced at parsed contact.
6. Read the name split. Fix “Mary Ann” in the form if the board shows separate first and last fields. Hyphenated last names belong entirely in Last Name.
7. Read Email and Phone. If either is blank, the contact was in a header. Cancel, fix the file, re-upload. Do not only type the email into a box and leave the PDF broken for the next rec.
8. Select-all in the resume viewer. If you cannot highlight Kafka and March 2021, you uploaded an image or a flattened export.
9. Confirm the file name on screen is this req’s file, not ResumeFinal3.pdf from a 2024 prospect attach.
10. Answer custom questions: years of payments, on-call, work authorization. The numbers must match a sentence on the resume.
11. EEO and self-ID screens are optional in many US boards; they are not scored from your PDF. Complete per your comfort and the instructions.
12. Cover letter only in the Cover Letter slot, and only if you have something specific to this payments team. The resume slot stays the parse-safe file.
13. Submit. Open the confirmation. If the org lets you view the application, open the resume again. “Update resume” later still needs this same preview check.
14. Run a parse check on the same file you uploaded so the next Greenhouse board is faster — and so a Workday req the same week does not surprise you.

Step 7 is the one people skip. They type the missing email into the form and never fix the PDF. The next requisition in the same Greenhouse org may attach the old extract and the old file. Fix the source. Workday shops that force a full widget walk still store an attachment; a recruiter can open a broken PDF there too. The difference is the confirm step: Workday makes you stare at Experience rows. Greenhouse makes you stare at a preview. Both are easy to click through. For Workday’s row-by-row path, use how to upload a resume to Workday. For the broader screen beyond one vendor, how to pass an ATS.

Sam will also apply to a hospital vendor that runs Workday and a contract shop that still uses Taleo. The same single-column backend file should travel. What changes is how much you trust autofill, and where the hiring manager actually reads. Greenhouse leans on the PDF plus search. Workday leans on named widgets you must audit. Taleo often makes you retype history and still stores the attachment. iCIMS mixes a parse with long numeric questions. One layout. Four confirm habits.

Do not keep three visual identities. Keep one parse-safe file and change the nouns per req (payments vs. ads vs. infra). Decorative PDFs “for the Greenhouse hiring manager” fail when that manager is reading inside the Greenhouse viewer, which is not Canva. Workday’s preview is not Canva either. Field-level Workday rules: Workday resume format. Click path: upload a resume to Workday. If you want the extract-vs-human view in one place, recruiter preview.

Lever sits closer to Greenhouse than to Workday: file plus search, fewer autofill widgets. The header-email failure is the same family. If Sam’s week includes Lever, Greenhouse, and Workday, the file does not change. The minutes you spend after upload do: preview in Greenhouse and Lever, Experience rows in Workday. That is the whole contrast. People who maintain a “designed Greenhouse version” are the people whose Workday Email widget is empty the same afternoon.

Two-word first names and hyphenated surnames: put a resume name that matches legal documents as closely as you can, then fix the form if Greenhouse shows a split. Background checks match Last Name. Do not put credentials in the Last Name field (“Okonkwo, SWE”). The title belongs after the name on the PDF as “Sam Okonkwo” or in the latest job line. A comma after the name is how some extracts split. Check the preview.

Country and phone: a US board that asks for State still wants State in the form even if you live elsewhere. Use the address questions, not a clever resume line. Phone with + and country code in the body reduces truncated Phone fields. Postal codes with spaces (UK, Canada) sometimes split in parsers; type them in the form exactly as the example. German or French boards may want the resume in that language; the layout rules do not change. Contact still belongs in the body.

Two attachments: many Greenhouse posts allow a cover letter and a resume. The parse-safe resume goes in Resume. A designed portfolio PDF does not. Cover letters are optional on a lot of boards; the resume still has to carry Kafka and PCI. If you include a letter, name the team and the req. Agency submissions: confirm which file the agency attached. Agencies love designed PDFs. You still own the preview if the company sends you a self-apply link later.

Intern and student titles: Greenhouse will store “Software Engineering Intern” as a title. That is fine. Do not relabel it “Senior Backend Engineer.” Dates still need month and year. A 12-week intern block should not look like a two-year staff job because you omitted months. Contract plus client: write both names in one block so search can hit the client the req named. Gaps still look like gaps to humans on the scorecard. One line in the summary is enough; do not invent a company to fill 2020.

Prospect vs candidate: a sourcer may have added Sam last year with an old PDF. When you apply, you become a candidate on this req. The old file can still be the first thing a manager opens. Replace it. Open the preview. Internal employees using Greenhouse for a new team have the same job: the worker chat in Slack is not the candidate profile. After submit, if the board offers “My applications” or a confirmation with a file name, read it. “Resume uploaded with warnings” is usually missing dates or an unreadable file, not a moral judgment.

What to do today: export a single-column file, select-all, run the checker, then walk Sam’s steps on one real Greenhouse req. If the preview email is empty, fix the PDF before you rewrite another adjective. Build the layout if you are still fighting Canva text boxes. For the screen beyond Greenhouse, how to pass an ATS. For the week you also hit a hospital Workday, keep Workday format and upload Workday open. The file is the same. The confirm step is not.

Last check templates skip: if Kafka lives only in a logo, Greenhouse search will not see it. Write the word. If the PCI scope lives only in a confidential appendix you did not attach, the manager will not see it. Write one honest sentence. If the email lives only in your email client signature, the profile will not have it. Write it under the name. Preview. Then submit. Silence after Apply is usually a blank extract or a stale PDF, not a secret ranking.