Skip to content

Developer job application template

Remote-friendly, small teams, real products.

Kind of form
Application
Questions
8
Required
5

Start the 14-day trial, then choose Developer job application under Form templates. Each field, word and colour can be changed.

The Developer job application template rendered as a live form: Join the team.
How this form looks to a customer.

Who uses it

A small agency hiring developers wants to see work, and the form puts that first. “Tell us about something you built” is required, and the code or portfolio link is a required URL field. The description sets the scene, remote-friendly, small teams, real products.

Role is required (Frontend, Backend, Full stack, Mobile, Design), “Years of experience” is a number, and the CV upload is optional, because the link and the build story usually say more. Phone number is optional too, which suits candidates who would prefer email while they are still in another job.

The same form, in 6 layouts

Same questions, same words. Pick the arrangement that suits the page it sits on; the layout can be changed later too.

Field guide

8 questions, each with what the business does with the answer.

Fields in the Developer job application template
QuestionTypeRequired
Full nameHeads the row Applicant intake adds to the hiring sheet for each candidate.Short textYes
EmailGets the instant acknowledgement, which suits candidates still in another job who prefer email.EmailYes
Phone numberOptional, so a candidate can apply without giving a number while still employed elsewhere.PhoneNo
Tell us about something you builtRequired, a build story the hiring lead reads before the code link, often more telling than a CV.Long textYes
RoleFrontend · Backend · Full stack · Mobile · DesignA branch on Design can send those applications to a design reviewer, and the rest to engineering.DropdownYes
Years of experienceA number, so a workflow can compare it with the minimum set as an Applicant intake must-have.NumberNo
GitHub or portfolioRequired link the reviewer opens first, since the code or the portfolio is what gets judged.WebsiteYes
Your CV (optional)An optional file kept with the application in Results, for reviewers who still want one.File uploadNo

What happens after someone sends it

Applicant intake fits, acknowledging each application at once, checking it against the agency’s must-haves, logging it and sending it to whoever hires. A must-have can be a role the team is short of, or a minimum on Years of experience, which a workflow can compare as a number.

Applicants for Design can go to a different reviewer from the engineering roles, and a branch on Role does that without anyone sorting the inbox. Each application also lands as a row in the Google Sheet Applicant intake logs to, so the hiring lead can sort by role and years without opening every response.

Each response adds the person to the client’s CRM, shows in their portal’s Leads and sends you a new-lead alert; if nobody has answered after 15 minutes, you hear again. Any workflow you start from the form runs the moment it arrives.

Library workflows that start from a form like this: Applicant intake.

Its answers can also go straight to another app with a starter: ActiveCampaign, Airtable, Asana, Attio, Brevo, ClickUp, Close and Discord, among others.

Trades that use it

The trade page that lists this form, with the trade’s other forms and workflows.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.