"How did you hear about us?" on an application: does it matter?

Short answer: it is recorded, and the person deciding whether to interview you almost certainly will not read it. The question is marketing attribution - which job board gets renewed, which career fair gets cut - and it sits in a different part of your record from the field that actually drives those reports. The one version that changes an outcome is the referral version, because that name is not text at all; it becomes a credit record with someone else's name on it.

That still leaves a reason to answer it deliberately rather than at random. Two of the five variants put another party's name on your application, and one of them is filled in before you type anything.

What the question is actually checking

Forms ask this in five shapes, and the shape tells you which system is behind the box.

Not one of these is a knockout question. There is no answer here that routes an application straight to a rejection queue, and none of the vendor help pages behind this post describes the field as scored - they describe it as attribution, which is a budgeting function, not a hiring one. A Sales Development Representative who writes "Indeed" and one who writes "Indeed - I've followed your Series B closely and admire the team" arrive in exactly the same place, with the second one having spent ninety seconds on a sentence nobody opens.

Who fills in the source, and when

The structured field behind all of this is called the source, and in Greenhouse it is usually set before the candidate touches the form. A job gets a tracking link - the job board URL plus a token that appears in the address bar as gh_src={TOKEN}, described by Greenhouse as "an automatically generated combination of letters and numbers used to identify the unique link". When someone applies through that link, "the source will automatically be added to their profile details."

So the same Data Analyst opening can carry four different links: one on the company careers page, one pushed to a job board, one in a recruiter's outreach email, one in a paid social ad. Same job, same form, four different sources recorded. Greenhouse ships with more than 180 sources configured by default, and those sources roll up into sourcing strategies, which the vendor states "are default hierarchies and cannot be modified" - so the reporting shape is fixed even where the source list is not.

By the time you reach the question, the system usually already knows the answer, and it did not learn it from you.

There is one exception, and it is the reason the question survives at all. The token has to make it through every redirect between the advert and the form, and Greenhouse's own guidance on tracking a candidate's source is largely troubleshooting for when it does not - job board integrations where the source parameter is dropped somewhere in the hop to the application page. When that happens the application lands with no source attached. At that point your typed answer is the only record of where you came from, and a coordinator cleaning up the report will read it and set the source by hand. So the free-text box is not useless; it is a backup that fires occasionally and silently, and you never find out which of your applications was one of them.

The two fields, side by side

The source field and the answer you type are not the same field

Channel attribution lives in a structured source field. Your typed answer lives on the application record beside it.

	Source	The answer you type
How it is set	Automatically, from the tracking link you clicked	By you, on the form
Where it appears	Source & Responsibility panel on the profile	Application section of the profile
Who can change it later	A recruiter, from the profile	Nobody - it is your text
How it is reported	Built-in reports by source and sourcing strategy	One job post at a time, unless linked to a candidate field
Options available	A fixed list the employer configures in advance	Whatever the job post's question offers

The reporting row is the whole reason this question feels pointless: Greenhouse states plainly that "responses to custom application questions can only be reported on one job at a time." An employer who wants to count your answers across every open role has to link the question to a candidate field first, and only five field types can be linked - short textbox, long textbox, yes/no, single-select and multi-select. That is configuration work somebody has to choose to do, on a field that already has a structured twin filling itself in automatically. You cannot tell from the form whether it was done, and the wording of the question will not tell you either.

That makes it the least valuable box on the form, and treating it as a second cover letter is a small self-inflicted wound. Not because enthusiasm is bad, but because the enthusiasm lands in a field designed to be counted, not read, while the fields that are read - the resume, the work history, the screening questions with knockout logic - got less of your attention as a result.

What to write, by situation

Match the channel, keep it to a few words, and stop. Each of these is the whole answer, not the opening of one.

You found the posting on a job board:

LinkedIn

A recruiter messaged you first, and you applied from that message:

Contacted by [recruiter's name] on LinkedIn

You saw it on the company's own careers page:

Company careers page

You came from a university or professional event - name the event, because that is the line item somebody is deciding whether to fund again:

Rutgers Spring Career Fair, March 2026

An agency put you forward, and the form asks which one:

Submitted by [agency name] - recruiter [name]

A former colleague forwarded you the link but does not work there - name the channel, not the colleague:

Forwarded by a contact; applied on the careers page

A Registered Nurse applying through a hospital system's careers site after seeing the role at a nursing conference should write the conference name, not "online". The hospital's talent team is deciding whether to buy a booth next year, and "online" is the answer that gets the booth cancelled. The same logic applies in reverse to a Marketing Coordinator who found a role through a paid ad and writes "Google" out of habit when the ad was on Instagram: the channel that gets credit is the channel that gets renewed, and misfiling it is how good channels quietly lose their budget.

If someone inside the company told you about the job

This is the version worth slowing down for. Naming a current employee does not just fill a box - Greenhouse stores the referrer under a "Who Gets Credit" list on the candidate's Details tab, in the Source & Responsibility panel, and organizations can add custom referrers "to assign credit to a unique referrer other than a user, such as for candidates submitted through a specific campaign."

Two practical consequences. First, what you type stops being text and becomes a structured field, which means it is reportable, filterable and attached to a specific person in the company's own system. Second, that is the same field a referral bonus program is settled from where the employer runs one, so the person you name may be asked to confirm that they know you and that they told you about the job.

So name them exactly: full name as it appears at work, plus their work email if the field allows it. A Software Engineer writing "my friend Dan on the infrastructure team" has created a matching problem for a coordinator; "Dan Whitaker, dan.whitaker@example.com" has created a referral. And if the person merely works there and had nothing to do with you finding the posting, do not use their name. That is a claim someone can check.

If the dropdown has no option that fits

Pick the closest real channel, or "Other" where the form offers it. A blank answer is an answer, and it is the wrong one - on a required field it either blocks your submission or leaves a gap in the only field this question exists to fill.

If you already work at the company

Internal applicants are a category the reporting cares about, because a role filled from inside costs nothing in advertising and the report exists to compare what channels cost. If the dropdown has an internal or employee option, take it. If it does not, say so in plain words and include your team - a source field left to default is what files you as an external applicant, and that is the pile your record then gets handled with:

Internal - current employee, Customer Support team

The manager who posted the job may already know you are applying. The system does not, and the source field is where it finds out.

If you genuinely cannot remember

Very common when you applied to forty roles across three weeks. Look at your browser history for the job's URL, and if the address still carries a gh_src token or a utm_source parameter, the answer is sitting in the link. Otherwise, answer with the channel you use most and move on:

Job board

Does any of this change whether you get an interview?

The volume those source reports are measuring, July 2026

7.3MJob openings, end of July 2026

5.1MHires during July 2026

3.1MQuits during July 2026

Here is the honest position. For everything except the referral variant, no - and the reason to answer it well is not your candidacy but the reporting, which is a real thing that real budgets follow.

The Bureau of Labor Statistics, in the JOLTS release of 1 September 2026, counted 7.3 million job openings at the end of July 2026 and 5.1 million hires during that month, against 3.1 million quits. A talent team filling a fraction of that runs Greenhouse's candidate quality by source report, which scores each source on "the average distance traveled in a job pipeline for all candidates" and plots channels in quadrants so the low-performing ones can be defunded. The new candidates by source report counts applicants per source and sourcing strategy over a date range. Those are the reports your answer feeds, badly, and the source field feeds well.

What none of this tells you is how often a human actually reads the free-text box. The vendor documentation describes where the answer is stored and how it can be reported; it does not say whether any recruiter opens it, and no public source measures that. The 939,700 human resources specialists BLS counted in 2025, at a median wage of $75,940 as of May 2025, are not documented anywhere as reading this field, and I would not build an application strategy on the assumption that yours does.

The one thing to get right

If a person at the company is the reason you know the job exists, name them, spelled correctly, with an email. That single answer is the only version of this question that writes a second person's name into your record - someone the company can go and ask about you, and who, at a company with a referral bonus, has a reason of their own to follow up.

Everything else is a channel label. Two or three words, matched to what actually happened, typed once and never agonised over again - because the minute you spend polishing this box is a minute not spent on the work history above it, which is the part that gets read.

And if you are answering it for the fortieth time this month, that is the part worth automating rather than perfecting - the platform answers the screening questions from your resume so the boxes that do carry weight get the attention this one does not deserve.