Planner

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have: - About the role: The first paragraph: "Wilson & Company is seeking a motivated and collaborative Planner to join our team in Phoenix, AZ. This position will support a variety of community planning, land use, transportation planning, and public engagement projects throughout the region. The Planner will work closely with planning and engineering staff on projects including comprehensive plans, zoning codes, economic development studies, corridor and area studies, feasibility studies, multimodal planning studies, public engagement efforts, transportation master plans, and other planning assignments. This role offers opportunities to contribute to meaningful projects while developing technical expertise and project management skills." That's about the role. - Responsibilities: "Essential Job Functions" list: Support planning projects from initiation through completion, coordinating tasks with project teams and clients. Conduct research, collect and analyze data, and develop planning recommendations. Prepare technical reports, presentations, maps, graphics, and other project deliverables. Assist with stakeholder meetings, workshops, public engagement activities, and client presentations. Collaborate with multidisciplinary teams of planners, engineers, and other professionals. Manage assigned project tasks, schedules, and budgets with guidance from senior staff. Support proposal development and other business development activities as needed. - Requirements: Might be same as qualifications? The posting has "Required Skills" and "Required Qualifications". We need to map to sections: Skills, Qualifications. Possibly "Requirements" could be used for required skills? But we have separate Skills and Qualifications sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications and Skills. We need to decide what goes where. We have "Required Skills" list: Strong verbal and written communication skills, including presentation development and delivery. Strong analytical and problem-solving abilities. Proficiency with GIS, Microsoft Excel, Word, and PowerPoint. Ability to organize and synthesize data into clear, compelling planning documents and presentations. Strong graphic, mapping, and visual communication skills. Ability to work both independently and collaboratively in a team environment. We have "Required Qualifications": Bachelor's degree in Planning, Urban Planning, Community and Regional Planning, Engineering, Geography, or a related field. 2-4 years of planning-related experience. Experience preparing technical reports, data analyses, graphics, and presentation materials. Knowledge of community planning, land use planning, transportation planning, and public engagement practices. Experience supporting planning studies, plans, or policy development efforts. Ability to manage multiple assignments and meet project deadlines. AICP certification or progress toward AICP is preferred. We also have "Please note that Wilson & Company is not currently sponsoring applicants for work visas." That's metadata; we can fold into a short p or drop. Probably include as a short p under maybe About the role? But we can drop as minor metadata. We have "Annual Salary Range: $62,000 - $82,000 (Depending on Experience)" => Pay section. We have benefits description: "We support our employees’ success and well-being with a comprehensive benefits package, including options for health insurance, life insurance, disability coverage, paid time off, and retirement savings plans." That's Benefits. Schedule: Not mentioned. So we should NOT include Schedule heading. We also have "About Us" section: description of company. Could be considered "About the role"? Actually "About Us" is separate. But we already have About the role; we could include About Us as part of About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add About Us heading unless we map it to About the role. The About the role already includes description of role; we could also incorporate company description there, but maybe better to keep About the role as role description and maybe add a separate "About the company"? Not in allowed headings. So we could incorporate the About Us content into About the role section, or we could drop it as boilerplate? It's not boilerplate; it's substantive about company. But the allowed headings list does not include "About the company". However we could still include it under About the role as extra description. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But likely they expect only those headings. Safer to stick to those headings and incorporate About Us content into About the role. Thus About the role will contain both role description and company overview. Now we need to output HTML fragment only, no /. Use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep all details from the posting. Let's extract details: About the role (combined): - Wilson & Company is seeking a motivated and collaborative Planner to join our team in Phoenix, AZ. - This position will support a variety of community planning, land use, transportation planning, and public engagement projects throughout the region. - The Planner will work closely with planning and engineering staff on projects including comprehensive plans, zoning codes, economic development studies, corridor and area studies, feasibility studies, multimodal planning studies, public engagement efforts, transportation master plans, and other planning assignments. - This role offers opportunities to contribute to meaningful projects while developing technical expertise and project management skills. - About Us: For nearly a century, Wilson & Company, Inc., Engineers & Architects, has provided award-winning engineering, architecture, planning, environmental, surveying, geospatial, and construction management services. With employees across multiple offices in the Midwest, Southwest, Rocky Mountain, and Western regions in the United States, we bring people together to practice their craft, create value, and accomplish great things. Guided by our purpose, we help clients move from concept to completion, transforming unused spaces into productive places, underutilized facilities into efficient ones, and rural or urban challenges into achievable solutions. At Wilson & Company, we focus on your specific needs, delivering excellence with lasting Higher Relationships in mind. By employing our core values—discipline, intensity, collaboration, shared ownership, and solutions—we create genuine experiences and lasting connections for our clients, employees, and communities. We support our employees’ success and well-being with a comprehensive benefits package, including options for health insurance, life insurance, disability coverage, paid time off, and retirement savings plans. We are proud to be an EEO employer and maintain a drug-free workplace, conducting pre-employment background checks. Join us and be part of a culture committed to helping you achieve personal and professional success. But note: Benefits description appears also in Benefits section; we might duplicate if we include in About the role. Better to keep Benefits separate and not duplicate. So we should not include benefits description in About the role; we can keep About the role limited to role description and maybe company overview without benefits. However the About Us paragraph includes benefits sentence; we could split: keep company overview but exclude benefits sentence. But we must preserve ALL substantive information; we cannot omit the benefits sentence entirely because it's substantive. However we will have a Benefits section later that includes that sentence. So we can omit it from About the role to avoid duplication, but we still need to preserve it somewhere; we will put it in Benefits section. That's fine. Thus About the role will include role description and company overview excluding benefits sentence. Let's craft: "Wilson & Company is seeking a motivated and collaborative Planner to join our team in Phoenix, AZ. This position will support a variety of community planning, land use, transportation planning, and public engagement projects throughout the region. The Planner will work closely with planning and engineering staff on projects including comprehensive plans, zoning codes, economic development studies, corridor and area studies, feasibility studies, multimodal planning studies, public engagement efforts, transportation master plans, and other planning assignments. This role offers opportunities to contribute to meaningful projects while developing technical expertise and project management skills. For nearly a century, Wilson & Company, Inc., Engineers & Architects, has provided award-winning engineering, architecture, planning, environmental, surveying, geospatial, and construction management services. With employees across multiple offices in the Midwest, Southwest, Rocky Mountain, and Western regions in the United States, we bring people together to practice their craft, create value, and accomplish great things. Guided by our purpose, we help clients move from concept to completion, transforming unused spaces into productive places, underutilized facilities into efficient ones, and rural or urban challenges into achievable solutions. At Wilson & Company, we focus on your specific needs, delivering excellence with lasting Higher Relationships in mind. By employing our core values—discipline, intensity, collaboration, shared ownership, and solutions—we create genuine experiences and lasting connections for our clients, employees, and communities. We are proud to be an EEO employer and maintain a drug-free workplace, conducting pre-employment background checks. Join us and be part of a culture committed to helping you achieve personal and professional success." Now Responsibilities: list as above. Requirements: Could be used for "Required Skills"? But we have Skills heading separate. The instruction list includes Requirements as a possible heading. We could put "Required Skills" under Requirements, and "Required Qualifications" under Qualifications. Or we could put skills under Skills and qualifications under Qualifications, and maybe Requirements could be omitted if not needed. But we need to include sections only when posting has real specific content. We have content for Skills and Qualifications. We could also have Requirements as a combination of both? But better to follow the example: they gave list of possible headings; we can choose which to use. Likely they expect us to use Skills for required skills, Qualifications for required qualifications, and maybe Requirements for something else like "Required experience"? But we already have qualifications covering experience. So we could omit Requirements heading to avoid thin sections. However we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine if possible. Could we put both skills and qualifications under a single "Requirements" section? But they differentiate Skills and Qualifications in the list. However we could still use Skills and Qualifications headings; they are substantive. Thus we will include: - About the role (h3) - Responsibilities (h3) - Skills (h3) for Required Skills - Qualifications (h3) for Required Qualifications - Benefits (h3) for benefits package - Pay (h3) for salary range We will not include Requirements or Schedule. Now we need to format lists. Skills list: - Strong verbal and written communication skills, including presentation development and delivery. - Strong analytical and problem-solving abilities. - Proficiency with GIS, Microsoft Excel, Word, and PowerPoint. - Ability to organize and synthesize data into clear, compelling planning documents and presentations. - Strong graphic, mapping, and visual communication skills. - Ability to work both independently and collaboratively in a team environment. Qualifications list: - Bachelor's degree in Planning, Urban Planning, Community and Regional Planning, Engineering, Geography, or a related field. - 2-4 years of planning-related experience. - Experience preparing technical reports, data analyses, graphics, and presentation materials. - Knowledge of community planning, land use planning, transportation planning, and public engagement practices. - Experience supporting planning studies, plans, or policy development efforts. - Ability to manage multiple assignments and meet project deadlines. - AICP certification or progress toward AICP is preferred. Note: Also note "Please note that Wilson & Company is not currently sponsoring applicants for work visas." This is minor metadata; we can fold into a short p or drop. Probably drop as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short p after About the role maybe: "

  Wilson & Company is not currently sponsoring applicants for work visas.

  " That's minor metadata