Who writes WorkHunt's guides

The author

Every article and sample on this site is written and reviewed by Yuvraj Bajwa, Founder, WorkHunt. Each post shows that byline, its publication date, and a link to the policy below.

Why we know the subject

WorkHunt (formerly Resumae) is a job-search workspace built under Coffee Drop Studio. Building it means working every day on what the articles describe:

• Turning one master resume into a version for a specific job.
• Scoring fit, finding gaps, and checking ATS keyword coverage against a posting.
• Writing cover letters tied to the role, not a template.
• Building interview prep from the job posting itself.
• Tracking applications through to an outcome.

Editorial policy

An article has to answer a real job-search question or explain how a WorkHunt workflow works. Topics come from what job seekers actually ask; anything written only to chase search traffic is cut before drafting.

• Claims about hiring, ATS behaviour, or recruiters are attributed to a source, or labelled as product guidance.
• Examples are specific enough to apply to your own resume, letter, or interview.
• AI can help with a draft, but a person checks the structure, facts, and links before anything is published.
• When an article recommends a workflow WorkHunt supports, it says so.

Sources

Where we can, we link to primary sources: official documentation, published research, and employers' own advice. Where none exists, we say what is known, mark the rest as judgement, and leave out statistics we cannot trace.

Updates

We revisit a post when the product changes, a source link breaks, or the advice goes out of date. Small fixes happen quietly; anything that changes the advice shows in the visible text, with an updated date.

What we won't claim

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

Corrections

Spotted a mistake? Email support@workhunt.ai or use the contact page, with the page URL and what is wrong. We acknowledge corrections within two business days and reply again once the page has been reviewed. The same standards apply to the help text inside the app.