Your device, any OS
The worker runs on a machine you control and drives a visible browser. You can watch it work, and close it whenever you like.
How it works
Five steps, then it runs
It runs on your machine, in a browser you are signed in to, inside limits you set. Nothing goes out before you have approved what may be said in your name.
Full namefrom your profileauto
Work historytailored to this roleauto
Why this role?answered in your words…
Right to workyou answer thisyou
Identity documentnever uploaded for youyou
Submitcounted only when the site confirms it
The sequence
Set up once, in an evening
Four of these five steps happen once. The fourth is the one that repeats, and it is the one you stop spending your own evenings on.
Build your profile once
Your experience, skills and preferences — the facts everything else is generated from. Nothing gets submitted that is not grounded in what you saved here.
Sign in to the job board yourself
You log in to SEEK in your own browser, on your own device. Jobsizy never asks for or stores that password. Your account stays yours.
Choose how applications are sent
Each prepared application waits for you to check and submit it, unless you choose automatic submission for a profile. You decide, in one place.
Applications go out, with receipts
Each application is matched, tailored, answered and submitted — and a receipt is captured. Anything uncertain is flagged for you rather than retried.
Prepare for what comes back
Interviews get preparation built from the actual role, consistent with the application already submitted in your name.
Where it runs
On your machine, in your own session
This is the decision everything else follows from. A tool that held your job-board password could be breached, could be locked out, and would be applying as something other than you.
Your login, never ours
You sign in to SEEK yourself. When the session expires, the window opens for you to sign in again — by design, not as a gap.
The decisions are ours, the actions are yours
The backend decides what should happen next and keeps the record; the worker only carries it out in the browser. Neither half can act alone.
One application, end to end
What actually happens between a vacancy and a receipt
Five stages. The last two are gated — one on you, one on the employer's own confirmation.
A single application
- Vacancy matched to your role profile
- Documents tailored to this vacancy
- Employer questions answered
- Consequential declarations left blank
- Submitted — confirmation captured
Why the last stage is drawn as a stop
A button that vanished, a page that merely loaded, a spinner that never resolved — none of those are proof that an employer received anything. An application counts as submitted only when the site itself confirms it, and anything short of that is recorded as uncertainand shown to you.
Uncertain applications are never retried on their own. A silent retry against a real employer risks a duplicate application under your name, which is worse than an honest “we cannot be sure”.
And why matching happens once
The same vacancy appears on several boards under different identifiers. Canonical identity resolution is what stops you applying twice to one job — which an employer notices, and which is the most expensive mistake a tool like this can make.
The volume problem
Matching first, so effort goes where it is worth spending
What it will never do on its own
Refusals written into the code. They are not a roadmap item, and there is no setting that turns them off.
- Enter payment detailsStops and asks you. Nothing legitimate asks a candidate to pay to apply.
- Upload or complete identity documentsStops and asks you.
- Sit an assessment or a timed testHands the session back to you, with the page already open.
- Make a consequential declarationRight to work, criminal history, licences, sponsorship — yours to answer.
Controls that behave the way the words suggest
Pause stops new work starting and lets anything mid-submission finish. Abandoning a half-sent application is exactly what creates an uncertain outcome, so pause drains rather than drops.
Stop does the same and then holds. Submissions off is the default state of the whole system and stays that way until you turn it on.
Live submissions are currently disabled platform-wide while the candidate policy gate is completed.
Questions
The things people ask about the mechanism
Do you need my SEEK password?
No, and the system is built so it cannot use one. You sign in yourself, in a visible browser window on your own device, and Jobsizy works within that session. When the session expires, the window opens again for you to sign in — that is the design, not a limitation.
Will applications be sent without me seeing them?
Not unless you choose that. By default each application waits for you to check its résumé, cover letter and answers and submit it; automatic submission is a setting you turn on for all profiles or one at a time. You can pause or stop at any time.
What happens if an application is interrupted halfway?
It is recorded as uncertain, never retried automatically, and shown to you to reconcile. Silently trying again risks a duplicate application to a real employer, which is worse than telling you plainly that we cannot be sure.
Can it invent experience I do not have?
No. Answers come only from facts you approved. Tailoring may re-emphasise something already true in your profile; it may not add a claim. Anything without an approved basis is queued for you to decide.
What about assessments, identity documents or payment requests?
Those are hard boundaries. Assessments, identity documents, payment fields and consequential declarations are never filled automatically — they are left for you, always.
Where does it run?
On your own device — laptop, desktop or a machine you control, on any operating system. That is deliberate: it drives a browser holding your own session.
What do I actually pay for?
Outcomes. An application that was submitted and receipted, a preparation session, a problem solved. Not a monthly seat that charges whether or not anything happened.
Can I stop mid-way?
Yes. Pause or stop at any time. If an application is already mid-submission it is allowed to finish rather than being abandoned halfway — abandoning it is what creates an uncertain outcome — and nothing new starts after that.
See it run on your own applications
Set up the profile once. You decide what may be sent before anything is.