Manager, Product Management

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. First paragraph: company description, mission, Blackstone, values etc. That's likely not a specific section heading; could be part of "About the role"? Actually "About The Role" heading appears later. The initial description about Sphera is company overview, not part of role. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Could be placed in a

before sections, as general description. Since we cannot create a heading for it unless matches allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the company overview in a

before any heading, as it's substantive. That's fine. Then we have "About The Role" heading. So we create

About the role

and then content under it. Then we have sections: Market Focus Responsibilities, Platform Product Focus Responsibilities, People Focus Responsibilities. Those are subheadings within responsibilities. We could combine them under a single Responsibilities section with

• items. But we need to preserve details. Could create subheadings? Not allowed unless they match allowed headings. So we likely put all responsibilities under a single Responsibilities section, using
  • for each bullet. However the posting has paragraphs describing responsibilities, not bullet list. We need to convert to list items. The instruction: Use
    • for any list of duties/requirements/benefits. So we need to identify lists. The responsibilities are described in paragraphs; we could treat each sentence as a list item? Might be overkill. Better to keep as

      for prose, but if there is a list we need to use

      • . The posting includes bullet-like sentences but not explicit bullet characters. However we can still treat each responsibility as a list item. The instruction says "Use
        • for any list of duties/requirements/benefits". If the content is not explicitly a list, we could keep as

          . Safer to keep as

          for prose sections. Thus: - After About the role heading, we put the paragraphs describing the role (the long paragraph). Could split into multiple

          for readability. Then we have "Market Focus Responsibilities" heading (but not allowed). We could treat that as part of Responsibilities section: maybe a

          not allowed. So we just include its content under Responsibilities

          or

          . Since it's a heading, we could ignore heading and just include its paragraphs. Similarly "Platform Product Focus Responsibilities" and "People Focus Responsibilities". Thus we will have a single Responsibilities section with multiple paragraphs. Then "Required Education" heading (not allowed). Could be part of Requirements or Qualifications. We have Required Education, then Requirements list. We could put education under Requirements or Qualifications. Since we have both Requirements and Qualifications allowed headings. We need to decide where to put education. Likely under Requirements (or Qualifications). The posting: "Required Education BS Degree in Engineering, Environmental Science, Computer Science, and/or Business/Marketing Requirements 5+ years of experience..." So it's mixed. We'll treat education as part of Requirements. Then we have a block: "Requirements 5+ years of experience with software platform design concepts and components 5+ years of Product Management experience is desirable.3+ years of people management experience Experience managing enterprise software applications and/or large-scale product initiatives, in particular SaaS applications. Strong understanding of Agile Product Management and Software Development methodologies Proven ability to communicate with customers, stakeholders, salespeople, and executives. Knowledgeable in modern technology and architectural patterns Knowledgeable in product development in Cloud environment Knowledgeable in products based on services and APIs’ Strong conceptual and analytical skills to form the basis of well-researched and documented plans Proven record as a self-motivated, performance-driven professional Demonstrates sound business judgement, common sense and insight Behaves consistently with Sphera values and ethical principles" That's a dense paragraph; we could split into sentences and make
          • for each requirement. That seems appropriate as it's a list of requirements. Then "Pay $127,000.00 - $203,000.00 + Eligible for Variable Compensation Plan" => we need Pay section. Then "Benefits Commensurate with relevant qualifications and experience Medical, Dental, and Vision InsuranceHealth Savings AccountFlexible Spending Account401(k) Retirement Plan with Company MatchLife and Disability InsuranceCritical Illness InsuranceAccident InsuranceHospital Indemnity InsurancePaid Time Off and HolidaysFlexible Working Schedule" We need Benefits section only if posting actually states them. It does list benefits. So we create Benefits section with
            • for each benefit. Note there is also "Commensurate with relevant qualifications and experience" which is vague; we should not include filler like that. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should exclude that phrase from Benefits section. So we list the actual benefits. Then "Schedule" maybe from "Flexible Working Schedule" appears under Benefits. There's no separate Schedule heading. So we may not create Schedule section because no explicit schedule info besides flexible working schedule which is a benefit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since schedule not explicitly stated as a separate section, we should not create Schedule heading. However we could include flexible working schedule as a benefit item. Thus sections: About the role, Responsibilities, Requirements, Qualifications?, Skills?, Benefits, Pay. We have no explicit Qualifications or Skills separate; we could combine skills into Requirements. But we have allowed headings; we can omit those sections if no specific content. So we will not include Qualifications or Skills headings. We need to ensure we don't create empty headings. Thus final HTML:

              Sphera is a leading global provider of enterprise software and services that enables companies to manage and optimize their environmental, health, safety and sustainability. Our mission is to create a safer, more sustainable and productive world. Sphera is a portfolio company of Blackstone, a U.S.-based alternative asset investment company that focuses on private equity, technology and innovation, and more. Blackstone businesses succeed through strong partnerships, a personalized approach and a commitment to exceptional performance with uncompromising integrity. Sphera and Blackstone are leaders in the Environmental, Social and Governance (ESG) space. We are guided by our core values of Customer Centricity, Accountability, Bias to Action, Innovation, and Collaboration. These values help us recruit the right talent to join our rapidly expanding team around the globe. It is important to us that each and every Spherion is not only eager to challenge themselves and knows how to get work done but is an awesome addition to our company culture.

              About the role

              As the Product Manager, Platform, you will lead the strategy and direction of the SpheraCloud platform product. You will guide product priorities and enhancements from the idea stage to full production and help to develop new ideas based on your industry experience and feedback from our partners and customers. You will collaborate with other solution areas to develop and deliver key functionality to our existing SpheraCloud product, further enabling a modular set of cloud-based solutions. The selected individual will partner closely with the customers (internal and external), the business lines and Agile teams to drive the evolution of the assigned products. The Product Manager is responsible for defining a product vision with a prioritized product backlog to deliver on business vision and priorities. The PM provides constant feedback to the business lines and Agile teams in support of delivery and evolution of the product. The PM must develop a well-rounded understanding of the customer’s needs that are aligned with business objectives as well as an ability to develop close relationships with key stakeholders. You will shape the software development roadmap for the product and communicate it to internal and external stakeholders. You are also the key member of the team responsible for both defining and prioritizing the release backlog in close collaboration with engineering counterparts and product owners/managers. You will work closely with the development and engineering team to define architecture, user experience, and product capabilities. You are responsible for the overall quality delivery of the solution to our customers. Using your skills, talents, efforts, and influence, you will deliver positive business outcomes for both our customers and Sphera.

              Responsibilities

              Market Focus Responsibilities: Assist in the research of market requirements and forecasts for new portfolio opportunities and platform advancement strategies; Document and maintain key competitor profiles; Work with branding and marketing teams to help them understand market positioning; Work with sales and marketing teams to document the buying process and identify sales enablement tools, including partner channels; Assists in the creation of the training and tools necessary to ensure the Sales, Services, and Customer Care are educated on the feature/functionality of products; Provide product and domain content focused on the market.

              Platform Product Focus Responsibilities: Maintain product success metrics for the Platform; Develop and maintain a roadmap for the Platform including: Developing a list of initiatives and epics; Balancing priorities between maintenance requirements, architecture, and new features, and maximizing the value of each release; Recommending market-specific enhancements for all portfolio products; Defining the planned date and content for a product release to customers; Actively work directly with the development team; Serve as the customer representative in all team meetings; Partner with product portfolio and develop personas and related product capabilities; Participate in release and product retrospectives with engineering, UX teams; Drive discussions to surface issues, identify fixes and advance projects; Participate in product planning and forecasts with the product management team; Maintain and report product status such as burn up/burn down and velocity charts; Participate in sprint retrospectives with the Agile team; Maintain a release backlog and focus on product deliverables.

              People Focus Responsibilities: Influence and partner with stakeholders to create a shared platform vision and optimal product outcomes; Lead cross-functional teams for key company initiatives; Contribute to Go-To-Market teams.

              Requirements

              • BS Degree in Engineering, Environmental Science, Computer Science, and/or Business/Marketing
              • 5+ years of experience with software platform design concepts and components
              • 5+ years of Product Management experience is desirable
              • 3+ years of people management experience
              • Experience managing enterprise software applications and/or large-scale product initiatives, in particular SaaS applications
              • Strong understanding of Agile Product Management and Software Development methodologies
              • Proven ability to communicate with customers, stakeholders, salespeople, and executives
              • Knowledgeable in modern technology and architectural patterns
              • Knowledgeable in product development in Cloud environment
              • Knowledgeable in products based on services and APIs
              • Strong conceptual and analytical skills to form the basis of well-researched and documented plans
              • Proven record as a self-motivated, performance-driven professional
              • Demonstrates sound business judgement, common sense and insight
              • Behaves consistently with Sphera values and ethical principles

              Benefits

              • Medical, Dental, and Vision Insurance
              • Health Savings Account
              • Flexible Spending Account
              • 401(k) Retirement Plan with Company Match
              • Life and Disability Insurance
              • Critical Illness Insurance
              • Acc