How Did You Hear About Us? The Answer That Shows You Actually Belong

Answer “how did you hear about us” with one honest sentence that fits your real source

When a form asks “how did you hear about us,” your goal isn’t creativity—it’s clarity plus credibility. A strong response sounds natural, matches how you actually found the role or company, and supports the impression that you’re a serious applicant.

Most people overthink this question. They either write something too vague (“online”) or too detailed (inventing an exact event they can’t confirm). Instead, use a simple structure: Source + light relevance.

Use the “Source + relevance” formula (and pick the right tone)

The fastest way to write a compelling “how did you hear about us” answer is to follow a formula you can repeat for any application. Source tells them where you came from, while relevance tells them why it mattered.

Here’s the practical template:

1. Source: The specific channel you used (job board, LinkedIn, company site, referral, event).
2. Relevance: One short clause that ties your interest to the role (skill match, mission, team focus, product, or posting details).

Examples you can copy-and-adapt (truthful, not robotic)

• If you found it via a job board: “I found the position through [job board] and it matched my experience in [area].”
• If you came from the company website: “I discovered the role on your careers page and was drawn to the team’s focus on [topic].”
• If it was a LinkedIn post: “I saw the posting on LinkedIn and the responsibilities align with the work I’ve done in [skill].”
• If you heard from a referral: “A colleague referred me after discussing your team’s work on [general area], and I reviewed the role to learn more.”
• If it came from an email/newsletter: “I learned about the opportunity via your email/newsletter and the role stood out for [reason].”
• If you attended an event/webinar: “I heard about the opportunity through your [event/webinar], and I’m excited about applying what I learned to this role.”

What tone works best for “how did you hear about us”

Use professional, calm language. Avoid hype (“I immediately fell in love with your company”) and avoid anything that sounds like a guess. If you want the best chance of passing quick review, aim for one sentence that reads like a real person.

When space is limited, prioritize your source. When space allows, add relevance. Either way, keep it grounded.

Pick answers for common real-life scenarios (with do/don’t rules)

To get top results, match your “how did you hear about us” answer to what actually happened. Don’t force a story—choose the closest truthful option.

If you don’t remember the exact details

Memory gaps are normal. If you can’t recall the exact day or channel, use a broad-but-honest version that still makes sense.

• Good: “I came across the posting through a job search and reviewed the role details.”
• Better: “I found the role through a job board during my search.”
• Avoid: “I saw it on your website last week” (if you’re not sure).

If a friend or colleague referred you

Referrals are a strong signal, but you still want to keep it accurate and respectful. Mention the referral and the reason you followed up.

• Good: “A colleague referred me after I asked about opportunities related to [area], and I applied after reviewing the posting.”
• Good: “I was referred by a teammate who thought the role would fit my background in [area].”
• Avoid: naming someone or claiming an internal conversation you can’t verify.

If you heard about the company through social media

“Social media” is technically true, but it’s often too vague. If you can, narrow it to the real platform or page.

• Good: “I found the posting on LinkedIn.”
• Better: “I saw the role shared on your company LinkedIn page.”
• Avoid: “Online” if you can name the channel.

If you found it through a recruiter message

If someone reached out to you, say so. Then connect it to why you responded.

• Good: “I was contacted by a recruiter about the role and reviewed the posting to confirm fit.”
• Better: “A recruiter reached out about this position, and the responsibilities align with my background in [area].”

Quick do/don’t list you can trust

• Do: Use a specific channel you genuinely used.
• Do: Keep it professional and one-sentence friendly.
• Do: Add relevance only if it’s true (skill match, interest, mission).
• Don’t: Invent names, dates, events, or approvals.
• Don’t: Write filler that doesn’t help them understand your source.

Tip: If you’re unsure between two sources, choose the one you’re more confident you used to find the posting. Confidence reads as professionalism.

How to tailor your answer without sounding like you’re “trying too hard”

The best “this application workflow” answers feel effortless. You can tailor them by making the relevance clause reflect what the role actually emphasizes.

Start with a small checklist based on the job description. Look for one recurring theme, then reflect it briefly. Examples: a technology stack, customer-facing focus, industry mission, or leadership scope.

Match your relevance to one job description signal

• Mission-driven roles: “I was drawn to the mission behind this role after finding the posting through [source].”
• Technical roles: “I found the position through [source], and the responsibilities align with my experience building [skill/system].”
• Customer success / operations: “I discovered the opportunity on [source], and it matches my experience supporting customers and improving processes.”
• Leadership roles: “I heard about the role through [source], and the scope fits how I’ve led teams across [context].”

Keep it short enough for “review speed”

Many applications get skimmed quickly. Your “this application workflow” line should be easy to parse. One sentence is usually enough.

If the field is very limited, prioritize the source and leave the relevance for another part of the application (resume summary, cover letter, or work history bullets).

A note on application workflow (so you don’t lose track of your answers)

If you apply to multiple roles, it’s easy to forget where each one came from. A simple workflow can prevent mistakes: save your “source note” while you apply, and reuse it when you fill out the form.

Even if you’re using tools to speed up repetitive form entries, treat this question like you would a cover letter opening—you want it to be accurate and written by you.

Where JobWizard fits: autofill repetitive fields, then review the one thing you should own

JobWizard is built to help you move faster through job applications by autofilling repetitive form information and prompting you to review before you submit. That matters because “this application workflow” is the kind of field where accuracy and tone come directly from your real story.

In our data, JobWizard has supported 720,000+ applications submitted and 600,000+ autofill sessions run through the product. Across those uses, autofill typically fills about ~18 repetitive fields per application (often 11–23). This is designed for the repetitive parts of applications—not for you giving up control of your key, role-specific responses.

When you’re using autofill, treat the “this application workflow” line as your final checkpoint: verify it matches the channel you actually used and aligns with the job posting you’re applying to.

If you’re ready to apply consistently (without rewriting everything each time), start with JobWizard and use it to speed the repetitive work—then personalize the source and relevance fields so your application still sounds like you.

Choosing the right value to use in “this application workflow”

• If you found the posting yourself: use your channel (company site, LinkedIn, job board).
• If someone told you to apply: name the referral situation (without inventing internal details).
• If you can’t remember precisely: use a broad honest version you’re confident about.

FAQ: “this application workflow” questions you’ll see on applications

Ready to apply faster? Use JobWizard to autofill the repetitive parts of job applications, then review the “this application workflow” field to ensure your source and relevance are accurate—and submit with confidence.