← All hiring guides
Urban Planner

How to Write a Urban Planner Job Description

A urban planner job posting needs to screen for defensible, community-informed planning recommendations, not just zoning paperwork — not just list duties. Here's what to include and what actually filters for the right candidates.

What this role actually needs to prove out

Before writing requirements, get clear on the one thing a strong urban planner candidate has to demonstrate: defensible, community-informed planning recommendations, not just zoning paperwork. Every requirement you list should trace back to that, not to a generic template for the job title. A posting that just restates the job title in bullet-point form filters for nothing — it neither attracts strong candidates nor repels weak ones.

Must-have requirements to include

Keep this list short and real — these are the skills that actually predict success in the role, not a wish list:

  • Land-use/zoning analysis
  • GIS software
  • Community engagement facilitation
  • Regulatory compliance
  • Report/proposal writing

Nice-to-have — list separately, don't gate on these

Worth calling out as a plus, but requiring them as "must-haves" needlessly shrinks your pool:

  • AICP certification
  • Transportation or environmental planning specialization
  • Grant-writing experience

What a strong candidate's resume bullet looks like

Useful as a benchmark when screening — this is roughly what real, specific evidence of the role's core skill looks like on paper:

  • Led the community engagement process for a comprehensive plan update, gathering input from 500+ residents
  • Reviewed and approved 80+ development proposals annually for zoning compliance
  • Authored a rezoning proposal that was adopted by city council, enabling 200 units of affordable housing

Titles candidates search for

People in this job look under several names: Town Planner, City Planner, Planning Officer, Land Use Planner. Use the title most of them search for as your heading, and work one or two of the others into the text so the posting is found by all of them.

A tip specific to this role

State the authority or sector, the types of applications and the tools.

What to look for on the CV

Applications or plans handled, the sector and GIS skill.

Credentials and checks to confirm

A planning qualification or professional membership where expected.

A starting job description for a urban planner

Fill in the brackets with your own details. The requirements come from this role's must-haves, so edit them to match your site.

Urban Planner

About the role
[Two sentences on your team and what this person will own.]

What you will do
- [Three to five responsibilities specific to your site]

What you need
- Land-use/zoning analysis
- GIS software
- Community engagement facilitation
- Regulatory compliance
- Report/proposal writing

A plus
- AICP certification
- Transportation or environmental planning specialization
- Grant-writing experience

Before you start
- A planning qualification or professional membership where expected.

What we offer
- [Pay range, hours or shift pattern, location]

Notice periods & salary disclosure, by country

Hiring for this role in a specific market? These vary enough to affect your timeline and posting requirements — see the full sourcing and interview guides for this role too.

CountryTypical notice periodSalary disclosure
🇮🇳 India30-90 days is standard, often negotiable with a buyoutNot legally required; increasingly expected on job boards for volume roles
🇺🇸 United StatesAt-will employment — typically 2 weeks, not legally mandatedIncreasingly required by state law (CA, CO, NY, WA and others) to post a range
🇬🇧 United Kingdom1 week to 3 months depending on seniority and contract, often longer for senior rolesNot legally required, but a stated range is increasingly expected and improves application rates
🇨🇦 Canada2 weeks is common but varies by province's employment standardsLegally required in Ontario and British Columbia for job postings; increasingly expected elsewhere
🇦🇺 Australia2-4 weeks typical, sometimes longer for senior rolesNot legally required nationally, but expected on major job boards and increasingly the norm
🇲🇽 MexicoTypically 1-2 weeks by custom, though not always formally mandatedNot commonly disclosed in postings, but expected during initial screening conversations
🇧🇷 Brazil30 days is the statutory minimum under CLT employmentNot commonly disclosed in postings; increasingly common for international-facing roles
🇻🇳 Vietnam30-45 days is standard for formal employment contractsNot commonly disclosed for local roles; more common for international/remote postings
🇮🇩 Indonesia30 days is the common statutory minimum for formal contractsNot commonly disclosed for local roles; more common for international/remote postings
🇫🇷 France1-3 months depending on role and collective bargaining agreement (convention collective)Not legally required in postings, but increasingly expected
🇦🇪 United Arab Emirates30-90 days typical, often defined explicitly in the employment contractNot commonly disclosed in postings; discussed directly during screening
🇩🇪 GermanyTypically 4 weeks to 3 months, longer with tenure — governed by contract and law (Kündigungsfrist)Not legally required nationally, but increasingly common and expected by candidates
🇯🇵 Japan2 weeks statutory minimum, though 1-3 months is customary by company policyNot commonly disclosed in postings; discussed during the process, sometimes via a recruiter intermediary
🇵🇱 Poland2 weeks to 3 months depending on contract type and tenureLegally required in job postings as of the EU Pay Transparency Directive's national implementation
🇵🇭 Philippines30 days is the common standard under the Labor CodeNot commonly disclosed for local roles; more common for BPO/international postings
🇸🇬 Singapore1 week to 3 months, commonly defined explicitly in the employment contractNot legally required, but a stated range is increasingly standard practice, especially for tech roles

Mistakes that scare off good candidates

  • Requiring years of experience as a proxy for skill (e.g. gating on "5+ years" when the real bar is demonstrated competence) — filters out strong candidates with less conventional paths.
  • Listing every tool/skill your team has ever touched as a "must-have," rather than the handful that actually predict success.
  • Burying the actual role and responsibilities under generic company boilerplate that could apply to any posting.
  • Not stating public or private sector. The pace, the clients and the career path differ, and candidates choose on them.

Frequently asked questions

What should I put at the top of a urban planner job posting?

A short intro (1-2 sentences) on the role and team, then straight into responsibilities and requirements. Candidates skim the first few lines to decide whether to keep reading — don't bury the actual role behind company boilerplate.

How many requirements should a urban planner job description list?

Split them into must-have (5 or fewer — every extra must-have measurably shrinks your applicant pool) and nice-to-have. A JD that lists 15 "requirements" with no distinction screens out strong candidates who'd have been a genuinely good fit.

Should I list a salary range?

Where legally required or common in your market, yes — it's increasingly expected, and its absence is one of the top reasons strong candidates skip an otherwise good posting without applying.

What other titles do people use for a urban planner?

The same job is also called Town Planner, City Planner, Planning Officer, Land Use Planner. Use the title candidates search for in the posting, and mention the others once in the text so the posting is found.

What should I check before hiring a urban planner?

A planning qualification or professional membership where expected.

Hiring a urban planner? The rest of the toolkit

See it on a real hire

Open a private demo with fictional candidates and walk a hire from job description to offer. No sign-up needed.

Try the live demo →