Project Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Key parts: - About Us (company description) - could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About Us" but not "About The Role:" heading. There's "About The Role:" then description. So we can put that under

About the role

with paragraph(s) containing that description. - Responsibilities: there is "Key Responsibilities" list. So we need

Responsibilities

with

• items. - Requirements: there is "About You:" with bullet-like lines: Ability to manage multiple concurrent projects..., 3–5+ years..., Proven track record..., Experience working... That's requirements. Also "Nice To Have:" could be considered Qualifications or Skills? Usually Nice To Have are additional qualifications/skills. We could put them under Qualifications or Skills. The instruction: we have sections Requirements, Qualifications, Skills. We need to decide where to put content. The posting includes "About You:" (requirements) and "Nice To Have:" (nice-to-have). Could treat "About You:" as Requirements, and "Nice To Have:" as Qualifications or Skills. Since they are about experience with AP automation, ERP systems, familiarity with financial processes, experience in partner/SI-led delivery models. Those are more like qualifications/skills. We could put them under Qualifications. - Benefits: posting mentions "Medius Is Committed To Fair And Equitable Compensation Practices. The estimated base salary range for this role is $125,000 to $135,000 USD..." That's Pay. Also mentions "total compensation package ... may also include eligibility for variable compensation (such as a performance bonus or commission), benefits, and/or participation in other incentive or benefit plans... Benefits may include medical, dental, and vision coverage, paid time off, and retirement benefits, subject to eligibility requirements." So we have Pay and Benefits sections. - Schedule: not mentioned. So we should not include Schedule section. - Skills: maybe we could extract skills from responsibilities? But we already have Qualifications. Could also put technical skills under Skills. However we have no explicit skills list besides those nice-to-have. Could treat those as Skills. But we already used Qualifications for nice-to-have. Might be okay to have both Qualifications and Skills sections if content exists. But we need to avoid thin sections. Let's see: we have Requirements (About You). Nice To Have could be Qualifications. Benefits and Pay we have. Skills maybe we could extract from responsibilities like "Ability to manage multiple concurrent projects", "Define and manage project scope..." but those are more responsibilities. Could still list under Skills but might be thin. Better to not include Skills if no explicit list. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if not clearly present. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other sections like "About Us" could be part of About the role? The About the role section should contain the description under "About The Role:" which includes role description. The earlier "About Us" is company overview; could be included under About the role? Might be considered part of About the role? But the instruction says use heading About the role for section headings (e.g. About the role...). It doesn't forbid adding extra content like company overview under that heading. However we should preserve all substantive information. The About Us description is substantive; we could include it under About the role as well, or maybe we could create a separate section like "About the company" but not allowed headings list. So we can incorporate it into About the role paragraph. Thus About the role will contain both the company overview (About Us) and the role description (About The Role:). Ensure we don't repeat job title heading. Now we need to strip boilerplate: navigation, duplicated lines, EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal, duplicated lines, etc. Also remove "Medius Is Committed To Fair And Equitable Compensation Practices."? That's part of compensation description, we keep it as part of Pay section maybe. The EEO paragraph: "Medius is an equal opportunity employer..." should be removed. Also the accommodation request line. Also the "Department CXO Role Project Manager Locations USA - REMOTE Remote status Fully Remote Employment type Full-time Contact Sara Snoussi Talent Acquisition Business Partner – Human Resources Current job openings Functional Consultant/ Project Manager CXO Manchester, London Hybrid Functional Consultant/Project Manager CXO Multiple locations Hybrid Elevate Functional Advisor CXO Tunis Hybrid More jobs USA - REMOTE Get to know more about us ..." That's a bunch of noise; we need to remove. Also remove repeated sections like the duplicated "About Us" later in the text (the second occurrence). We'll keep only one copy. Now let's extract substantive content: Company overview (About Us) from first occurrence: "At Medius, we believe managing finance should be about strategy, not stress. That same mindset shapes not only the solutions we build, but also the culture we create for our people. We remove complexity, embrace innovation, and give our teams the freedom to focus on what truly matters — whether that’s transforming the future of finance with AI or finding balance to go home on time. Founded in Sweden in 2001, Medius has grown from a local startup into a global leader in cloud-based spend management solutions. Today, thousands of organizations worldwide trust us to simplify accounts payable and spend management processes. Our journey has been driven by continuous innovation, a passion for technology, and above all — the people who make it happen. We’re more than a software company. We’re a team of problem-solvers, innovators and collaborators working together to reinvent the category of accounts payable. Our solutions use Artificial Intelligence to eliminate manual work, bring clarity, confidence, and control, and empower finance teams of the future. At Medius, our values guide how we work and grow together: Connect – We believe in the power of people—individually and collectively—and our success depends on understanding and respecting each other. We appreciate that ‘empowering finance teams of the future’ is an exciting endeavor, and we share it with everyone around us.Question – We enjoy the challenge of our work and the thrill of collaboration. We are not afraid to question ourselves and each other because we believe diverse perspectives can lead to better outcomes and that there is great power in resolution.Own – We are thorough, thoughtful, and decisive. We anticipate what’s next, what a customer might need, and then we deliver. That’s how we get things done. And that’s how we remain a leader. Customers trust us to do our job so that they can focus on what they do best. At Medius, you’ll join a diverse, global community where curiosity is celebrated, ideas matter, and innovation never stops. If you’re passionate about technology, eager to make an impact, and ready to grow alongside a team that lives its values, Medius is where you can do your best work — your impact is global. Learn more at www.medius.com" Note there is a weird "Question –" with no space after dash? Actually it's "Question –". We'll keep as is. Now About The Role description: "As a Project Manager at Medius, you will own the end-to-end delivery of customer implementation projects, ensuring successful onboarding of Medius solutions across AP automation and spend management. You will act as the primary point of contact between customers, internal delivery teams, and partners throughout the project lifecycle." That's the paragraph. Now Responsibilities list (under Key Responsibilities): - Lead full lifecycle delivery of Medius implementations — from kickoff through go-live and hypercare - Define and manage project scope, timelines, budgets, and resource plans - Coordinate cross-functional teams including consultants, developers, integration specialists, and customer stakeholders - Proactively identify, track, and mitigate project risks and issues - Manage customer expectations and maintain strong relationships at all levels including C-suite - Drive adherence to Medius implementation methodology and best practices - Facilitate steering committee meetings, status reporting, and executive updates - Ensure quality delivery and smooth handover to Customer Success post go-live - Contribute to continuous improvement of delivery processes and tooling - Budget Management (maybe a separate bullet? It appears as a line after the list: "Budget Management". We'll treat as bullet.) Now About You (requirements): - Ability to manage multiple concurrent projects in a fast-paced environment - 3–5+ years of project management experience in B2B SaaS or ERP/fintech implementations - Proven track record delivering complex software projects on time and within budget - Experience working with enterprise customers across multiple geographies Nice To Have: - Experience with AP automation, P2P, or ERP systems (D365, SAP, Oracle, Unit4) - Familiarity with financial processes and the office of the CFO - Experience in partner/SI-led delivery models Now Pay/Benefits: Compensation: "Medius Is Committed To Fair And Equitable Compensation Practices. The estimated base salary range for this role is $125,000 to $135,000 USD, which represents a good-faith estimate of the compensation for this position. Actual compensation will be determined based on several factors, including but not limited to relevant skills, experience, qualifications, certifications, internal equity, and the geographic location in which the role is performed. Compensation may vary for roles performed in different locations due to differences in the cost of labor. The total compensation package for this position may also include eligibility for variable compensation (such as a performance bonus or commission), benefits, and/or participation in other incentive or benefit plans, in accordance with the terms of the applicable plans." Benefits: "Benefits may include medical, dental, and vision coverage, paid time off, and retirement benefits, subject to eligibility requirements." We should combine these into Pay and Benefits sections. Now we need to output HTML fragment with headings

  and content. We must not include any markdown code fences. We'll produce something like:

  About the role

  At Medius, we believe managing finance should be about strategy, not stress. ... Learn more at www.medius.com

  As a Project Manager at Medius, you will own the end-to-end delivery of customer implementation projects, ensuring successful onboarding of Medius solutions across AP automation and spend management. You will act as the primary point of contact between customers, internal delivery teams, and partners throughout the project lifecycle.

  Responsibilities

  • Lead full lifecycle delivery of Medius implementations — from kickoff through go-live and hypercare
  ...

  Requirements

  • Ability to manage multiple concurrent projects in a fast-paced environment
  ...

  Qualifications

  • Experience with AP automation, P2P, or ERP systems (D365, SAP, Oracle, Unit4)
  ...

  Benefits

  • Medical, dental, and vision coverage
  • Paid time off
  • Retirement benefits

  Pay

  The estimated base salary range for this role is $125,000 to $