Job application and hiring forms
Small teams collecting applications from a careers page. Point your form at FormHook — applications land in a dashboard, spam is filtered, and you can export candidates to CSV.
The problem: application forms need to be trustworthy
A job application form collects things you genuinely can't afford to lose: a candidate's name, contact details, links to their work. If an application vanishes, the candidate never knows — and you never get a second chance.
Email-based applications get buried in inboxes and forwarded threads. Spreadsheets get messy and shared wrong. And a full applicant-tracking system is absurd for a small team hiring for one role.
You need a form on your careers page that stores applications somewhere you can read them, filters junk, and shares or exports cleanly when it's time to decide.
How FormHook helps
Point your careers form at a FormHook endpoint (e.g. /api/submit/jobs) and each application is stored with a timestamp, visible in your dashboard, and exportable to CSV whenever you need the details in a spreadsheet.
Spam filtering keeps the noise out: the honeypot catches automated submissions, and heuristic checks flag throwaway email domains and link-stuffed messages — common patterns in fake applications.
Applications stay in one place, in arrival order. Review them from any device, delete irrelevant ones, mark spam, and export the shortlist to CSV to share with a colleague.
Set it up in three steps
Create an endpoint for applications
Pick a key like jobs or applications. If you don't create it first, the first submission creates it automatically.
Build your form
A plain <form> posting to your endpoint with method="post". Text fields like name, email and portfolio URL are stored under exactly those names — keep file uploads out of scope for now.
Review and export
Each application appears in your dashboard as it arrives. Flag spam, delete junk, and export candidates to CSV when you're ready to compare them properly.