Jobs · Business Development · New York

Strategy and Operations, Manager / Senior Manager - Future Platforms | Housing

EliseAI · New York, NY · 1 mo ago
On-siteBusiness Development$160k–$200k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications?, Skills?, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "About The Role" (we can use About the role heading). Then "Key Responsibilities" -> Responsibilities. Then "Requirements" -> Requirements. There's also "Why Join" but not required. Benefits section present: "Benefits In addition to the growth and impact..." includes list of benefits. Pay: "Job Compensation Range" gives salary range. Schedule: maybe not explicit; there is willingness to travel ~1x per month, work in person 4-5 days a week. That's schedule info. So we can include Schedule section with that info. Also maybe Qualifications not separate; Requirements covers. Skills maybe not separate. We'll include sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We must not repeat job title. No Job ID. Remove boilerplate like EEO etc. Also remove navigation etc. We'll keep substantive info. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from each section. Let's extract content. About EliseAI paragraph: we may not need to include? The instruction: "About EliseAI" is not a required heading; but we could include as part of About the role? Actually "About EliseAI" is company description; not required heading but we could include as prose under About the role? The role description includes "About The Role". The "About EliseAI" is separate but could be considered 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 should have heading About the role. Under that we can include the role description plus maybe company overview? The "About EliseAI" is not about the role but could be included as prose under About the role? Might be okay. But we must not repeat job title. We'll include the role description from "About The Role". Also maybe include the EliseAI description as part of About the role? Might be considered extra but not harmful. However we must preserve ALL substantive information; we cannot omit the EliseAI description if it's substantive. The posting includes that at top. It's about the company. Should we include it? The instruction says we should preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we don't have a heading for company overview, we could put it under About the role as a paragraph before the role specifics. That seems acceptable. Now extract About EliseAI content: "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." We'll keep that as a paragraph. Then "The Future Platforms Team - Executing on EliseAI’s Future Products" etc. That's also substantive about team. Could also be included under About the role? Might be okay. But we might risk too much. However we need to preserve all substantive info. Could include as another paragraph under About the role. But maybe better to create a separate section? Not in allowed headings. Could we add a heading like "About the team"? Not allowed per instruction; they gave examples but not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but we could add others? Safer to stick to those. So we put all company/team description under About the role. Now "About The Role" content: we need to include that as prose under About the role heading (maybe after the company description). We'll include the paragraph(s) from "About The Role". Let's extract: "As a Strategy and Operations Manager / Senior Manager on the Future Platforms team, you’ll help found and scale a critical new function at EliseAI: taking our future platform products from early customer promise to live, adopted, business-impacting deployments. This is a strategy role sitting inside a deployment function. You'll own how our deployment motion works and scales with our platform. You'll take ownership of a core piece of that motion and go deep: diagnosing where it breaks today, designing how it should work, and driving the change across Product, Engineering, Partnerships, and Delivery until it holds at scale. You'll also carry one or two engagements yourself, so you experience the problems you are trying to fix. You'll partner closely with senior leadership, but you'll own outcomes. This role is ideal for someone who wants to operate like a founder: comfortable with ambiguity, energized by turning a messy, undocumented process into a system that scales, and willing to do whatever it takes to make it real." We'll keep that. Now "Key Responsibilities" list: we need to convert to
    • . The bullet points are sentences starting with "Own core pieces of the deployment motion:" etc. We'll extract each bullet. Let's list: - Own core pieces of the deployment motion: Take a defined slice, such as scoping methodology, migration readiness, or the product requirements pipeline, and take it to the next level: sharpen the standards, close the gaps that surface at volume, and put real measurement behind it - Diagnose where the motion breaks: Use engagement data, retrospectives, and direct observation to find what actually drives deployment timeline, cost, and quality, and prioritize accordingly - Plan for the next order of magnitude: Model what the function needs at several times today's volume, identify the constraints that break first, and make the case for building ahead of them - Design and drive execution: Define priorities, timelines, and success metrics, then push changes through Product and delivery teams until they stick - Carry one or two engagements: Stay close enough to the customer-facing reality to pressure-test what you're building, and to keep your recommendations credible with the people running deployments full time - Shape the product roadmap: Turn patterns across engagements into prioritized requirements with Product and Engineering, grounded in what deployments actually surface - Build the team: Help hire, onboard, and ramp the people running engagements, and codify what good looks like - 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. Note the last bullet seems multiple sentences; we can keep as one
    • . Now "Requirements" section: we need to list bullet points. Extract: - 3 - 7 years of experience in management consulting, corporate strategy, product management, and/or founder/operator roles at high-growth startups - Strong analytical skills with the ability to make data-driven decisions - A track record of designing and standing up processes or systems that kept working after you moved on - Strong technical intuition, demonstrated by STEM degree or equivalent technical background - Proven ability to take ownership and operate autonomously with strong judgement in fast-paced, ambiguous environments - Proven ability to independently manage complex projects end-to-end in a client facing setting - Excellent communication and ability to naturally build strong relationships and influence across internal and external stakeholders - Willingness to travel ~1x per month for ~3 days - Willingness to work in person at our office 4-5 days a week Now "Benefits" section: list. Extract: - 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! Now Pay: "Job Compensation Range The salary range for the Manager role is $160,000 - $200,000, and for Senior Manager is $190,000 - $250,000. EliseAI offers a competitive total rewards package which includes base salary, equity, and a comprehensive benefits & perks package. Exact compensation is determined based on a number of factors including experience, skill level, location and qualifications which are assessed during the interview process. Additional details about total compensation and benefits will be provided by our Recruiting Team during the hiring process." We'll include that as prose under Pay heading. Not a list. Schedule: we have willingness to travel ~1x per month for ~3 days and willingness to work in person at our office 4-5 days a week. That's schedule info. We'll put under Schedule heading as prose. Now we must not include boilerplate like EEO etc. Remove those paragraphs. Now produce HTML fragment. Structure:

      About the role

      ... company description ...

      ... Future Platforms Team description ...

      ... About The Role content ...

      Responsibilities

      • ...
      • ...

      Requirements

      • ...
      • ...

      Benefits

      • ...
      • ...

      Pay

      ... compensation range ...

      Schedule

      ... travel and in-office expectations ...

      Make sure no extra whitespace issues. Now craft the HTML. Let's write the paragraphs. About EliseAI paragraph: combine sentences. "The Future Platforms Team - Executing on EliseAI’s Future Products" paragraph: we need to include that as well. Let's write:

      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.

      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

Similar jobs