splitforms.com
JOB APPLICATION · REACT

Job Application for React

Careers-page form with role, resume URL, and cover letter. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for React
Form.tsxtsx59 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function JobForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New job application');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="role">Position you're applying for *</label>
36 <select id="role" name="role" required>
37 <option value="">Choose…</option>
38 <option>Engineering</option>
39 <option>Design</option>
40 <option>Marketing</option>
41 <option>Sales</option>
42 <option>Operations</option>
43 <option>Other</option>
44 </select>
45 <label htmlFor="linkedin">LinkedIn / portfolio URL</label>
46 <input id="linkedin" type="url" name="linkedin" placeholder="https://linkedin.com/in/janebuilder" />
47 <label htmlFor="resume_url">Resume URL</label>
48 <input id="resume_url" type="url" name="resume_url" placeholder="https://..." />
49 <label htmlFor="cover_letter">Cover letter *</label>
50 <textarea id="cover_letter" name="cover_letter" placeholder="Why this role, why us." required />
51
52 <button type="submit" disabled={status === 'sending'}>
53 {status === 'sending' ? 'Sending…' : 'Send'}
54 </button>
55
56 {status === 'error' && <p>Something went wrong. Try again.</p>}
57 </form>
58 );
59}
500
submissions / mo, free
6
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00React + Job Applicationplatform-specific integration guide

Why React developers choose splitforms for job application

React ships nothing for form delivery — it's a view layer. The historical options are an Express server you stand up just for POST /api/contact, a Vercel serverless function with SMTP wiring, or a third-party library like Formik that still leaves the backend problem unsolved. The job application on this page uses <code>useState</code> for submit state and a plain <code>fetch</code> POST to splitforms — no form library, no context provider, no wrapper component. It works in Create React App, Vite, Remix, and every React bundler because it's just standard <code>FormData</code> and the Fetch API.

§ 00Quick answerReact / Next.js · hr

Yes — this is the shortest safe path for React.

Use the React / Next.js snippet on this page, keep the job application fields visible in your React UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

The posted payload contains full name, email, position you're applying for, linkedin / portfolio url, resume url, cover letter. Required fields are full name, email, position you're applying for and cover letter.

native react reality

React itself ships nothing for form submission — it's a view layer.

use case fit

Most career-page application forms hide behind Greenhouse / Lever, which charge $200+/month per role. For a startup hiring 1-3 roles a year, a self-hosted form with resume upload does the job.

§ 01Job Application × Reactwhy this combination, in 80 words

Built for React developers who hate operating a backend.

Splitforms is the form backend for React sites. One POST endpoint, no SDK, no plugin — drop the job application into a page and ship.

Splitforms is the form backend for React sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan
  • 500 form submissions per month
  • 2 forms on Free; unlimited forms on Pro
  • Spam protection (honeypot + classifier)
  • Webhooks: Slack, Discord, WhatsApp, custom
  • CSV export of all submissions
  • Email notifications (CC and BCC on Pro)
§ 02Copy-paste codeReact / Next.js · 59 lines

Drop into any React project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a React page, and ship. No build-time integration required.

Form.tsxtsx59 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function JobForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New job application');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="role">Position you're applying for *</label>
36 <select id="role" name="role" required>
37 <option value="">Choose…</option>
38 <option>Engineering</option>
39 <option>Design</option>
40 <option>Marketing</option>
41 <option>Sales</option>
42 <option>Operations</option>
43 <option>Other</option>
44 </select>
45 <label htmlFor="linkedin">LinkedIn / portfolio URL</label>
46 <input id="linkedin" type="url" name="linkedin" placeholder="https://linkedin.com/in/janebuilder" />
47 <label htmlFor="resume_url">Resume URL</label>
48 <input id="resume_url" type="url" name="resume_url" placeholder="https://..." />
49 <label htmlFor="cover_letter">Cover letter *</label>
50 <textarea id="cover_letter" name="cover_letter" placeholder="Why this role, why us." required />
51
52 <button type="submit" disabled={status === 'sending'}>
53 {status === 'sending' ? 'Sending…' : 'Send'}
54 </button>
55
56 {status === 'error' && <p>Something went wrong. Try again.</p>}
57 </form>
58 );
59}
ALTPrefer plain HTML? View the universal job application HTML snippet30 lines
form.htmlHTML
<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New job application">

  <label for="name">Full name *</label>
  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
  <label for="email">Email *</label>
  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
  <label for="role">Position you're applying for *</label>
  <select id="role" name="role" required>
    <option value="">Choose…</option>
    <option>Engineering</option>
    <option>Design</option>
    <option>Marketing</option>
    <option>Sales</option>
    <option>Operations</option>
    <option>Other</option>
  </select>
  <label for="linkedin">LinkedIn / portfolio URL</label>
  <input id="linkedin" type="url" name="linkedin" placeholder="https://linkedin.com/in/janebuilder">
  <label for="resume_url">Resume URL</label>
  <input id="resume_url" type="url" name="resume_url" placeholder="https://...">
  <label for="cover_letter">Cover letter *</label>
  <textarea id="cover_letter" name="cover_letter" placeholder="Why this role, why us." required></textarea>

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first job application submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the job application into your React project

Drop the form snippet into a React page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippettsx
'use client';
  …
</form>
STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now
FROM contact@yoursite.com
New job application
Maya Iyer maya@studio71.co
Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?
§ 03bJob Application Form (Careers Page)template-specific playbook

The reason this job application exists.

Resume upload (Pro) · webhooks into Notion / Airtable / Greenhouse.

why it matters

ATS subscriptions (Greenhouse, Lever, Workable) start at $6-15k/year for a small team — a lot of money for a startup that hires 2 engineers a year. A self-hosted application form on the careers page handles the inbound flow. The form captures name, email, role applying for, resume (PDF upload, often required), LinkedIn / portfolio URL, and a brief 'why us' textarea. The submission lands in the hiring manager's inbox or webhooks into Notion / Airtable / a Slack channel for triage. As soon as you're past 5 simultaneous open roles, an ATS pays off — until then, this works.

route the submission
01

Capture role and basics

Required: name, email, role (dropdown of open positions), resume upload (PDF/DOCX). Optional: LinkedIn URL, portfolio URL, cover-letter textarea, location / timezone.

02

Receive resume upload

Storage-backed file upload keeps the resume connected to the submission. Attachments cap at 10 MB per file; resume PDFs are usually 100-500 KB, so headroom is generous.

03

Webhook to Notion / Airtable

Push the application as a row in a Notion / Airtable database (one per role). Hiring team triages from there — moves to interview stage, archives obvious passes, comments inline. Cheaper than Greenhouse for low-volume hiring.

§ 03cReact production notesnative path · deploy · gotchas

What changes when this job application lives in React.

These notes come from the React platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

React itself ships nothing for form submission — it's a view layer. The historical baseline is one of: an Express/Hono/Fastify server you stand up just for POST /api/contact, a Function-as-a-Service (Vercel/Netlify/Cloudflare) that ends up needing the same SMTP wiring, or a third-party form library (React Hook Form, Formik) that handles validation but still leaves you to operate the backend. Vite, CRA, and Remix all default to assuming you have somewhere to POST — they just don't tell you where. Splitforms is the where: a single fetch call, no library install, no useEffect gymnastics, no Express boilerplate.

deploy notes

Vite-built React apps are static — they deploy to any static host (Vercel, Netlify, Cloudflare Pages, S3, GitHub Pages). The splitforms fetch is cross-origin, so configure your CSP to allow connect-src 'self' https://splitforms.com if you have one. Vite reads env vars from .env at build time and only exposes those prefixed VITE_ to the browser bundle. CRA uses REACT_APP_ instead. On Cloudflare Pages, the build output is served from the edge with sub-50ms cold starts; splitforms adds another ~30ms RTT — not noticeable in practice. Lock the access key to your live origin in the splitforms dashboard.

React gotcha

useState + setStatus inside async causes race conditions

If a user double-clicks submit before the first request settles, you'll fire two POSTs. Always disable the button while status === 'loading'. Better still, also use an AbortController to cancel the in-flight request if a re-submit happens.

React gotcha

FormData and controlled inputs can desync

If you control inputs via useState (value={name} onChange={...}), the FormData object you build with new FormData(e.target) won't see your state — it reads the actual DOM. Either use uncontrolled inputs (no value prop) or build the body manually from state.

React gotcha

CSP errors when posting to a third-party endpoint

If your site has a strict Content Security Policy with connect-src 'self', fetch to splitforms.com will be blocked. Add splitforms.com to your connect-src directive: connect-src 'self' https://splitforms.com.

React gotcha

Strict mode + double-mount triggers two submissions in dev

React 18+ strict mode mounts components twice in development to surface side effects. If you put your fetch call in useEffect (don't), you'll see double-submits. Always trigger network calls in event handlers, not effects.

PATTERN A

Pattern A — uncontrolled inputs + native FormData

Skip useState per field. Inputs stay uncontrolled, new FormData(e.currentTarget) reads them at submit time, status state covers idle/loading/ok/err. ~25 lines, no form library. Use the same wiring for the job application fields on this page.

pattern-a.jsxjsx17 lines
01import { useState } from "react";
02export default function ContactForm() {
03 const [status, setStatus] = useState("idle");
04 return (
05 <form onSubmit={async (e) => {
06 e.preventDefault(); setStatus("loading");
07 const fd = new FormData(e.currentTarget);
08 fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
09 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10 setStatus((await r.json()).success ? "ok" : "err");
11 }}>
12 <input name="email" type="email" required />
13 <textarea name="message" required />
14 <button disabled={status === "loading"}>Send</button>
15 </form>
16 );
17}
PATTERN B

Pattern B — React Hook Form for validation, splitforms for delivery

RHF handles client-side validation (zod schema, error messages); on valid submit, hand off to splitforms. RHF's handleSubmit callback receives parsed values — repackage as FormData and POST. Use the same wiring for the job application fields on this page.

pattern-b.jsxjsx8 lines
01import { useForm } from "react-hook-form";
02const { register, handleSubmit, formState } = useForm();
03const onSubmit = async (data) => {
04 const fd = new FormData();
05 Object.entries(data).forEach(([k, v]) => fd.append(k, v));
06 fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
07 await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
08};
§ 04Field-by-field rundown6 fields · names you POST

What every field actually does.

Each field below ships in the job application template — rename, remove, or add your own. Splitforms accepts any name you POST.

nameREQUIRED
TEXT

Full name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Jane Builder
emailREQUIRED
EMAIL

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · jane@example.com
roleREQUIRED
SELECT

Position you're applying for

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

EngineeringDesignMarketingSalesOperationsOther
linkedin
URL

LinkedIn / portfolio URL

Out-of-band material reviewers can open in one click.

placeholder · https://linkedin.com/in/janebuilder
resume_url
URL

Resume URL

Out-of-band material reviewers can open in one click.

placeholder · https://...
cover_letterREQUIRED
TEXTAREA

Cover letter

Free-text input — no character limit, expands as the visitor types.

placeholder · Why this role, why us.
§ 06Questions9 answered

Job Application on ReactFAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this job application work on React?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any React site without server-side code, plugins, or SDKs. Drop the snippet into a React page or component and submissions land in your splitforms dashboard.
02How much does the job application cost on React?
Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.
03Can I customize the fields?
Yes. The template ships with sensible defaults (full name, email, position you're applying for, linkedin / portfolio url…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the job application?
A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on React as on any other framework.
05Can I send the job application submissions to Slack or Discord?
Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.
06Will it work on a static React site?
Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.
07Is this EEOC / OFCCP compliant?
If you're under the regulated thresholds (15 employees for most EEOC requirements; federal contractor for OFCCP), basic forms are fine. If you're regulated, you need to collect voluntary self-ID demographics on a separate page (race, gender, veteran, disability) with explicit non-discrimination language. Your employment lawyer should review the final flow.
08How do I avoid resume-spam from staffing agencies?
Hidden honeypot field plus splitforms' spam classifier catches most. For persistent agency spam, add a 'are you applying directly or through an agency?' radio — direct applications get the role-specific reply; agency applications get a 'we don't accept third-party submissions' auto-response.
09Should I require a cover letter?
For senior or specialised roles, yes — quality goes up with the friction. For volume hiring (support, ops, junior eng), no — required cover letters drop application count 60-80% and the cover-letter quality is mostly noise anyway. Tune by role.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a job application on React in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your React project.

Get free access key →Read the docs
founders pricing locked in · early access open