Revenue Systems Product Manager

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key content: - Position Description: description of role, purpose statements, etc. Could be "About the role" section. - Job Responsibilities: bullet list of responsibilities. - Qualifications: Required Qualifications and Desired Qualifications. - Additional Information: Salary (Pay), Benefits, Telework Expectations (Schedule?), maybe schedule. - Also "More About What You’ll Be Doing" subpoints: could be part of responsibilities. We need to produce sections: About the role (maybe from Position Description). Responsibilities (list). Qualifications (maybe combine Required and Desired). Skills? Could be derived from qualifications but maybe not needed if not explicit. Benefits and Pay sections: we have salary and benefits. Schedule: telework expectations (hybrid, minimum three days onsite per week). So we can include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual salary range and benefits description. We must not include application instructions, EEO boilerplate, etc. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

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

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The position description paragraphs: "The City of Seattle Information Technology (ITD) Department is seeking a Revenue Systems Product Manager (Strategic Advisor 2, exempt) to lead the City’s tax, business licensing, and cash receipting platforms, including partnerships with FileLocal and the multi-city tax portal. As part of a collaborative team, this role provides strategic technology leadership, product oversight, and vendor management—guiding product direction, aligning investments with business objectives, and ensuring reliable, secure delivery of enhancements, integrations, and operational stability—while working closely with Tax, Treasury, Licensing, and Finance to translate business needs into technical roadmaps and preserve business ownership of policy, workflows, and revenue operations. As a city, Seattle is recognized as a progressive leader in technology, innovation, and environmental stewardship. As an employer, the City of Seattle continues to lead local government in advancing environmental responsibility, social justice, and equitable services—values that shape both the city’s identity today and its vision for the future. The City’s workforce plays a critical role in making this progress possible. Seattle IT is a trusted partner that provides secure, reliable, and compliant technologies, enabling the City of Seattle to deliver equitable and responsive services to residents. This purpose statement reflects Seattle IT’s role and mission: it serves as a guide to ensure the department stays focused on why its work matters and remains committed to solving complex challenges. It underscores that Seattle IT exists to support City partners and is part of a larger organization working collectively to improve the lives of Seattle’s residents. More than 600 professionals across Seattle IT contribute to the full spectrum of modern IT services, creating a dynamic environment with diverse career opportunities. We hope you will consider joining us." We can condense but must preserve all substantive information; we cannot summarize away detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? It says do not summarize away detail. Probably we should keep the substance but can rephrase? Safer to keep the sentences as is, maybe break into paragraphs. We'll put that in

  under

  About the role

  . Responsibilities: There's a "Job Responsibilities" paragraph then "Here Is More About What You’ll Be Doing" with subheadings: System Operations & Technical Support, Strategic Product Leadership & Stakeholder Partnership, Vendor Management & Contract Performance, Technical Project Management, Governance & Best Practices. Each has bullet-like sentences (some with semicolons). We need to output as
  • for any list of duties/requirements/benefits. So we can treat each bullet as a list item. We'll need to extract each duty. Let's list them: From "Job Responsibilities" paragraph: - The role partners with Budget, Tax, Licensing, Treasury and other finance stakeholders, Seattle IT, product owners, and vendors to translate requirements into reliable revenue systems. - It informs long-term strategy by evaluating tools, SaaS platforms, integrations, and security practices for feasibility, risk, cost, and value. - The position coordinates Seattle IT resources to support the City’s tax, business licensing, and cash receipting systems. - Responsibilities include operational monitoring, troubleshooting, production support, vendor oversight, and delivery across design, configuration, testing, and deployment—providing day-to-day direction to staff and ensuring secure, reliable operations aligned with business owners. Then "Here Is More About What You’ll Be Doing" sections: System Operations & Technical Support: - Own day-to-day operations of the cash receipting system; direct technical contractors. - Coordinate server, database, network, and application support to meet performance targets. - Maintain and support integrations (e.g., FileLocal, payment portals). - Ensure reliable, secure operations and maintain technical runbooks. Strategic Product Leadership & Stakeholder Partnership: - Serve as the technology advisor to Tax, Treasury, and Licensing for revenue systems. - Maintain a product roadmap aligned to business priorities, security, and long-term goals. - Translate business needs into a prioritized backlog and define feature objectives. - Assess modernization opportunities and recommend future-state strategies. - Communicate impacts, timelines, and risks to stakeholders; act as the primary technology POC. Vendor Management & Contract Performance: - Manage SaaS vendors and contractors; oversee SOWs, SLAs, deliverables, and release schedules. - Ensure contractual performance and timely incident resolution. - Develop SOWs for maintenance and enhancements; coordinate partial-FTE resources. Technical Project Management: - Lead small–medium upgrades and enhancements. - Create and maintain PM artifacts (charters, test plans, risk/issue logs). - Coordinate UAT, release readiness, training, and deployments with vendors. - Proactively manage technical risks, dependencies, and monthly/quarterly release plans. Governance & Best Practices: - Run change control, risk management, and work prioritization for in-scope systems. - Enforce vendor documentation, technology best practices, and City methodologies. - Facilitate governance forums; track and report system health KPIs with vendors. We can combine all these into a single list under Responsibilities, or we could keep subheadings but we only allowed headings for sections; subheadings not allowed? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. Probably better to keep a single Responsibilities section with a list of all duties. We must not invent or summarize away detail; we need to keep each duty as is. Now Qualifications: Required Qualifications and Desired Qualifications. Required Qualifications: - Education: Bachelor’s degree in computer science, Information Systems, Information Technology, Business Administration, Public Administration, or a related field. (Equivalent combinations of education and additional professional experience in lieu of degree will be considered.) - Experience: 5+ years of progressively responsible experience in product management, business systems management, IT project leadership, or enterprise application support. - Demonstrated experience delivering technology solutions for complex, enterprise-level systems (preferably financial, permitting, tax, licensing, payments, or ERP platforms). - Strong vendor management experience, especially with SaaS or vendor-managed applications. - Experience leading implementations, large enhancements, or modernization initiatives for enterprise or municipal systems. - Expertise in system operations, including incident management, release management, and continuous improvement practices. - Experience with governance frameworks (e.g., ITIL, change control, risk/issue management). Desired Qualifications: - Product management or product ownership experience, including backlog grooming, user story writing, release planning, and stakeholder engagement. - Strong analytical and problem-solving abilities, with the ability to translate complex business needs into clear technical requirements. - Exceptional written and verbal communication skills, able to articulate technology concepts to non-technical audiences and build trust with business owners. - Experience leading cross-functional teams, including technical staff, vendors, and business stakeholders. - Familiarity with municipal revenue systems, such as tax platforms, cash receipting systems, licensing systems, or payment portals. - Strong customer service, with the ability to balance user needs, system constraints, and organizational priorities. - Ability to prioritize independently and manage multiple concurrent deadlines in a high-demand environment. - Experience leading others through system implementations or continuous improvement initiatives - Experience in government technology environments or public-sector digital platforms. - Experience with API-driven integration, data governance, or cloud-hosted revenue systems. - Experience in government technology or public-sector digital platforms. (duplicate? but we keep) We can combine Required and Desired into a Qualifications section, maybe split into Required and Desired sublists? But we only allowed headings for sections; we could still have subheadings inside? Not specified. Safer to have one Qualifications section with two lists: Required Qualifications and Desired Qualifications as

    • each, maybe preceded by a

      stating "Required Qualifications:" and "Desired Qualifications:" but that might be considered heading? Not exactly. We'll just include them as separate

      with preceding

      labels. Skills: Not explicitly listed; we could omit Skills section if no specific skills beyond qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills. Benefits: The City offers a comprehensive benefits package including vacation, holiday, and sick leave as well as medical, dental, vision, life and long-term disability insurance for employees and their dependents. More information about employee benefits is available on the City's website at: https://www.seattle.gov/human-resources/benefits. Additionally, we provide free public transportation options. We need to preserve all substantive information; we can include that as

      • items? Benefits are a list; we can make
        • for each benefit item. Pay: Salary: The full pay range for this position is $56.57 – 84.88 per hour. The salary for this individual role will be based on experience, training, and internal equity. We need Pay section with that info. Schedule: Telework Expectations: This position offers flexibility of a hybrid work schedule. At this time, hybrid telework schedules have a minimum requirement of three days onsite per week, which is subject to change at any time at the mayor’s discretion. Individual schedules are based on operational needs and agreement between the employee and their supervisor. We need Schedule section with that. We must not include application instructions, EEO boilerplate, etc. Now produce HTML. Structure:

          About the role

          ... (the description)

          Responsibilities

          • ... each duty
          ...

          Qualifications

          Required Qualifications:

          • ... each required

          Desired Qualifications:

          • ... each desired

          Benefits

          • ... each benefit

          Pay

          The full pay range for this position is $56.57 – 84.88 per hour. The salary for this individual role will be based on experience, training, and internal equity.

          Schedule

          This position offers flexibility of a hybrid work schedule. At this time, hybrid telework