Job search that runs itself.
JobWerks runs a weekly workflow for one candidate: it searches the job boards, filters to the postings that are genuinely relevant, writes a tailored cover letter for each one, builds an ATS-clean resume, audits the candidate's public profiles, and keeps a master spreadsheet and action sheet current. One profile file retargets the whole search.
How JobWerks works
Fill in one profile file: who the candidate is, the target city, the locations, titles, level and rules that qualify or disqualify a posting, the boards to sweep, and which experience to feature per industry. No personal data ever lives in the product itself.
Every week the run sweeps each enabled board for postings from the last few days, opens each shortlisted posting and reads the real requirements, drops the stretches, and skips anything already applied to. Every source reports searched, no results, unreachable or disabled: four different findings, never blurred.
For each qualifying job the run writes a four-paragraph cover letter addressed to that employer, checks the application link is still live, and bundles the letter, the action sheet and the ATS-checked resume into a ready-to-send application pack.
The master spreadsheet grows with every run and the count is reconciled against last week's. The action sheet lists what to apply to, the deadlines inside two weeks, and what was deferred. A run log records when each run started and whether it finished.
Everything a weekly search needs
Location, level, qualifying and disqualifying titles, designation, education, language, employment type, salary floor, posting age and closing date, all read from the profile. Borderline postings are dropped, not flagged: a short list of real matches beats a long one padded with stretches.
Four paragraphs per employer: the exact role and one specific reason for this company, the candidate's education, their current role, and the supporting experience mapped to that employer's industry. Designation milestones keep their real tense.
The resume is built from plain data into a single-column document with no tables, text boxes, images, headers or footers, then audited before it ships. A resume that fails the audit is never bundled into a pack. Any resume can be audited, including one a recruiter sent back.
Shows the candidate what a recruiter sees before the recruiter does: each listed account is opened logged out and scored against a fixed rule catalogue. Consent is required, only listed accounts are touched, and a walled platform is reported as not assessed, never as clear.
One spreadsheet of every job ever found, with the delta reconciled after each run. One action sheet per batch: company, role, salary, deadline, direct link and the special instructions for each application. Dead links are checked and removed before anything is generated.
JobWerks is not tied to one field or one city. Change the profile and the search filters, the sources and the cover-letter tailoring follow: a different city, a different role, a different seniority, or a different candidate entirely.
Product preview
Screens from the JobWerks design brief: the weekly digest, the master list, an application pack, and the targeting editor. The engine runs today; the hosted product surface is the open build, and these show the intended experience.
Plans
no public prices and no self-serve checkout yet- One candidate, one targeted search
- Weekly run across the enabled boards
- Cover letters, action sheet and ATS-clean resume
- Master spreadsheet kept current
- Several candidates, one search each
- Retarget a search from a single profile
- Social profile audit with the candidate's consent
- Run history and source status per search
- Searches for a whole cohort of candidates
- Field-specific boards added per candidate
- Weekly reporting across every search
- Dedicated support
Questions, answered
What is JobWerks?
A weekly job-search workflow for one candidate. It searches the job boards, filters to genuinely relevant postings, writes a tailored cover letter for each one, builds an ATS-clean resume, audits the candidate's public profiles, and keeps a master spreadsheet and action sheet current. Everything is driven by one profile file.
Who is it for?
People running a targeted search, and the career advisors and outplacement firms who run searches on their behalf. An advisor keeps one profile per candidate and gets a ready-to-send application pack for every match.
Which job boards does it search?
The standard sweep covers LinkedIn, Indeed, Glassdoor, the professional body's career centre and government job postings, each with its own on-off toggle. Field-specific boards (industry associations, niche, regional or employer boards) are added per candidate and swept the same way.
How does it decide what is relevant?
Every posting is checked against the profile: acceptable and excluded locations, level, qualifying and disqualifying titles, designation and education rules, language, employment type, salary floor, posting age and closing date. Each shortlisted posting is opened and its requirements read in full; a search-result snippet is never enough. Anything borderline is dropped.
What makes the resume ATS-clean?
Applicant-tracking systems read the raw document, not the page, and routinely drop tables, text boxes, columns, images and anything in a header or footer. JobWerks builds the resume from plain data in a deliberately simple single-column layout, then audits the file for those failure modes before it is bundled into any application pack.
Is the social profile audit safe?
It runs only with the candidate's explicit consent, only on the accounts they list, and only on what is publicly visible when logged out. It never searches the web for the candidate by name. Platforms that wall off logged-out visitors are reported as not assessed, never as clear.
Let the search run while you get ready for the interview.
Book a demo and we will walk through a weekly run: the shortlist, the application packs, the profile audit and the spreadsheet that keeps count.