Technical Project Manager (Gov't Tech)

We need to output HTML fragment with sections: About the role? Actually description includes "What to expect when you join Sikich" etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract content. Let's parse posting: - Title: Technical Project Manager (US- Remote) - Description: "What to expect when you join Sikich Team members at Sikich have a lot in common while also being part of a rich and varied group of contributors, creating a distinct and thriving culture. ..." This is about company culture, could be "About the role"? Actually "About the role" maybe not; but we have "What to expect when you join Sikich" which is about culture, maybe "About the role"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have sections: - Position summary (description of role) -> could be "About the role" or "Responsibilities"? Actually "Position summary" describes role. Could be "About the role". - "What will you do in this role?" with sub-bullets: Technical Project Planning & Delivery, FHIR, Interoperability & Technical Coordination, Agile & Portfolio Alignment, Risk, Dependency & Decision Management, Governance, Reporting & Stakeholder Engagement. Those are responsibilities. - "What do you need to succeed in this role?" includes requirements: Bachelor's degree, 8+ years experience, etc. Also "In compliance with this state’s pay transparency laws, the base compensation range (25%-50%-75%) for this role is $130,000- $137,500- $145,000." That's Pay. - Also "About Sikich" description of company. - "Sikich Total Rewards" benefits list. - No explicit Schedule info. Thus we can create sections:

About the role

with position summary paragraph.

Responsibilities

with

• items for each responsibility area (maybe combine subpoints). Must preserve all substantive info; we can break into multiple
• each covering a bullet.

  Requirements

  with education and experience etc.

  Qualifications

  maybe for preferred certifications etc. Could separate.

  Skills

  Benefits from Sikich Total Rewards.

  Pay

  with compensation range. No Schedule. We must not repeat job title as heading. No metadata like Job ID. We must remove boilerplate: EEO, legal, etc. At end there is "Sikich is an Equal Oppor" truncated; remove. We must preserve all substantive info; not invent. Let's extract content precisely. First, "What to expect when you join Sikich Team members at Sikich have a lot in common while also being part of a rich and varied group of contributors, creating a distinct and thriving culture. Chief among our commonalities is a desire for growth and a shared unity of purpose in our professional lives. We believe that through diverse perspectives, challenging the status quo and rewarding action, we accelerate innovation and drive growth – for our clients, for ourselves and for our communities. The professional services landscape continues to evolve. For Sikich, this means we have an opportunity to further cement our leadership position in this industry and continue to grow our organization in increasingly exciting ways. This growth is meaningful for every team member at our company because larger companies simply see more interesting client opportunities and can attract impressively talented individuals like you. Through a dedicated focus on key business priorities and intentionally creating rewarding employee experience, Sikich has developed into a highly regarded provider of professional services and a sought-after employer of choice. Do you want to work with other skilled and agile practitioners who thrive on challenge and growth? We believe everyone has untapped potential. That’s why we lead with vision and act fast, pairing deep expertise with practical solutions. Our teams cut through complexity and deliver real impact. It's our hope that you find more than just a job. At Sikich, you'll find optimism, clear insights and genuine warmth, without egos. Are you ready to grow with us?" This is about company culture; could be placed under "About the role" or maybe separate "About Sikich". But we have also later "About Sikich" paragraph. To avoid duplication, we could combine culture description into "About the role" as introductory. But we also have separate "About Sikich" later: "About Sikich Sikich offers the public and private sectors a diverse platform of professional services across consulting, technology, and compliance. Highly specialized and hands-on teams deliver integrated solutions rooted in deep industry experience. Our approach is strategically and thoughtfully designed to help our clients, teams and communities accelerate success. Sikich has approximately 2,000 team members and operates across North America, EMEA and APAC." We could put that under "About Sikich" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit content into those. "About Sikich" could go under "About the role" as well, but maybe better to put under "About the role" the role summary, and maybe we can add a separate "About Sikich" not allowed; we must not create extra headings. So we must incorporate that info into one of the allowed sections. Perhaps we can put company overview under "About the role" as a brief intro. Thus "About the role" will contain both the "What to expect when you join Sikich" culture paragraph and the position summary and maybe the About Sikich description. But we must not lose any substantive info. Let's capture all paragraphs. Paragraphs: 1. "What to expect when you join Sikich ..." (culture) 2. "Position summary The Technical Project Manager supports CMS's Digital Quality Initiative (DQI) on the Security, Innovation, and Operations (SIO) program, leading the planning, coordination, and delivery management needed to advance the initiative's technical work across the Center for Clinical Standards and Quality (CCSQ). This role works across CMS teams and stakeholders, including close partnership with Information Systems Group (ISG) leadership, to translate strategic direction into actionable technical plans and coordinate execution across interconnected efforts. A defining part of this role is understanding the technical ecosystem supporting digital quality, including FHIR-based interoperability, data exchange, systems integration, and the dependencies involved in moving from strategy through implementation. The Technical Project Manager does not need to serve as the solution architect or primary developer but must have sufficient technical depth to work credibly with engineers, architects, product teams, and CMS stakeholders; identify and manage technical dependencies and risks; and drive complex technical work toward defined outcomes." 3. "What will you do in this role?" then subheadings with paragraphs. We need to convert subheadings into list items under Responsibilities. Let's extract each responsibility bullet: - Technical Project Planning & Delivery: paragraph: "Translate DQI strategy and priorities into actionable technical roadmaps, implementation plans, milestones, and work products. Coordinate technical activities across CCSQ teams and workstreams, including close partnership with ISG and other stakeholders responsible for DQI implementation. Maintain visibility into scope, schedules, dependencies, risks, decisions, and delivery progress across interconnected technical efforts. Drive work from planning through execution, identifying barriers and coordinating actions needed to maintain progress. Build on existing CMS capabilities, standards, and prior work to support implementation while avoiding unnecessary duplication. Maintain integrated plans that connect technical activities and dependencies to broader DQI objectives and outcomes." - FHIR, Interoperability & Technical Coordination: "Support planning and coordination of FHIR-based interoperability and data exchange activities associated with DQI. Work with architects, engineers, developers, data teams, and other technical subject matter experts to understand implementation requirements, dependencies, constraints, and sequencing. Facilitate technical discussions and translate decisions into clear actions, owners, and next steps. Coordinate across systems and teams where integration or shared technical dependencies affect delivery. Develop and maintain a working understanding of relevant CMS technical standards, platforms, architecture, and interoperability approaches to effectively support project execution." - Agile & Portfolio Alignment: "Align DQI technical delivery with CMS's Agile and Lean Portfolio practices. Write, coordinate, and help manage Agile work products, including epics, features, backlog items, roadmaps, and other planning artifacts needed to advance the initiative. Support prioritization and sequencing of technical work based on dependencies, readiness, risks, and program priorities. Facilitate planning sessions, technical working sessions, and other forums needed to coordinate work and move implementation forward. Ensure technical work and progress are visible through established CMS program and portfolio management processes." - Risk, Dependency & Decision Management: "Proactively identify and manage technical risks, issues, dependencies, assumptions, and decisions across DQI workstreams. Analyze cross-team and cross-system dependencies and work with appropriate stakeholders to develop mitigation and resolution strategies. Establish clear escalation paths and bring issues requiring CMS direction forward with sufficient context to support timely decisions. Track key technical decisions and ensure resulting actions are incorporated into project plans and execution. Anticipate potential delivery challenges and work across teams to address them before they affect critical milestones." - Governance, Reporting & Stakeholder Engagement: "Provide CMS leadership and stakeholders with clear, concise visibility into technical delivery status, upcoming milestones, risks, dependencies, decisions, and areas requiring attention. Develop and maintain roadmaps, dashboards, status reporting, and other artifacts that provide an integrated view of DQI technical execution. Coordinate reporting through standard program workflows and tools rather than creating unnecessary one-off reporting processes. Build effective working relationships across CMS leadership, ISG and other CCSQ teams, technical teams, contractors, and stakeholders involved in DQI. Communicate complex technical topics clearly to both technical and non-technical audiences and help connect technical decisions to broader program objectives." Now "What do you need to succeed in this role?" includes: - Bachelor's degree in Information Technology, Computer Science, Engineering, Health Informatics, or a related field required. - 8+ years of progressive experience managing complex technology projects or programs, preferably within healthcare, federal government, or another large, highly regulated environment. - Demonstrated experience leading technical projects involving multiple systems, teams, stakeholders, and interdependent workstreams. - Working knowledge of healthcare interoperability and FHIR standards - Experience working with technical teams, including architects, engineers, developers, data specialists, cybersecurity professionals, and product or platform teams. - Demonstrated ability to translate strategic objectives and technical direction into actionable plans, milestones, dependencies, and work products. - Experience identifying and managing technical risks, dependencies, issues, and decisions across complex initiatives. - Experience developing executive-level reporting, technical roadmaps, dashboards, and decision-support materials. - Excellent written and verbal communication skills, including the ability to facilitate technical discussions and communicate complex information to executive and non-technical stakeholders. - Experience in regulated or compliance-driven environments, particularly healthcare or the public sector; CMS/CCSQ experience preferred, though comparable federal health system experience will be strongly considered. - Knowledge in the following areas preferred: FHIR certification preferred. Candidates without an existing FHIR certification must be willing to obtain an approved FHIR certification following hire. - Experience applying Agile and Lean Portfolio practices; SAFe certification strongly preferred. - Strong project management skills; PMP or comparable project/program management certification preferred. Then compensation: "In compliance with this state’s pay transparency laws, the base compensation range (25%-50%-75%) for this role is $130,000- $137,500- $145,000. This is not a guarantee of compensation or salary, as final offer amount may vary based on several factors including but not limited to experience and geographic location. Compensation ranges for roles in our