Product Manager, Real Assets (Real Estate + Infrastructure), AVP

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. "Who We Are Looking For" - this is about the role overview 2. "What You Will Be Responsible For" - responsibilities 3. "What We Value" - qualifications/skills 4. "Education & Preferred Qualifications" - requirements 5. "Additional Requirements" - additional requirements 6. "About State Street" - company info, benefits, salary range The rules say: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID as heading - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Let me map the content: 1. "Who We Are Looking For" -> This is "About the role" section. It has prose describing the role. 2. "What You Will Be Responsible For" -> "Responsibilities" section. It's a list of duties. 3. "What We Value" -> This seems like "Qualifications" or "Skills". It's a list of valued traits. 4. "Education & Preferred Qualifications" -> "Requirements" section. List of qualifications. 5. "Additional Requirements" -> Could be part of Requirements or separate. It's a list (travel). 6. "About State Street" -> Contains company description, benefits, salary range. Benefits and Pay are mentioned specifically. Salary Range is given: $80,000 - $140,000 Annual. Benefits are listed in detail. So we should include Pay and Benefits sections. Schedule? Not explicitly mentioned except travel requirement (20%). Might not need a Schedule section. Now, I need to avoid duplication. The "About State Street" appears twice in the text (two paragraphs). I'll combine. Also, there's boilerplate: EEO statements, Job ID, application disclosure, etc. Remove those. Let me structure:

  About the role

  ...prose from "Who We Are Looking For"...

  Responsibilities

  • ...each bullet from "What You Will Be Responsible For"...

  Qualifications

  • ...from "What We Value" and "Education & Preferred Qualifications" and "Additional Requirements"? But the rules say separate sections for Requirements, Qualifications, Skills. However, the posting has "What We Value" (soft skills) and "Education & Preferred Qualifications" (hard requirements). I'll combine into "Qualifications" or split? The rules mention "Requirements, Qualifications, Skills" as possible headings. I think "Qualifications" can cover both. But "Education & Preferred Qualifications" is more like requirements. I'll create a "Requirements" section for the list under "Education & Preferred Qualifications" and "Additional Requirements", and a "Qualifications" section for "What We Value". However, the rules say "Prefer a few substantive sections over many thin ones." So maybe combine into one "Qualifications" section with sub-lists? But the HTML structure is flat. I'll do:

    Qualifications

    What we value:

    • ...

    Education & preferred qualifications:

    • ...

    Additional requirements:

    • ...
    But that might be too many subheadings. Alternatively, just one list with all qualifications. However, the posting separates them. I'll keep them as separate lists under the same heading with introductory paragraphs. Better: Use

    Qualifications

    then a
    for "What We Value", then another
    for "Education & Preferred Qualifications", then another for "Additional Requirements". But that's three lists. Could also use

    but rules only mention

    for section headings. Not allowed to use

    . So I'll just use paragraphs to separate. Let's see the rules: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have Requirements and Qualifications as separate sections. I'll do:

    Requirements

    • 5+ years of real estate and/or infrastructure investment management background
    • Enterprise SaaS experience is preferred
    • Understanding of the private markets/alternative investment lifecycle from manager due diligence to investment monitoring and analytics & reporting
    • Ability to work as part of a global, distributed organization
    • Progress towards CFA or CAIA is desirable
    • Experience using JIRA or other agile development tools
    • Ability to travel as required for client engagements (up to 20%), including internationally

    Qualifications

    • Highly driven, determined & business oriented
    • Highly polished executive presence and sophistication to gain credibility with the firm's most senior professionals and provide leadership, guidance, and direction to a team
    • Demonstrated ability to deliver on assigned responsibilities through commitment to quality and attention to detail
    But "What We Value" is more like soft skills/qualities. "Education & Preferred Qualifications" is requirements. "Additional Requirements" is also requirements. So I'll combine the latter two into Requirements. Now, Benefits and Pay: The posting includes "Salary Range: $80,000 - $140,000 Annual" and a detailed benefits list. So we should include:

    Pay

    Salary range: $80,000 - $140,000 annually. The range quoted applies to the role in the primary location specified; if the candidate would ultimately work outside of the primary location, the applicable range could differ.

    Benefits

    • Retirement savings plan (401K) with company match
    • Insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages
    • Paid time off including vacation, sick leave, short term disability, and family care responsibilities
    • Access to Employee Assistance Program
    • Incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans)
    • Eligibility for certain tax advantaged savings plans
    • Flexible Work Program
    • Paid volunteer days
    • Matching gift program
    • Access to employee networks
    • Development programs and educational support
    Also, there's a paragraph about "Work, Live and Grow" and "Inclusion, Diversity and Social Responsibility". That's more company culture. Could be part of "About the company" but not required. The rules say include section only when real specific content. We have Benefits and Pay. The company description is boilerplate? It's specific to State Street. Might include a "About the company" section? The rules don't list that as a standard heading. The example headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "About the company" is not listed. But we can include it as "About the company" if we want? The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, "Prefer a few substantive sections over many thin ones." The company description is somewhat generic. But the benefits and pay are specific. I'll include a brief "About the company" section with a paragraph summarizing State Street. But the posting has two "About State Street" paragraphs. I'll combine into one paragraph. But the rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statements are boilerplate. The "Discover more at StateStreet.com/careers" etc. are boilerplate. The Job ID is to be folded into a short

    or dropped. I'll drop it. Also, the "Job Application Disclosure" about lie detector test is legal boilerplate, remove. Now, let's write the HTML. I'll start with About the role, then Responsibilities, then Qualifications, then Requirements, then Pay, then Benefits. Maybe also include a short "About the company" before Benefits? But the benefits are part of the company. I'll include a brief company description as a paragraph before Pay/Benefits? Or just include in Benefits? The benefits section is about employee benefits. The company description is separate. I'll add a section "About the company" with a paragraph. But the rules didn't list "About the company". However, it's substantive. I'll include it as

    About the company

    with a paragraph. Let's structure:

    About the role

    Charles River for Private Markets is seeking a Product Manager, Real Assets to support a high performing team to execute the vision, strategy, creation, and advocacy of the core Charles River for Private Markets real assets offering. In this role, you will report directly to Head of Product and be responsible for enhancing our overall infrastructure and real estate product offering. You will work jointly with the product, engineering, and delivery teams to build and deliver the best possible experiences and value to customers within private markets investment management through the Charles River for Private Markets platform. The ideal candidate will have prior real assets investment background, excellent business acumen, passionate about evangelizing data-driven decision making and product advocacy at all levels. They should also be a strong communicator comfortable with facilitating executive level, decision justification, and roadmap. Here, you can work alongside talented engineers and product managers in an open, supportive, inclusive environment where your voice is valued, and you make your own decisions to drive forward Charles River for Private Markets’ mission to accelerate transparency, accuracy, and liquidity in private markets.

    Responsibilities

    • Be responsible for analyzing, enhancing and delivering all new real assets enhancements across internal teams, customers, and stakeholders.
    • Work collaboratively with existing real asset clients and account managers to represent the voice of the customer.
    • Ensure individual features and products are aligned with business objectives.
    • Lead client calls and workshops to collect and understand customer insights to drive product decisions.
    • Prioritize, communicate, and support complex and conflicting opportunities and market needs.
    • Engage with cross-functional heads to ensure alignment and orientation to product execution across the organization.
    • Own the real assets front to back product roadmap communication to internal and external stakeholders.
    • Work with product teams to ensure timely and complete requirements gathering, definition, deconstruction, and design.

    Qualifications

    • Highly driven, determined & business oriented.
    • Highly polished executive presence and sophistication to gain credibility with the firm's most senior professionals and provide leadership, guidance, and direction to a team.
    • Demonstrated ability to deliver on assigned responsibilities through commitment to quality and attention to detail.

    Requirements