Application form questions that reveal real work

Good application form questions invite a candidate to show how they worked, not just assert that they have a skill. Start with the job and ask for the smallest set of material that would let a reviewer decide whether to continue. For many internships, that means contact details, a résumé or relevant work sample, and two to four contextual questions. More fields can create work without adding evidence.

The form also represents your organization. State who is hiring, what the role involves, whether it is remote or on site, and what the candidate should expect after submission. If the role has a required schedule, location, or eligibility condition, say so plainly. Do not bury it inside a later screening decision.

Build questions from criteria

Take each important screening criterion and ask what a candidate could reasonably provide. A “copywriting” criterion might be supported by a sample plus an explanation of audience and intended action. “Technical fluency” might be supported by a project link and one trade-off the applicant handled. “Ownership” needs a separation between “we did” and “I did.”

The “better” questions still need a short context block. Tell candidates what the organization sells or serves, who the intended customer is, and which assumptions are hypothetical. An applicant should not have to infer your business from an unfamiliar brand name. If the recruiter has not provided enough context, ask for it before publishing. Badal's agent guidance explicitly prompts for role and organization context.

Choose the right material, not every material

A résumé can show education, work history, and a chronology. A portfolio can show outputs. A code repository may show implementation details. A writing sample can demonstrate tone and audience judgment. Ask for the evidence that fits the role, and allow a link when a file is not the best format. Avoid requiring a public portfolio for work that candidates are contractually unable to share. A short description of a private project can still be useful.

If you ask for a file, state accepted types and size before the upload. Badal's current public form accepts PDF or DOCX files up to 5 MB, and recruiters can view submitted files in their authorized workspace. A resume field should be required only when it is genuinely part of your selection method; otherwise give a work-material alternative. Badal's new-role flow starts with a required résumé field, which a recruiter can edit before publishing. Check the actual public form after saving.

Protect candidate privacy. The application needs a link to your privacy notice and should collect only material needed for the hiring decision. Do not ask for national IDs, detailed health information, or unrelated personal data at the first stage. Avoid inviting protected-trait information into open answers. If a candidate volunteers sensitive information, do not turn it into a scoring criterion. Badal publishes a privacy page and terms page; your organization should also review its own obligations.

A practical four-question set

For a content and operations intern at a consumer product company, this set gives useful breadth without a second assignment hidden in the form:

1. Work example: “Share one consumer product, campaign, or operations project you personally worked on. What problem were you trying to solve, what did you own, and what changed?”
2. Copy example: “Link or paste a short piece of copy you wrote. Who was it for, what action did you want, and which choice in the wording matters most?”
3. Experiment judgment: “Imagine our product helps independent restaurants recover missed customer inquiries. With a small test budget, which audience and two messages would you test first? What early result would make you revise the test?”
4. Learning: “Describe a time a plan did not work. Which signal told you, what did you change, and what would you do differently next time?”

The restaurant scenario is explicitly an example. Replace it with the employer's actual audience and product once the recruiter confirms those facts. The form should not pretend a hypothetical brief is company history.

Check for accessibility and completion effort

Write each question in plain language and ask for one thing at a time. Provide an approximate expected length where it helps, for example “three to six sentences.” Make it clear whether a link, file, or text answer is required. Test keyboard navigation and a mobile viewport. A one-question-per-screen format improves focus only if progress and submission states are honest. After submission, send or show a receipt that clearly names the role. If a duplicate application is blocked, explain that no new record was created.

Configure and review in Badal

Create the campaign through Job posts or the API, add organization and recruiter names, and edit the default questions. Open the public /apply/{slug} link yourself before sharing it. Recruiters can inspect the submitted answers and original material in the candidate report. An AI screen may summarize evidence, but the recruiter should review the underlying answer before making a final decision. Badal's campaign setup documentation and application-to-interview guide explain how the form feeds the next stages.

Agent-ready instruction

Ask me one question at a time for role, organization, recruiter name, audience, responsibilities, and screening criteria. Draft a concise public application: contact details, a relevant résumé or work-material request, and two to four questions. Provide candidate-facing context for every scenario. Mark each field required or optional and explain why. Show me the complete form and ask for approval before publishing it.

The test of a good question is simple: can a reviewer point to a specific piece of evidence in the response and relate it to a published criterion? If not, rewrite it.

Frequently asked questions

Should a résumé always be required?

Require it when the role's review process actually uses it. For a portfolio-heavy role, a relevant work sample and short contribution explanation may be stronger evidence. State the requirement before candidates start and offer an appropriate alternative when a file cannot be supplied.

Can I ask a hypothetical scenario in the form?

Yes, if you provide enough background to answer it and label assumptions as hypothetical. Keep it short. A multi-hour scenario belongs in a later, clearly bounded assessment rather than the initial application.