Add fields beyond Kula's built-in Personal Info and Profile sections to collect role-specific information — a knockout question, a portfolio link, expected compensation — directly on the application.

Template vs. job level: where to add a question

Custom questions can live in two places, and it changes their reach:

• Application form templates — add the question via Settings → Jobs & Applications → Application Forms.

  It becomes available to every job that uses that template, so use this for questions common across many roles.

• Within a specific job — open the job → Job Post Settings → Application Form, and edit the assigned form directly. Changes made here apply only to that job and don't touch the template or any other job using it. Use this for role-specific questions (a knockout question for one opening, a portfolio link for a design role).

Adding a question

• Open the form (template or job-level) and go to the section you want to add the field to, or create a new section first.

• Click Add Field (or Add field).

• Enter a field name — this is what candidates see as the question label.

• Choose a field type. Confirmed real types include Short Text, Long Text, Yes/No, Single Select, Multi Select, Number, Date, URL, and File; Rich Text also appears as an option. You can't change a field's type after creating it, so confirm before saving.

• Add a description or placeholder text if it helps candidates understand what's being asked.

• Toggle Required if candidates must answer before submitting.

• Set visibility for your hiring team — Recruiters always see the field; Hiring Managers, Coordinators, and External Recruiters can be toggled Visible or Hidden per field.

• Save the field, then save/update the form.

Organizing with sections

Group related questions into sections for a cleaner candidate experience — click Add Section, name it (e.g., "Role-Specific Questions," "Compensation & Availability"), and add fields underneath. You can drag and drop fields to reorder them within a section, but fields can't be moved between sections once placed — if a field belongs in a different section, you'll need to recreate it there.

Good to know

• A field's type can't be changed after it's created. If you need a different type, you'll have to delete the field and add a new one — any answers already collected under the old field are not migrated to the new one.

• Existing applicants don't retroactively see new or changed questions. A question you add (or a form you update) only applies to candidates who apply after the change — candidates who already applied keep their original submitted answers.

• Rich Text currently shows up as an option for knockout rules, which it shouldn't. Knockout rules are meant to work off matchable values (like Yes/No or Single/Multi Select answers) — a Rich Text field doesn't have a fixed set of possible answers to match against, so this is a known display bug rather than a usable configuration.

• Cloning an application form template can drop or scramble its knockout rules, particularly the selected options tied to Single Select and Multi Select fields. If you clone a form that has knockout rules configured, double-check those rules landed correctly on the clone before relying on it.

• File-type custom field values can render as "[object Object]" when they surface elsewhere, such as in offer fields — a known display bug outside the application form itself. If a file-type answer looks broken somewhere downstream, this is a likely cause rather than a data-loss issue.

• Separate Internal vs. External application forms exist but aren't generally available yet — as of mid-2026 this was enabled only for specific accounts behind a feature flag. Most accounts use the same application form for both internal and external applicants.

• Custom questions you add in Kula don't extend to LinkedIn Easy Apply or similar job-board-native quick-apply flows. Whether an Easy Apply questionnaire's questions are required or optional is controlled by the job board contract (e.g., set up in VONQ/LinkedIn), not by Kula's application form builder.

FAQ

• Can I add a question to just one job without changing the template everyone else uses? Yes — edit the application form from within that job's Job Post Settings → Application Form. Changes made there apply only to that job.

• Can I reuse the same custom questions across multiple jobs? Yes — add them at the template level (Settings → Jobs & Applications → Application Forms). Any job using that template picks up the questions automatically. You can also clone a form to reuse its structure with small variations.

• Will candidates who already applied be asked a new question I just added? No — new or changed fields only apply to applications submitted after the change. Existing candidates' original answers are preserved as-is.

• Can I delete a custom question or section? Yes for both — hover over a field or section and use the delete icon. Deleting a section removes every field inside it. Built-in fields in the Personal Info and Profile sections can't be deleted.

• What happens if a candidate skips an optional custom question? Their application still submits normally — optional questions don't block submission if left blank.

• I can't find where to add a custom question on a specific job — where is it? Job → Job Post Settings → Application Form section. If you're deciding between job-level and template-level, ask whether the question is role-specific (job level) or should apply broadly (template level).

Need help?

If a field type isn't behaving as expected, knockout rules didn't clone correctly, or a file-type answer is displaying incorrectly elsewhere in Kula, contact Kula support.