JobsFor recruiters4 min read

Creating a job

Every interview is anchored to a job. Here is how to create one from scratch — the required fields, the interview-mode settings, and what each field actually controls downstream.

Key takeaways

  • You need: a title, location, employment type, experience level, and a job description.
  • You can paste the JD as text or upload a PDF — we extract the same fields from both.
  • The interview duration (15/30/45 min) is set on the job, not per candidate.
  • Required Skills and Preferred Skills are used to weight evaluations against the JD.

Every interview in RecruitMe is anchored to a job. Before you can invite a candidate, you need at least one job in the system. This article walks through creating a job from scratch (typing the fields in directly). If you have a JD as a PDF, see Auto-parsing a JD from PDF — same outcome with less typing.

Opening the new-job form

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Alternatively, on the dashboard, click Create new job under quick actions.

The required fields

Job title

Be specific. Senior Frontend Engineer — React, TypeScript is better than Engineer. The title appears in candidate-facing emails and in the AI interview itself (the AI introduces itself by saying "You are here to interview for the role of <title>").

Location

City and country, or Remote. If hybrid, you can write Bengaluru, India (Hybrid). This is shown to candidates in the invitation email.

Employment Type

Full-time, Part-time, Contract, Internship. Affects nothing in the AI logic; purely informational for candidates.

Experience Level

Entry, Mid, Senior, Lead/Principal. This does affect the AI's expectations — Senior candidates are scored against a higher technical bar than Entry. Pick honestly; over-leveling a junior role makes candidates look worse than they are.

Years of Experience

Minimum years required. 5+ or 3–7. Used during evaluation when assessing Experience Relevance.

Openings

How many positions you are filling. Informational. Used by Analytics for funnel calculations.

Skills — Required and Preferred

Two separate lists. Add as many as relevant. Used by the AI when:

  • Asking questions during the interview — the AI biases questions toward your Required skills.
  • Scoring evaluations afterwards — strong Required-skill coverage boosts Experience Relevance and Technical Competence; missing them drops both.

TIP

Be specific. *React* is a fine skill; *React Server Components* tells the AI you care about modern usage. *Project management* is vague; *Agile / Scrum* and *Stakeholder communication* are sharper. Aim for 5–10 Required and 3–8 Preferred.

Job Description

The full text of the JD — responsibilities, what the team does, what you are looking for, what a successful candidate looks like at 6 months. Anything you would put in a public posting. The AI uses the JD when generating the interview plan (the questions it will ask).

TIP

If you wrote a great JD for the LinkedIn posting, paste it here verbatim. The AI extracts whatever it needs.

Interview settings

Below the JD section:

Interview duration

15 minutes for screening calls. 30 minutes for first-round interviews — the most common choice. 45 minutes for senior or principal roles where you want depth on technical and behavioural fronts.

This controls how many credits each interview consumes (0.5 / 0.75 / 1.0 — see How credits work).

Interview mode

Three options:

  • AI-only — fully autonomous AI interview. The default and what most jobs use.
  • Assessment Call — adds a structured live-coding / case-study segment within the interview. Configurable per job.
  • Live Assessment — schedules a real-time slot where a human interviewer is also present. Used rarely.

Cultural values (optional)

If you skip this, the AI uses generic defaults. To customise, list 3–5 values that describe how your team actually works — be specific. "Disagree-and-commit in writing" is sharper than "team player."

Publishing the job

Once you fill everything in, click Create Job. The job appears in your Jobs list with status Open. It is now ready to accept candidates and invitations.

Jobs list showing multiple created jobs with status badges
Your Jobs list — newly created jobs appear with an *Open* status badge.
Job detail page with Skills, Job Description, and Candidates panel
Job detail page after creation — you can edit any field, add candidates, or close the job from here.

Editing later

Open the job and click Edit. Most fields are editable any time. Changes apply to future interviews — interviews that already happened are scored against the JD as it was at interview time, not the current state.

Next: how to skip the typing by uploading a PDF.

Frequently asked questions

Can I duplicate an existing job to save typing?

Yes. Open the job, click the overflow menu (three dots) in the header, choose *Duplicate*. A new draft job appears with all fields copied — change the title and any details that need updating, then publish.

Can I edit a job after it's published?

Yes. Open the job → *Edit*. Most fields can be changed at any time. Changing the JD or skills after candidates have already interviewed will *not* re-score them — the evaluation locks against the JD at interview time.

What does *Close Job* do?

Closing stops the job from accepting new candidates and new invites. Existing interviews can still be completed and reviewed. You can re-open a closed job at any time.

What's the difference between Required and Preferred skills?

Required skills are weighted heavily in the Experience Relevance and Technical Competence scores. Preferred skills are weighted lighter — their absence does not penalise much; their presence is a positive. Use Required for must-haves and Preferred for nice-to-haves.

Next steps

Related articles