Principal Project Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Sparq, mission, etc. Could be "About the role"? Actually "About the role" maybe includes description of role and company. We'll treat that as About the role. - "C2C is not available Must be authorized to work in the U.S. without sponsorship" -> This is eligibility requirement. Could go under Requirements or Qualifications. Probably Requirements. - "Why You Will Enjoy Mondays Again" bullet list: Opportunity to work alongside a talented, diverse team in a collaborative and creative environment; Ongoing investment in your growth through training, mentorship, and industry certifications; Hands-on exposure to cutting-edge technologies across multiple industries; Recognition programs and employee awards within an inclusive culture that celebrates great work, including our AI Innovators Program; Remote or hybrid work options; Competitive salary; Robust benefits package, matching 401(k) plan, and substantial PTO; Tuition reimbursement These are benefits and perks. Could go under Benefits (maybe also Pay). "Competitive salary" is Pay. "Robust benefits package, matching 401(k) plan, and substantial PTO" is Benefits. "Tuition reimbursement" also Benefits. Also "Remote or hybrid work options" hybrid work options could be Schedule? Actually schedule: remote/hybrid work options. Could be Schedule. - "A Day In The Life" list of duties: Lead a highly complex, portfolio-aligned IT program from initial discovery and scope definition through execution, transition, and closeout.; Develop and manage an integrated program plan across multiple concurrent application development projects, ensuring timelines, milestones, and deliverables remain aligned.; Partner with the Program Sponsor, Portfolio Manager, and other senior stakeholders to establish reporting cadences and provide clear, executive-level updates on program health, progress, financials, risks, and decisions.; Collaborate across a large, distributed organization to define program scope, navigate ambiguity, build stakeholder alignment, and identify dependencies across projects and business areas.; Own program financial management, including cost estimates, budget development, forecasting, and forecast-to-actual tracking.; Work onsite in the St. Louis, Missouri area as business needs require, up to once per week or three times per month.; Monitor program risks, issues, dependencies, and health indicators, escalating significant concerns and leading resolution of the most complex challenges.; Direct third-party and vendor activities by integrating external deliverables into the overall program plan and tracking performance against contractual commitments.; Oversee resource needs across the program, review requests from project managers, and escalate capacity or skill constraints that may affect delivery.; Apply Waterfall, Agile, or blended delivery approaches based on the needs of the program, projects, and stakeholders.; Lead interim and post-program reviews to evaluate outcomes, capture lessons learned, and identify opportunities to strengthen future execution.; Actively use AI tools, including Claude through our Anthropic partnership, to streamline tasks, improve the quality of your work, and share best practices with teammates while continuously seeking new ways to integrate AI into your everyday workflows; Mentor project managers and reinforce consistent project management standards, governance practices, and reporting expectations across the PMO.; Support organizational change activities by anticipating stakeholder impacts, strengthening adoption, and maintaining effective relationships throughout the program lifecycle. These are responsibilities. - "What It Takes" list: Consultative approach and problem solving skills to successfully align digital solutions with long-term business goals of the client; Hands-on experience using AI tools to enhance daily work, or a strong desire to do so, including a willingness to experiment, learn, and champion AI adoption within your role; Claude Certified Developer or Architect highly preferred; possible opportunity to obtain as a Sparq colleague; Commitment to understanding and exceeding client expectations; Ability to perform project oversight and execution of deliverables; Flexibility to adapt within a high-growth organization; Ability to lead, mentor and motivate those around them; Hunger for continuous learning and professional development; Intellectual curiosity to provide creative solutions; Full understanding of the software development life cycle; Ability to positively impact fellow colleagues through effective leadership, presentations, coaching, etc.; Desire to work in a team environment; Good interpersonal, written and verbal communication skills; Regardless of your specific role, we seek individuals who are excited to explore, adopt, and evangelize AI tools and methodologies. If you have experience in AI or a proven track record of rapidly learning and mentoring others on emerging tech, you’ll fit right in. These are qualifications/skills. Could split into Requirements (must-haves) and Qualifications (preferred) and Skills. But we need to decide sections. We have to include sections only if posting has real specific content. We can include About the role (intro), Responsibilities (A Day In The Life), Requirements (eligibility + maybe some must-haves), Qualifications (preferred like Claude Certified), Skills (maybe list of skills), Benefits (benefits list), Pay (competitive salary), Schedule (remote/hybrid and onsite requirement). Must avoid filler like "commensurate with experience". We have actual specifics: Competitive salary (but no amount). That's still specific enough? It says "Competitive salary". That's a statement but not a number. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive salary" is stated, though vague. It's not placeholder like "commensurate with experience"? It's similar but maybe acceptable. The instruction says avoid filler/placeholder text like "commensurate with experience". "Competitive salary" could be considered placeholder but it's explicitly stated. I'd include Pay section with that line. Benefits: "Robust benefits package, matching 401(k) plan, and substantial PTO", "Tuition reimbursement", "Recognition programs and employee awards...", "Ongoing investment in your growth through training, mentorship, and industry certifications", "Hands-on exposure to cutting-edge technologies across multiple industries", "Remote or hybrid work options" (maybe schedule). We'll include Benefits section with those items. Schedule: "Remote or hybrid work options", "Work onsite in the St. Louis, Missouri area as business needs require, up to once per week or three times per month." That's schedule info. Now we need to avoid duplication. Also remove EEO boilerplate etc. We need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

Intro paragraph(s) about Sparq and role.

Responsibilities

• ... each duty

Requirements

• Must be authorized to work in the U.S. without sponsorship
• C2C is not available
maybe also include "Consultative approach and problem solving skills..."? That's more skill. But we can put must-haves: maybe "Consultative approach and problem solving skills to successfully align digital solutions with long-term business goals of the client" is a requirement. But we have many skill items. Could split: Requirements = eligibility + core abilities; Qualifications = preferred certifications; Skills = list of skills. But we need to avoid too many thin sections. Perhaps combine Requirements and Qualifications into one? But the instruction says we can use those headings if content exists. We'll decide to have: - About the role - Responsibilities - Requirements (includes eligibility and core competencies) - Qualifications (preferred certifications like Claude Certified) - Skills (maybe list of interpersonal/communication etc) - Benefits - Pay - Schedule But we risk many sections. However we have substantive content for each. Let's extract: About the role: The first paragraph(s) up to "C2C is not available Must be authorized to work in the U.S. without sponsorship". Actually that line is separate. So About the role could be: "At Sparq, we help companies solve the right problems—not just build more technology. We’re a modern product engineering partner blending strategy, craftsmanship, and speed to help organizations modernize confidently in the age of AI. From data ecosystems to digital products and AI acceleration, we turn complexity into clarity and ideas into impact. If you’re driven to build what’s next, lead with empathy, and deliver excellence without ego, you’ll feel right at home at Sparq." That's good. Requirements: "C2C is not available Must be authorized to work in the U.S. without sponsorship". Also maybe "Consultative approach and problem solving skills to successfully align digital solutions with long-term business goals of the client" is a requirement but could be skill. We'll keep it simple: eligibility. Qualifications: "Claude Certified Developer or Architect highly preferred; possible opportunity to obtain as a Sparq colleague". Also maybe "Hands-on experience using AI tools to enhance daily work, or a strong desire to do so, including a willingness to experiment, learn, and champion AI adoption within your role". That could be qualification. Skills: list of many items: Commitment to understanding and exceeding client expectations; Ability to perform project oversight and execution of deliverables; Flexibility to adapt within a high-growth organization; Ability to lead, mentor and motivate those around them; Hunger for continuous learning and professional development; Intellectual curiosity to provide creative solutions; Full understanding of the software development life cycle; Ability to positively impact fellow colleagues through effective leadership, presentations, coaching, etc.; Desire to work in a team environment; Good interpersonal, written and verbal communication skills; Also "Regardless of your specific role, we seek individuals who are excited to explore, adopt, and evangelize AI tools and methodologies. If you have experience in AI or a proven track record of rapidly learning and mentoring others on emerging tech, you’ll fit right in." That's also skill/qualification. But we might combine Qualifications and Skills into one section "Qualifications and Skills". However instruction says we can use those headings if content exists. To reduce number of sections, we could have: - About the role - Responsibilities - Requirements (eligibility) - Qualifications (includes certifications, AI experience, etc.) - Skills (maybe interpersonal etc) - Benefits - Pay - Schedule That's 8 sections. Might be okay. But we need to ensure we don't create sections with filler. Each has real content. Let's draft. Responsibilities list items from "A Day In The Life". We'll copy each sentence as
• . Benefits list: from "Why You Will Enjoy Mondays Again": - Opportunity to work alongside a talented, diverse team in a collaborative and creative environment - Ongoing investment in your growth through training, mentorship, and industry certifications - Hands-on exposure to cutting-edge technologies across multiple industries - Recognition programs and employee awards within an inclusive culture that celebrates great work, including our AI Innovators Program - Remote or hybrid work options (maybe schedule) - Competitive salary (Pay) - Robust benefits package, matching 401(k) plan, and substantial PTO - Tuition reimbursement We'll separate Pay and Schedule. Pay: Competitive salary Schedule: Remote or hybrid work options; Work onsite in the St. Louis, Missouri area as business needs require, up to once per week or three times per month. Benefits: the rest (excluding Pay and Schedule). Also maybe include "Recognition programs..." etc. Now Requirements: "C2C is not available Must be authorized to work in the U.S. without sponsorship". Could be two items. Qualifications: - Claude Certified Developer or Architect highly preferred; possible opportunity to obtain as a Sparq colleague - Hands-on experience using AI tools to enhance daily work, or a strong desire to do so, including a willingness to experiment, learn,