Skip to content

About

Who writes WorkHunt's job-search content

Articles on this site are written and reviewed by named people on the WorkHunt team - the same people who build the tailoring, fit analysis, cover letter, interview prep, and application tracking features the articles describe.

By Yuvraj Bajwa, Founder, WorkHunt

A named author, not a content farm

Every article, guide, and sample on this site carries a named byline. The content is currently written and reviewed by Yuvraj Bajwa, Founder, WorkHunt. We do this on purpose: attributing content to a real, accountable person is the honest description of how it is actually made. Each post carries that byline, a publication date, and a link to the standards it was reviewed against.

Where our job-search knowledge comes from

WorkHunt (formerly Resumae) is an AI job-search workspace built under Coffee Drop Studio. Building it means we work daily on the mechanics behind the advice we publish:

  • Turning one master resume into a version tuned to a specific job description.
  • Scoring fit, surfacing gaps, and checking ATS keyword coverage against a posting.
  • Drafting cover letters that stay tied to the role rather than to a template.
  • Generating interview prep from the job posting itself.
  • Tracking applications through to an outcome.

That work is the basis for what we write. Where AI assists a draft, the named author still reviews the structure, accuracy, links, and usefulness before anything publishes. When an article covers something outside the product - how a particular recruiter or applicant tracking system behaves, for example - we attribute the claim to a source or frame it explicitly as product guidance rather than fact.

What we will not claim

No tool can promise interviews, offers, or a guaranteed pass through an ATS, and we do not write as if one can. We avoid invented statistics, and we do not present WorkHunt marketing as independent research.

Editorial policy

Every article must answer a real job-search question or explain a WorkHunt workflow. Topics come from questions job seekers actually ask; pages that exist only to chase search traffic without helping a reader act are cut before drafting.

  • Claims about hiring, ATS behaviour, or recruiter habits are attributed to a source or framed as product guidance.
  • Examples are concrete enough to apply to a resume, cover letter, interview, or application tracker.
  • AI can assist drafting, but a human reviews structure, accuracy, links, and usefulness before publication.
  • If an article recommends a workflow WorkHunt supports, it says so directly.

Sources and evidence

Wherever possible, guidance links to primary sources such as official documentation, published research, or employer-side advice. When no reliable source exists, we say what is known, label the rest as judgement, and avoid statistics we cannot trace.

Review and updates

We review content when product behaviour changes, when source links break, or when job-search guidance becomes outdated. Posts carry publication and update dates, and structured data is generated from the same frontmatter as the visible page. Minor fixes happen quietly; substantive changes show in the visible copy so returning readers always see current guidance.

Corrections and contact

To report a correction, or to reach the team about an article or the product, email [email protected] or use the contact page. Include the page URL and the specific issue. We acknowledge correction requests within two business days and reply again once the page has been reviewed.

This policy applies to the marketing site and the blog. In-product help text follows the same standards and is updated alongside the features it describes.