All resources
Form design & UX

Collecting Job Applications on Your Own Site, Without an ATS

Build a careers form that collects what you need, stays clear of questions that create discrimination risk, and handles CVs so they do not sit in an inbox forever. For teams hiring a handful of people, not running a recruiting function.

The ShipMyForm team

· 6 min read

A job application form needs five things: name, email, the role, a CV, and one open question. The form is the easy part, and most teams get it right. What breaks is everything after it — forty applications interleaved with the rest of your email, a spreadsheet on the side to remember who you replied to, and a folder of CVs nobody ever deletes.

Full disclosure: ShipMyForm is our product, and it is one of the options at the end. The first three sections are about the form and the process and apply whatever you use. This is practical guidance from people who build form infrastructure, not legal advice — for an actual position on employment law in your jurisdiction, ask someone qualified.

Ask for five things, make two of them optional

Every required field costs you candidates. That matters more in hiring than anywhere else, because the people you most want are the ones with the least patience for a twenty-field form and the most other options.

The set that works:

  • Full name and email. Required.
  • The role. Required, and pre-filled if you have one form per opening. If you run a single form for everything, a select beats a text field — you want to be able to filter, not read.
  • CV. Required for most roles. One file, PDF or Word.
  • One open question. Required. Not "cover letter" — that word produces three paragraphs of nothing. Ask something answerable: "What have you built that you would want us to look at?" or "Why this role, in a few sentences?"

Optional, and genuinely optional:

  • Portfolio or LinkedIn link. In design and front-end this is often better than the CV. In backend and data it is frequently empty for excellent candidates. Optional either way.
  • Phone. You do not need it until you are arranging a call, and asking for it up front is a small tax on everyone who is merely curious.

That is it. Notice period, salary expectations, current employer and postal address can all wait until there is mutual interest. Asking at the top of the funnel buys you noise from the people who would have answered anyway.

Leave off the questions that create a record you have to defend

This is the part generic form advice skips, and it is the part with actual consequences.

Do not ask, on an application form, for:

  • Date of birth, or dates that imply it (school-leaving year is a proxy for age)
  • A photograph
  • Marital or family status, or caring responsibilities
  • Nationality or country of birth
  • Religion
  • Health or disability information
  • Gender

The problem is not only that these are poor practice. It is that collecting them creates a durable record showing you held that information at the moment you decided to reject someone. If that decision is ever challenged, the conversation is no longer about your reasons — it is about why you asked.

Some of these have a legitimate place later. Right-to-work checks are real, and so are reasonable adjustments for interviews. Both belong after you invite someone in, asked separately, with the reason stated. Diversity monitoring, if you do it, belongs in a separate anonymous form that is not attached to the application and that the hiring manager never sees.

The test:

Before adding a field, ask what you would do differently based on the answer at this stage. If the honest answer is "nothing yet", it belongs later in the process or not at all.

The form works. The pile is what fails.

Here is the shape of the problem for a team hiring one or two people.

Forty applications arrive over a month. Each is an email with an attachment, sitting between invoices and newsletters. Two people are reading them. Somebody starts a spreadsheet: name, role, link to the email, a status column. The spreadsheet immediately drifts from reality, because replying to a candidate happens in the mail client and updating the row happens later, if at all.

Then the predictable things happen. Someone gets two replies. Someone gets none, three weeks after applying. A strong candidate from the first week is forgotten by the third because the thread sank. Nobody can answer "how many are waiting on us?" without reading the whole inbox.

None of this is a discipline failure. It is what happens when the tool is an inbox and the work is a pipeline. An inbox is sorted by arrival time and has exactly two states, read and unread. Hiring has five or six states and the one that matters — waiting on us — is invisible.

CVs are the part nobody plans for

A CV is a dense piece of personal data: employment history, education, sometimes an address and a photograph the candidate added themselves. You have a clear reason to hold it while you are deciding. Once you have said no, that reason is gone.

What actually happens is that it stays. In the inbox, in a Drive folder, in whatever the form backend stored it in, usually forever, because deleting it is a chore nobody is assigned and no system does automatically.

A defensible position is simple:

  1. Pick a period you can justify. A few months after the decision is normal — long enough to explain the decision if asked, and to come back to a near-miss when the next role opens. Six months is a common figure.
  2. Say it in your privacy notice, on the careers page, near the form.
  3. Make something enforce it. This is the one that gets skipped. An unenforced retention policy is worse than a short one, because you have written down a promise your storage is not keeping.

If you want to keep a near-miss on file for longer, ask them. "Can we keep your details for twelve months in case something closer to your experience opens up?" is a reasonable question, and a yes is worth more than a quiet assumption.

What a workable setup looks like

For a small team, the bar is not an ATS. It is three things: applications somewhere that is not your email, a visible stage per candidate, and a rule that deletes what you no longer need.

You can assemble that from parts you already have — a form backend, a shared label, a spreadsheet and a calendar reminder to clear the folder. Plenty of teams do, and it works as long as somebody maintains it.

The ShipMyForm version, since you asked by reading this far: build the form in the job application generator, which gives you the fields above with the CV upload already wired, then set the form's kind to job application. The inbox becomes a board — applied, screening, interview, offer, rejected — the card shows the name, the role and whether a CV came, and the CV itself is a one-click download in the detail rather than row eleven of a field dump. You can reply from the inbox so the thread returns to your own address, and assign a candidate to whoever is interviewing.

And the retention point above is a field on the form's settings: delete rejected applications after N days, counted from the rejection rather than the application, files included. That is the piece that is hard to build yourself and easy to forget.

When you should buy an ATS instead

Be honest about the threshold. Buy one when:

  • You are running several roles at once and need to see them side by side
  • You need structured scorecards so interviewers are comparing the same things
  • You have to demonstrate a consistent, auditable process — regulated industries, or above a headcount where it stops being optional
  • Scheduling is the bottleneck, not deciding

Below that, an ATS is mostly overhead, and the usual outcome is a team that pays for one and still runs the real process in a spreadsheet. The question is not "are we serious about hiring" — it is whether the volume justifies the structure.


If you are putting a careers page up this week, the shortest path is the job application generator for the markup, file uploads for the CV, and a retention period set on day one rather than the day you remember. The rest of the process you can grow into.

Frequently asked questions

What should a job application form actually ask for?
Name, email, the role being applied for, a CV, and one open question. That is enough to decide whether to talk to someone. Everything else — phone number, postal address, notice period, salary expectations — can wait until there is mutual interest, and each extra required field costs you candidates who were on the fence. If you want a portfolio or LinkedIn link, make it optional: strong candidates in some fields have one and strong candidates in others do not.
What should you never ask on a job application form?
Date of birth, photograph, marital or family status, nationality or country of birth, religion, health or disability information, and anything about pregnancy or caring responsibilities. Asking creates a record that you held the information when you made the decision, which is the hard part to defend if a rejected candidate challenges it. Right-to-work and reasonable-adjustment questions have their place, but that place is after an offer or an interview invitation, asked separately and for a stated reason.
How long can you keep job applications and CVs?
There is no fixed number, but the principle is that you keep them only as long as you have a reason to. For unsuccessful applicants that is usually a few months — long enough to defend the decision if it is questioned, and to come back to a near-miss when the next role opens. Six months is a commonly used figure. What matters more than the number is that something actually enforces it: a retention period written in a privacy notice that no system implements is a promise your inbox is quietly breaking.
Do you need an applicant tracking system to hire?
Not for your first handful of hires. An ATS earns its cost when you are running several roles at once, need structured scorecards to compare interviewers fairly, or have to prove a consistent process to an auditor. Below that it is mostly overhead, and teams end up working around it in a spreadsheet anyway. What you do need is somewhere applications are not interleaved with the rest of your email, a way to see who is at which stage, and a rule that deletes the CVs you no longer need.
Where do CV uploads go when you use a form backend?
That depends on the service and it is worth checking before you collect anything. With ShipMyForm, a file is stored in object storage and the submission holds a reference to it rather than the bytes; it is served through an authorised route that checks your session or a signed link, never a public URL. The practical questions to ask any vendor are the same: is the file reachable without authentication, is it deleted when I delete the submission, and can I set a retention period that actually removes it.

Related guides