How to choose a long-term occupation in Project Zomboid

Choose an occupation for the work your character will repeat, then verify every occupation-specific claim on the build you are actually playing.

Start with your long-term routine

Turn a vague search for the strongest occupation into a playstyle-specific decision.

• List the duties the character is expected to perform repeatedly.
• Identify the setbacks or responsibilities that most often disrupt the intended run.
• Separate frequent needs from tasks that may occur only occasionally.
• Set one non-negotiable priority and one drawback you are unwilling to accept.

Confirm the build and displayed options

Keep the comparison tied to the occupation information available in the player's current installation.

• Record the installed build and branch before comparing occupations.
• Read each relevant occupation description directly in the current game.
• Transcribe important wording instead of relying on remembered summaries.
• Mark any unstated effect, value, exclusivity claim, or permanence claim as unresolved.

Isolate occupation-specific value

Evaluate the occupation itself before adding a broader trait plan.

• Note only the benefits and drawbacks explicitly associated with each candidate on the current screen.
• Ask how often each stated benefit supports the planned routine.
• Check whether the candidate solves a recurring problem or merely improves an occasional task.
• Do not assume a feature is unavailable elsewhere unless the installed build establishes that distinction.

Compare opportunity cost

Choose between candidates using consistent criteria without inventing unsupported mechanics.

• Compare every candidate against the same recurring-duty list.
• Lower the rank of a benefit that the planned character would rarely use.
• Reject a drawback when there is no clear routine for managing it.
• Treat unresolved mechanical differences as test questions rather than facts.

Run a controlled comparison

Use limited testing to resolve experiential questions before committing to a longer character.

• Create disposable comparison characters on the same build.
• Keep non-occupation choices as consistent as practical.
• Test the one recurring duty or drawback that separates the finalists.
• Record whether the difference was useful, unsuitable, or still unresolved.

Build the remaining trait plan separately

Prevent overlap with the existing general trait-planning guide and preserve a clear editorial boundary.

• Select the occupation first using occupation-specific evidence and opportunity cost.
• Use the existing trait-planning guide for the wider positive-and-negative trait package.
• Recheck the combined character against the intended routine.
• Return to the occupation decision if the wider trait plan depends on an unverified assumption.

Decision checklist

• Record the installed build and branch.
• Write down the character's recurring long-term duties.
• Choose one non-negotiable priority.
• Copy the current descriptions of the leading occupations.
• Mark unsupported exclusivity or permanence claims as unresolved.
• Compare every candidate against the same criteria.
• Test the finalists with disposable characters.
• Keep occupation selection separate from the wider trait plan.

Worked example

A player expects one character to handle a repeated base duty and occasional travel. Candidate A's current description states an advantage that directly supports the repeated duty, while Candidate B's stated advantage applies mainly to the occasional task. Candidate A should lead the shortlist if its displayed drawback is manageable. If the player has merely heard that Candidate B includes an exclusive or permanent feature, that claim stays out of the decision until the installed build confirms it. A short disposable-character comparison can then test the practical difference without turning the result into a universal recommendation.

Common mistakes

• Choosing from an old occupation tier list without checking the installed build.
• Treating a remembered effect as if the current game documents it.
• Assuming an occupation-specific feature is exclusive or permanent without current confirmation.
• Valuing an occasional benefit above support for a repeated duty.
• Changing the occupation and the wider trait package during the same comparison.
• Keeping a drawback without a practical plan for managing it.

Related guides