Sr. Project Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - About The Role (section heading "About The Role") -> we need to use

About the role

(case? Use exactly as given? Probably "About the role"). - Specific Responsibilities -> we can map to "Responsibilities" heading. - Required Qualifications -> "Qualifications" heading. - Desired Qualifications -> maybe "Skills" or "Qualifications"? Could be separate "Skills" heading. The posting includes "Desired Qualifications" with bullet items: PMP, Permitting and Licensing knowledge. Could be placed under "Skills" or "Qualifications". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Qualifications" for required qualifications, and "Skills" for desired qualifications (or maybe "Requirements" for required? Actually they gave list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Required Qualifications" which could go under "Qualifications". Also "Desired Qualifications" could go under "Skills". There's also "About Accela" which is company description; not a required heading; could be omitted or maybe part of About the role? But we should preserve all substantive information. The "About Accela" is substantive but not fitting any of the prescribed headings. However instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must only use those headings; we can use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we could also use other headings if needed, but better to stick to those. However "About Accela" is not one of those examples; but we could incorporate it into "About the role" maybe? But that would be mixing. Better to create a heading "About Accela" as

About Accela

even though not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add other headings as needed. We'll include About Accela as its own section. Also there is "OUR COMMITMENT TO DIVERSITY, EQUITY, AND INCLUSION" and "Compensation And Well-being". Those could map to Benefits and Pay sections. "Compensation And Well-being" includes salary range, bonus, benefits. So we can have Pay section for salary range and bonus, Benefits section for benefits description. Also there is "Accela is an Equal Opportunity Employer..." which is boilerplate EEO; we should remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we strip the EEO statement at end. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. There's no job ID visible. We need to output ONLY the HTML fragment — no /, no markdown code fences. Thus produce something like:

  About the role

  ... (the About The Role paragraph)

  Responsibilities

  As the owner of the cross-functional Professional Services delivery process you will make significant impacts on the customer and Accela's business in these key areas:

  • Project Management: Manage engagements start-to-finish by applying standard and accepted project management principles; lead project planning and budgeting; mobilize and direct the work streams of cross-functional project teams; champion the Statement of Work; convert scope change into a change order rather than letting the team absorb it silently.
  • Project Health: Drive on-time and on-budget completion of projects; track project progress and variability; maintain a RAID log - risks, assumptions, issues and dependencies - as the working record; work collaboratively with customer and internal teams to identify risks; develop and execute appropriate risk mitigation strategies within a defined escalation path; implement appropriate tracking and reporting metrics in a manner that provides transparency and visibility into project health; run a weekly budget-burn review - hours consumed against hours contracted, percent complete against percent budget - to surface at-risk engagements early; report on-time go-live rate, budget variance, time-to-go-live and SLA attainment.
  • Tooling and Project Record: Run your engagements in Jira against the standard implementation project template - consistent epics, issue types, workflow states and a definition of done per phase - rather than a parallel tracker; keep the per-customer space current with environments, contacts, configuration decisions, go-live checklists and retro notes; maintain per-customer dashboards and saved filters so status, aging and blocked items are visible to leadership without a bespoke report; contribute requirements for Jira, GitHub and configuration-repository integration so work is traceable from issue to deployment.
  • Go-Live and Transition: Own the go-live readiness review; make the handoff into Customer Success and support a defined event with explicit acceptance criteria rather than a fade-out; run a lessons-learned review after every go-live and feed the findings into the implementation playbook.
  • Customer Relationship Management: Foster an environment of highly effective and collaborative communications in day-to-day interactions with clients and stakeholders; serve as the first point of escalation on the project; support Regional Director in executive steering committees; track customer-side dependencies as the real critical path - workflow decisions, record type and Standard Choice sign-off, test participation, approvals and training scheduling; initiate escalation when a customer is unresponsive or a configuration decision is stuck, rather than leaving the implementer to chase it.
  • Cross Functional Teamwork: Lead and support collaboration across many internal stakeholder groups - Consultants, Architects, Project Management Office, Cloud Operations, Product, Support, Partners and others. On joint Civic Platform and ePermitHub programs, coordinate with the counterpart project manager on dependency mapping, milestone alignment and shared-risk visibility, and represent the program's scope in steering meetings.
  • Business Development: Support initiatives to grow new business and expand existing projects; participate in aspects of the proposal development process and budget estimation.

  Qualifications

  Required Qualifications

  • Government Enterprise Software - 5 years leading successful implementations of COTS software/platform-based solutions for Tier-1 government clients, or clear evidence of navigating slow, committee-driven stakeholder groups.
  • Complex Projects - 5 years leading projects of $1M+ budget, 12+ months duration, and involving more than one government department or group.
  • Proven ability to manage multiple complex projects that are at various stages of delivery.
  • Comfortable owning budget and burn, and having scope conversations directly with customers.
  • Aptitude for understanding and applying new technologies and methodologies.
  • BA or BS in a technical discipline, or similar technical degree program.
  • Use of formal project management tools (e.g., MS-Project, Visio, etc.).
  • Working proficiency in Jira and Confluence, including building boards, dashboards and saved filters - not only working tickets.
  • Strong technical background, with previous experience with delivery of enterprise class software - enough technical literacy to read a configuration repository and a workflow diagram without needing translation.
  • Strong analytical skills and experience managing technical and project management issues.
  • Strong organizational skills with an ability to manage competing client demands.
  • Ability to interact and communicate with CxO-level personnel.
  • Excellent communications and interpersonal skills.
  • Ability to travel up to 50% percent of the time.

  Skills

  Desired Qualifications

  • Project Management Certification - Certified Project Management Professional (PMP) preferred; skilled at identifying the appropriate strategies and tools for planning and tracking complex projects and driving teams to high productivity.
  • Permitting and Licensing knowledge desired.

  About Accela

  For nearly 20 years, Accela has been an industry leader in designing and delivering government software to improve efficiency, increase citizen engagement and enable the development of thriving communities. Today, citizens are savvy to how services should be delivered, and expect a consistently convenient, openly transparent view into their local government. While government agencies struggle to do more with less, our mission has never been more critical. Accela provides a robust, cloud-based platform of government software solutions that accelerate growth, efficiency, and transparency in communities of all sizes. From planning, to building, to service request management and more, Accela’s SaaS offerings level the playing field for small and medium governments and enable smaller agencies to leverage larger city technologies. Our open and flexible technology helps agencies address specific needs today, while ensuring they are well prepared for the emerging challenges of the future.

  Pay

  The annual base salary range for this full-time position is $140,000-$160,000 (less applicable taxes). The actual annual base salary offered may be adjusted based on a variety of factors, including but not limited to, location, education, skills, training, and experience. In addition to an annual base salary, this position is eligible for an annual bonus target. This is a discretionary bonus awarded based on company and individual goal achievement.

  Benefits

  Accela’s U.S. team members will receive a generous benefits package consisting of options including flexible time off, comprehensive medical, dental, and vision plans, family planning benefits, 401(k) retirement savings plan with company match, health savings account with company contributions, flexible spending account, life, accident, and disability coverage, business travel insurance, employee assistance programs, and other well-being benefits.

  We should also include the OUR COMMITMENT TO DIVERSITY, EQUITY, AND INCLUSION section? It's substantive but not covered by headings; we could add a heading "Diversity, Equity, and Inclusion". However the instruction says we can use headings for section headings (e.g. list). It didn't forbid other headings. But we might consider it as part of About Accela or separate. Since it's substantive, we should preserve it. Let's add a heading "Diversity, Equity, and Inclusion". Use

  Diversity, Equity, and Inclusion

  and then the paragraph. We need to ensure we didn't include any boilerplate like "Accela is an Equal Opportunity Employer/Affirmative Action Employer..." which we should remove. Thus final HTML fragment includes sections: About the role, Responsibilities, Qualifications, Skills, About Accela, Diversity, Equity, and Inclusion, Pay, Benefits. We should not include Schedule as no info. Check for any duplicated lines: we have not duplicated. Make sure we used

  for prose and

  • for lists. Check that we didn't accidentally put headings inside

    incorrectly. For Required Qualifications we put a

    Required Qualifications

    then