Senior Public Realm Transportation Planner (Planner, Sr City-Transportation)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. No invented or summarized away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - The Position Job Appointment: Full-Time Work Schedule: Monday - Friday 8:00 - 5:00 An alternate schedule may be available - Benefits: Please check our benefit tab for an overview of benefits for this position. - Union Representation: PROTEC17 . To view labor agreements, current and future, please visit the Current City Labor Agreements page . - Application Material: Please click APPLY to submit your application via the City of Portland’s online portal. You will need to respond to the supplemental questions and attach a resume. - The City of Portland is seeking a highly motivated Senior City Transportation Planner to lead transportation planning, program and policy design projects within the Policy Innovation and Regional Collaboration Section in the Portland Bureau of Transportation's Planning Division. - Senior City Transportation Planners are team leaders, project managers and top-level technical experts for the Planning Division of PBOT. - What You’ll Get To Do (list of responsibilities) - Who You Are (list of qualifications/skills/experience) - About The Division (description) - Questions Terrol Johnson Senior Recruiter terrol.johnson@portlandoregon.gov - To Qualify Qualifications Applicants must specifically address and demonstrate in their supplemental question responses and resume how their education, training and/or experience, meets each of the following minimum qualifications: (list) - Although Not Required, You May Have a Degree in Urban Design or Urban Planning - The Recruitment Process (steps) etc. - Salary Range/Equity Pay Analysis: Please note per the Oregon State Pay Equity Law , your salary is determined based on the experience and education listed in your resume/application. It is strongly encouraged to include any transferable experience (paid or unpaid, regardless of how recent) to ensure your offer is reflective of all directly related and equivalent experience. - Additional steps etc. - Additional Information Click here for additional information regarding the following: City of Portland Core Values Recruitment Process - Work Status Equal Employment Opportunity Veteran Preference ADA, Pregnancy, and Religious Accommodations - Did you know? The City of Portland has How to Apply Videos and offers How to Apply Classes once per month. If you have questions after watching the videos you are invited to contact the recruiter listed on the announcement. An Equal Opportunity Employer We need to remove boilerplate: navigation, legal, EEO, equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Application Material: Please click APPLY..." etc. Also remove "Questions Terrol Johnson..." maybe keep contact? Not sure if that's considered boilerplate. Probably it's contact info, but might be considered part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So contact info maybe not boilerplate but could be considered application instruction? It's not exactly instruction to apply, but it's contact for questions. Might be okay to keep? The instruction says remove application instructions. Contact info is not exactly instruction but could be considered part of application process. Safer to remove it? The instruction says remove application instructions, not necessarily contact. But "Questions Terrol Johnson Senior Recruiter terrol.johnson@portlandoregon.gov" is likely a contact for questions, which could be considered part of application instructions. I'd remove it to be safe. Also remove "Although Not Required, You May Have a Degree in Urban Design or Urban Planning" maybe keep as part of qualifications? It's a qualification note. It's substantive. We need to decide sections: - About the role: maybe a brief description of the role: "The City of Portland is seeking a highly motivated Senior City Transportation Planner to lead transportation planning, program and policy design projects within the Policy Innovation and Regional Collaboration Section in the Portland Bureau of Transportation's Planning Division. Senior City Transportation Planners are team leaders, project managers and top-level technical experts for the Planning Division of PBOT." That's substantive. - Responsibilities: the "What You’ll Get To Do" list. - Requirements: maybe combine "Who You Are" and qualifications? But we have separate sections: Requirements, Qualifications, Skills. The instruction: use headings for those categories if content exists. We need to decide what goes where. We have "Who You Are" which lists attributes: Experienced Planner, Excellent Collaborator, Equity Focused, Excellent Communicator, Dedicated, Authentic, Project Manager. Those are more like skills/qualities. We have "To Qualify Qualifications" list: specific minimum qualifications. We have "About The Division" description. We have schedule info: Full-Time Work Schedule: Monday - Friday 8:00 - 5:00 An alternate schedule may be available. We have benefits: "Please check our benefit tab for an overview of benefits for this position." That's vague; not specific. According to rule: never create Benefits section unless posting actually states them. It does state benefits but only says "please check our benefit tab". That's not specific substantive content. Should we include Benefits? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits but not specifics. However it's still stating that there are benefits, but not detailing. The rule says "never create ... Benefits sections unless the posting actually states them." It does state them (mention benefits). But also rule: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits statement is vague but not placeholder like "not specified". It's a direction to check benefit tab. Might be considered not specific content. Safer to omit Benefits section. Schedule: we have specific schedule: Monday - Friday 8:00 - 5:00, alternate schedule may be available. That's specific. So we can include Schedule section. Pay: we have Salary Range/Equity Pay Analysis: says salary determined based on experience and education per Oregon State Pay Equity Law, encourage to include transferable experience. No specific range. That's not specific numbers. It's more like explanation. According to rule: never create Pay section unless posting actually states them. It does state something about pay but not a range. It's not a specific number or range. It's more like policy. Likely we should omit Pay section because no concrete pay info. Thus sections: About the role, Responsibilities, Requirements (maybe combine Who You Are and qualifications?), Qualifications (maybe the To Qualify list), Skills (maybe Who You Are?), Benefits omitted, Pay omitted, Schedule included. But we need to avoid duplication. Let's think: The posting has "Who You Are" which is a list of desired attributes/skills. That could go under Skills. The "To Qualify Qualifications" list is specific minimum qualifications, could go under Qualifications. The "About The Division" could go under About the role? Or maybe we could have About the role as description of role and division. But we already have About the role description earlier. Could combine division info into About the role. Better: About the role: includes the description of the role and division. Responsibilities: the What You’ll Get To Do list. Qualifications: the To Qualify list (minimum qualifications). Skills: the Who You Are list (attributes). Schedule: the schedule info. We should not include Requirements heading if we don't have distinct content; we could omit Requirements. Thus output:

About the role

The City of Portland is seeking a highly motivated Senior City Transportation Planner to lead transportation planning, program and policy design projects within the Policy Innovation and Regional Collaboration Section in the Portland Bureau of Transportation's Planning Division. Senior City Transportation Planners are team leaders, project managers and top-level technical experts for the Planning Division of PBOT. PBOT's Planning Division is a nationally recognized leader in the development of policies, plans, and projects that promote livability, prosperity, sustainability, equity, and safety. The Planning Division shapes the City and manages growth to meet ambitious goals including developing active public spaces. Staff develops long-range transportation area, corridor and safety plans, and streetscape plans, writes policy and code language and identifies multimodal projects such as high-capacity regional transit projects, freight, bicycle and pedestrian projects, and major capital infrastructure, and transforms right of way into public spaces that support the City's goals.

But we need to ensure we don't invent or summarize away detail. The division description is from "About The Division". We can include that as part of About the role. Now Responsibilities: list from "What You’ll Get To Do". Need to preserve all substantive information, not summarize away detail. So we need to copy each bullet as

. Let's extract: - Lead the development of a Curb Management Framework to more holistically guide the prioritization of access to valuable curb space across multiple uses beyond parking. - Serve as program lead and project manager as PBOT explores, develops, and implements an updated policy and implementation approach in established and emerging parking management areas. - Advance ongoing evolution and implementation of current work program assignments related to parking management plan development and implementation, such as establishing new Parking Management Districts that enable additional permit and paid parking projects in specific geographic areas. - Lead, manage, and provide the highest-level expertise on policy, program and project approaches to advancing holistic curb management in support of adopted city goals. - Exercise expert independent judgment, initiative, and decision-making authority to develop to develop timely and innovative solutions to complex curb management challenges and opportunities. - Serve as project manager and/or PBOT representative on complex and politically sensitive planning, urban design, and infrastructure projects. - Deliver excellent programs and projects through strong partnerships with community organizations, residents, businesses, elected officials, and staff in other parts of PBOT and the City. - Prepare studies, analyses, renderings, models, and other written, verbal, and visual materials addressing a variety of transportation and urban design issues. - Implement innovative parking and curb management programs that advance City and bureau values of addressing racism and enhancing equity in action and outcome. - Be a key resource on transportation plans and projects that serve community goals and create great places while supporting mobility and access on city streets. - Engage a diverse range of people and communities; meaningfully center community members and deploy an equity framework that ensures outcomes are equitable and that underrepresented communities benefit from parking and curb management decisions and investments. Note there is a duplicate "develop to develop" maybe a typo but we preserve as is. Now Qualifications: from "To Qualify Qualifications" list: - Experience applying theories, principles, standards, practices, and current trends in transportation planning and policy, parking and curb management, urban design, and space utilization to address growth management issues. - Ability to manage large, complex, and politically sensitive transportation projects and contracts, including setting budgets, managing schedules, and ensuring the quality of work products. - Experience consulting with and managing teams, building effective working relationships, resolving conflicts, and building support at all levels of an organization and with diverse stakeholders. - Experience using effective communication skills and producing high-quality visual representations of spatial information related to land use and urban design. - Experience developing and coordinating equity-focused public involvement and outreach for complex and politically sensitive projects. Also "Although Not Required, You May Have a Degree in Urban Design or Urban Planning" - we could include as a note maybe as a

after list. Now Skills: from "Who You Are" list: - Experienced Planner: You are an expert transportation planner who can manage a dynamic workload with demonstrated experience in policy and program development and implementation,