AI Deployments PM - Future Platforms | Housing

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Benefits, Pay (if present), Schedule (if present). We must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info. Must not include sections with placeholder text. Must include only sections where there is real content. We have content: About EliseAI (company description) maybe not needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The posting includes "About EliseAI" and "The Future Platforms Team - Executing on EliseAI’s Future Products" and "About The Role". We need to decide what sections to include. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. We have "About The Role" paragraph: description of role. That's content for "About the role". We'll put that in

. Responsibilities: list under "Key Responsibilities". We'll make

• items. Requirements: list under "Requirements". We'll make
  • . Qualifications: maybe not separate; but we have "A degree in statistics, mathematics, computer science, or a related technical field is a plus". That could be qualifications. Could include under Requirements or Qualifications. Since we have a Qualifications section possible, we could put that there. But we need to avoid thin sections. Could combine qualifications into Requirements. But we have separate "Requirements" heading already. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Qualifications if we have content. We have degree plus maybe "Willingness to work in person at our office 4-5 days a week" could be schedule? Actually schedule is about work schedule; we have that. So we could put schedule section with that line. Skills: maybe we have analytical skills, communication skills, self-starter, etc. Could be under Skills. But we already have many skill-like items in Requirements. Might be redundant. Better to keep Requirements as is and not create Skills unless we have distinct skill list. The posting includes "Strong analytical skills and comfort working directly with spreadsheets and imperfect data", "Ability to spot patterns...", "Clear communication skills...", "A self-starter...". Those are skills/requirements. Could put them under Skills. But we already have Requirements list; we could split: Requirements (experience) and Skills (abilities). However instruction: prefer a few substantive sections over many thin ones. So maybe we keep just Requirements and include all bullet points there. Then we don't need Skills. Benefits: we have a Benefits section with list. We'll include Benefits. Pay: we have "Job Compensation Range The salary range for this role is $150,000 - $250,000." So we include Pay. Schedule: we have "Willingness to work in person at our office 4-5 days a week." That's schedule expectation. So we include Schedule. We must not include boilerplate like EEO, etc. Also must not include "About EliseAI" and "The Future Platforms Team" maybe not needed as they are not sections headings we defined. Could we include them under About the role? Probably not; they are company description. The instruction says we should preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Where to put? Could be a short paragraph before sections, maybe as a

    without heading. The instruction: "fold minor metadata into a short

    or drop it." The company description is not minor metadata; it's substantive about the company. We should keep it. Since we cannot add arbitrary headings not in list, we can just put it as a

    before the sections. That's acceptable. Thus output: start with a

    containing EliseAI description and Future Platforms team description? Actually we have two paragraphs: "About EliseAI" and "The Future Platforms Team - Executing on EliseAI’s Future Products". We'll combine them into a single

    or maybe two

    s. We'll keep them as separate

    elements. Then

    About the role

    with the paragraph from "About The Role". Then

    Responsibilities

    with
    list of responsibilities. Then

    Requirements

    with
    list of requirements (including experience, analytical skills, communication, self-starter, degree plus, willingness to work in person? Actually willingness to work in person is schedule; we'll move that to Schedule.) Then

    Benefits

    with
    list. Then

    Pay

    with

    containing salary range. Then

    Schedule

    with

    containing willingness to work in person 4-5 days a week. We must not include sections with placeholder text. All have content. We must not include any other headings like Qualifications, Skills. Now we need to ensure we preserve all substantive information: Let's extract. Company description: "About EliseAI At EliseAI, we're improving the industries that matter most: housing and healthcare. Everyone needs a place to live and access to quality healthcare, yet both are often harder to secure than they should be. By integrating AI agents deeply into existing workflows, we make them more efficient, reduce costs, and improve the experience for everyone. Housing: We simplify how renters tour apartments, sign leases, submit maintenance requests, and stay connected with their property team—bringing everything they need for their home into one place.Healthcare: We make it easy to schedule appointments, complete intake forms, and we help patients communicate with providers, so everyone can focus on health instead of paperwork. With EliseAI, organizations reduce manual work, improve accessibility, and deliver a seamless experience across essential services. We recently raised a $250 million Series E round led by Andreessen Horowitz to accelerate this mission." Future Platforms Team description: "The Future Platforms Team - Executing on EliseAI’s Future Products The Future Platforms team is responsible for executing on the next generation of AI products and business lines. This team will blend go-to-market, product, operations, and strategy with a mandate to push the frontier of AI and own everything required to take them from idea to market leadership. Our goal is to take Elise from agentic AI to truly end-to-end autonomous operations, fundamentally transforming how housing operators run their businesses and how residents experience their homes. Future Platforms will operate as a startup within a startup, run like a Seed or Series A company but with the capital, resources, and market access of a well-funded Series E, deep C-suite involvement (CEO, CRO, CSO, CTO) and founder-level ownership from day one." About The Role paragraph: "About The Role EliseAI is expanding its platform across housing, and we’re looking for an AI Deployment PM to help bring new products to customers. You’ll work closely with Product and Engineering to own the work between a customer saying yes and a successful launch. This is a hands-on role: you’ll drive deployments alongside customers and internal teams, work through complex customer data, and identify issues that need to be resolved before a product goes live. Our deployment processes are still taking shape, so you’ll also help establish a clearer, more repeatable way to launch as we grow." Key Responsibilities bullet list: - Own customer deployments from initial discovery through launch, keeping work on track and resolving blockers - Work directly with customer teams, including operations leaders, accounting controllers, and property managers, to understand their processes and requirements - Analyze customer data, identify discrepancies, and ask the questions needed to determine how information should flow into EliseAI’s products - Partner with Product and Engineering to investigate issues, set priorities, and turn what you learn during deployments into product improvements - Build practical processes and documentation that make future deployments faster and more reliable - Identify and communicate progress, risks, and decisions clearly to customers and internal stakeholders - Attract top-tier talent to join our driven team - Move at rocket speed, build something massive. We’re scaling fast, solving real client problems with precision and ambition. Here, you own your impact; full autonomy, no micromanagement, no fluff. We hire the best, expect the best, and give you the masterclass of your career. It’s hard, it’s intense, and it’s the most rewarding work you’ll ever do. If you’re hungry, driven, and ready to build something massive, climb aboard. Wait the last bullet seems like a paragraph not a bullet; but it's part of the responsibilities section after the bullet list? Actually the text after "Attract top-tier talent to join our driven team" continues as a paragraph. We'll treat it as a separate

    under Responsibilities maybe. But we can include as a

    after the list. Requirements bullet list: - 2-4 years of experience in a role involving analytical problem-solving and ownership of complex projects. Experience in consulting, banking, data analytics, or an early-stage startup could be a strong fit - Strong analytical skills and comfort working directly with spreadsheets and imperfect data - Ability to spot patterns, get to the root of a problem, and make progress when the path forward is unclear - Clear communication skills and confidence working with customers and cross-functional teams - A self-starter who takes ownership, follows through on details, and is willing to do hands-on work to make a deployment successful - A degree in statistics, mathematics, computer science, or a related technical field is a plus - Willingness to work in person at our office 4-5 days a week But we moved willingness to work in person to Schedule. So we should remove that from Requirements list. Thus Requirements list will have first six bullets. Benefits list: - Equity in the company - Medical, Dental and Vision premiums covered at 100% - Fully paid parental leave - Commuter benefits - 401k benefits - Fitness & home services stipend to cover part of your expenses so you can focus on what matters - A collaborative in-office environment with an open floor plan, fully stocked kitchen, and all meals covered in the office - Unlimited vacation and paid holidays - We'll cover relocation packages and make the move exciting, not painful! Pay: salary range $150,000 - $250,000. Schedule: Willingness to work in person at our office 4-5 days a week. Now we need to output HTML fragment only. We'll wrap company description paragraphs in

    without heading. Potentially we need to keep the "About EliseAI" and "Future Platforms Team" as separate

    elements. Let's craft. Note: Ensure no extra whitespace causing issues? It's fine. We'll output:

    About EliseAI ...

    The Future Platforms Team ...

    About the role

    EliseAI is expanding its platform across housing, and we’re looking for an AI Deployment PM to help bring new products to customers. You’ll work closely with Product and Engineering to own the work between a customer saying yes and a successful launch. This is a hands-on role: you’ll drive deployments alongside customers and internal teams, work through complex customer data, and identify issues that need to be resolved before a product goes live. Our deployment processes are still taking shape, so you’ll also help establish a clearer, more repeatable way to launch as we grow.

    Responsibilities

    • Own customer deployments from initial discovery through launch, keeping work on track and resolving blockers
    • Work directly with customer teams, including operations leaders, accounting controllers, and property managers, to understand their processes and requirements
    • Analyze