A job is the central record for a role you're hiring for. It's where everything about that role comes together — the pipeline, the hiring team, the job description, and every candidate who's applied.

Who can do this: Viewing and working within a job depends on your role and permissions — typically Recruiters, Hiring Managers, Admins, and Super Admins, scoped to the jobs they're part of unless broader visibility has been granted.

Where to find it: Jobs module (left-hand navigation)

What a job contains

Jobs vs. job posts

• A job and a job post aren't the same thing. The job is the internal record — it holds the pipeline, hiring team, and candidate data.

• The job post is the public-facing listing, configured under the job's Settings, and it's what determines whether the role shows up on your career portal or job boards.

• A job can exist without a job post at all — candidates can still be added to it manually.

• A job post can also be unlisted: it generates a direct link you can share, but it won't appear publicly or be indexed.

Jobs vs. requisitions

• If requisitions are enabled for your org, a job and a requisition are two different things that work together, not two names for the same object. The requisition is the headcount request — it goes through its own approval flow before a job is created against it.

• The job is what recruiters actually work in day to day: the pipeline, hiring team, and candidates.

• In orgs where requisitions are enabled and set as mandatory, you can't create a job without linking it to an approved requisition. If that setting isn't turned on, jobs can be created independently.

Who can create jobs

By default:

• Admins and Super Admins can create and manage all jobs.

• Recruiters can create jobs if the permission is enabled for their role.

• Hiring Managers can be added to jobs but typically can't create them.

A video showing briefly about Requisition creation and Jobs:

Good to know

• A candidate can apply to more than one job. Each application is tracked separately, even for the same candidate.

• Closing a requisition doesn't automatically close its linked job. If a requisition is marked filled, the job it's tied to stays open until someone closes it manually.

• Each job has exactly one job post, which can be listed (public) or unlisted (direct link only) — not multiple posts per job.

FAQ

• What's the difference between a job and a job post? The job is the internal record — pipeline, hiring team, candidates. The job post is the public listing tied to it, configured under the job's settings, and it's what candidates actually see. For more, see Jobs List View Explained (link to be added).

• What's the difference between a job and a requisition? They're separate objects that work together. A requisition is a headcount request that goes through its own approval before a job is created against it; the job is where day-to-day recruiting happens once that's done. This only applies if requisitions are enabled for your org. For more, see Applying an Interview Plan to a Job (link to be added).

• Can I have a job without publishing it? Yes. A job can stay entirely internal with no job post, or have an unlisted post reachable only by direct link. For more, see Job Status: Draft, Open, Closed (link to be added).

• Can a job have multiple job posts? No — each job has one job post, which is either listed or unlisted. For more, see Job Status: Draft, Open, Closed (link to be added).

• If I mark a requisition as filled, does the job it's tied to close automatically? No — the job stays open until it's closed manually, even after its requisition is filled. For more, see Archiving and Closing a Job (link to be added).

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.