Application form

The application form is the second half of every hire page. You add the questions you actually need answered, and we collect responses, validate them, and route everything to the applicant detail panel in your kanban.

Two fields are always there, whether you add them or not: name and email. They're required for every submission, and they're what we use to identify the applicant across the rest of the product.

Field types

• Short text — one-line text. Good for job title, location, a single link.
• Long text — multi-line text. Good for "tell us about yourself" answers. No hard limit; ~2,000 characters is the practical ceiling for readability.
• Email — a valid email address, validated server-side.
• URL — a valid URL. Auto-prepends https:// if missing. Good for portfolios, LinkedIn, Loom.
• Number — integer or decimal with optional min and max.
• Date — a date, with a native date picker on supporting browsers.
• Choice (single) — pick one from a list of options. Radio-style.
• Checkboxes — pick many from a list of options.
• Dropdown — pick one from a list of options. Use instead of single choice when the list is long (5+ options).
• Rating — 1–5 self-rating. Useful for self-assessed skill level.
• File upload — one file per field. PDF, DOC/DOCX, PNG, JPG, GIF, ZIP, TXT, MD. 10 MB per file.

File upload details

• One file per field. If you want resume + portfolio + cover letter, add three separate file fields.
• Files are stored on Cloudflare R2. You can download originals from the applicant detail panel, and they're included in CSV export as signed URLs.
• We do not parse resumes into structured fields. The file is what the candidate uploaded, nothing more.

Building the form

Open a hire page in the editor and switch to the Form tab. Each field has:

• Label — what the candidate sees (e.g. "Link to your portfolio")
• Help text (optional) — sub-label rendered below the input
• Required toggle — if on, blank submissions fail validation
• Placeholder (text fields only)
• Options (choice / checkbox / dropdown only)

Drag the handle on the left of a field to reorder. Click the trash icon to delete.

Validation, anti-spam, and rate limiting

We validate every submission server-side:

• Email fields require a syntactically valid address
• URL fields require a valid URL (we auto-prepend https:// if the scheme is missing)
• Required fields can't be blank
• File uploads must be one of the accepted MIME types and under 10 MB
• Submissions are rate-limited per IP and protected by a honeypot field invisible to humans

Bots that try to mass-submit a hire page are rejected before they hit your inbox.

What candidates see

A single-column form below the role body. Required fields are marked with an asterisk. If validation fails, errors render inline next to each field — the candidate doesn't have to scroll up to find what went wrong.

On successful submission, the form is replaced by a confirmation screen and (optionally) an automatic email is sent. The candidate doesn't make an account.

Editing the form after publish

• Adding fields is safe. New fields collect answers from new applicants; existing applicants show "—" for those fields.
• Renaming a label is safe. Old answers stay under the new label.
• Deleting a field preserves existing answers on the applicant record but they no longer appear in the kanban or CSV export. Hide rather than delete if you want to keep existing answers visible.

Frequently asked

Can I make a form with no extra fields beyond name + email?

Yes. Some teams do this on purpose — frictionless apply, screen everyone with a short reply.

Can I add conditional logic (show this field if they picked X)?

Not in v2. Every applicant sees every field.

Is there a maximum number of fields?

No hard cap. Forms over ~10 fields hurt conversion in practice.

Can candidates save and resume?

Not in v2. The form is one-shot — if they close the tab, they start over.

Can I export form responses?

Yes, on Starter and above. See CSV export.