Member Operations Associate (NY/NJ)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the posting. Content: - Intro about Honey Homes: description of company and role. Could be "About the role" or maybe "About Honey Homes"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections accordingly. We need to decide what goes where. The posting includes: - About Honey Homes (company description) and description of role: "The Member Operations Associate is the evolution..." etc. That could go under "About the role". Could also be "About Honey Homes" but not in list; we stick to given headings. - Responsibilities: bullet points under "What You'll Do": Own the member journey, Solve today's problems while eliminating tomorrow's, Use AI to multiply your impact, Improve The Member Experience, Own a functional area, Operate with high agency. - What Success Looks Like: could be part of Responsibilities or maybe "Qualifications"? It's more about outcomes; could be under "Responsibilities" or maybe a separate section like "Expectations". But we only have allowed headings; we could put under "Responsibilities" as part of responsibilities. - What We're Looking For: list of qualifications/experience: 2+ years experience, communication skills, organizational skills, high agency, curiosity, comfort with AI tools, critical thinking, problem solving, collaboration, interest in process improvement, experience in startup a plus. That's "Requirements" or "Qualifications" or "Skills". We need to decide. - Compensation: "The compensation for this role is $72,000 plus equity. Because it's part of a structured program, we offer the same compensation package to everyone in the program and therefore is non-negotiable." That's Pay. - Benefits: Not explicitly mentioned besides equity? There's no explicit benefits like health, PTO. So we should not create Benefits section unless posting actually states them. It does not list benefits besides equity (which is part of compensation). So we skip Benefits. - Schedule: Not mentioned. So skip Schedule. - Qualifications: Could be same as Requirements. We need to avoid duplicate sections. Choose either Requirements or Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple if content exists. We need to decide what goes where. We have: - About the role: company description and role overview. - Responsibilities: detailed duties. - Requirements: maybe the experience and skills needed (2+ years experience, communication, etc.) - Qualifications: maybe the same? Could separate "Requirements" for mandatory, "Qualifications" for preferred? The posting says "The Strongest Candidates Will Bring Many Of The Following" then list items, and "Experience working in a fast-paced startup environment is a plus." So we could treat the list as Requirements (or Qualifications). Since there's no separate "Preferred" vs "Required", we can put all under Requirements. - Skills: maybe we could extract specific skills like communication, organizational, AI tools, critical thinking, problem solving, collaboration, process improvement. But those are already in Requirements. Could create Skills section for those. But we must avoid thin sections. Better to combine. Given we have limited distinct content, we could have: - About the role - Responsibilities - Requirements (including experience, skills, qualifications) - Pay We should not create Benefits or Schedule. We must not include boilerplate like EEO statement. Remove that. Also remove duplicated lines. Now craft HTML. We need to wrap each section in

heading then content: either

for prose or

• for lists. Let's extract prose for About the role: "About Honey Homes Honey Homes is reimagining homeownership through a membership that makes maintaining a home effortless. Our members have a dedicated handyman who proactively cares for their home year-round, helping prevent small problems from becoming expensive ones. The Member Operations Associate is the evolution of traditional customer support. Rather than simply responding to members, you'll own member outcomes while helping improve the systems, tools, and processes that power the entire member experience. Every day you'll work directly with homeowners, helping them solve problems and coordinating across teams to ensure they're taken care of. But that's only part of the job. You'll also identify recurring issues, improve workflows, leverage AI to eliminate repetitive work, and partner across the business to make Honey Homes better for both our members and our internal teams. This is an ideal role for someone who enjoys helping people, loves solving problems, thinks in systems rather than one-off solutions, and is excited about using AI and technology to fundamentally change how customer operations are run." That's a paragraph. Now Responsibilities: list items under "What You'll Do". We'll create
  • for each bullet. Bullet points: - Own the member journey: Own member issues from beginning to end across app messaging, phone, SMS, and email. You'll coordinate across teams, communicate proactively, remove blockers, and ensure every member feels taken care of throughout their experience. Solving the immediate problem is expected. Owning the outcome is the standard. - Solve today's problems while eliminating tomorrow's: Every recurring member issue should trigger a deeper question: Why did this happen? How do we prevent it? Can we automate it? Should we document it? Does another team need to know? Your job isn't complete when the ticket is resolved. It's complete when you've helped reduce the likelihood another member experiences the same problem. - Use AI to multiply your impact: Leverage AI tools like Claude and ChatGPT to eliminate repetitive work, improve documentation, automate workflows, and increase your effectiveness. We expect everyone on the team to actively experiment with new tools, test ideas, and continuously improve how work gets done. - Improve The Member Experience: Member Success sits at the center of the member experience. You'll partner closely with Sales, Walkthrough Specialists, Field Operations, Billing, Product, Marketing, Recruiting, and other teams to surface trends, advocate for change, and help implement better ways of working. Our responsibility is the entire member journey, not just the conversations that reach our queue. - Own a functional area: In addition to supporting members, every Member Operations Associate owns an area of the business. This might include onboarding, messaging, knowledge management, phone operations, AI tools, NPS, reporting, documentation, or another operational focus area. You'll become the team's subject matter expert and be responsible for continuously improving how that area operates over time. - Operate with high agency: We don't wait for someone else to identify problems. We expect every teammate to proactively find opportunities, propose solutions, build improvements, measure their impact, and share what they've learned. Curiosity, ownership, systems thinking, and continuous improvement aren't nice-to-haves—they're core expectations of the role. We could also include "What Success Looks Like" as part of Responsibilities or separate but we can incorporate as bullet points under Responsibilities maybe as additional bullets. But we have already covered many duties; the "What Success Looks Like" list includes: - Deliver consistently exceptional experiences for Honey Homes members. - Develop expertise in your operational ownership area and drive measurable improvements. - Identify recurring member issues and help implement solutions that reduce future support volume. - Build AI-powered workflows and automations that improve efficiency across the team. - Create documentation, SOPs, and knowledge resources that make the organization more effective. - Become a trusted cross-functional partner who proactively identifies opportunities to improve operations and follows through on delivering results. These are also responsibilities/expectations. Could add as additional bullets under Responsibilities. We'll combine. Now Requirements: list of qualifications. From "What We're Looking For": - 2+ years of experience in customer support, customer success, operations, hospitality, or another customer-facing role. - Outstanding written and verbal communication skills. - Strong organizational skills and the ability to manage multiple priorities simultaneously. - High agency and a bias toward ownership - you don't wait to be asked to solve problems. - Curiosity and a desire to continuously improve how work gets done. - Comfort learning and using AI tools like ChatGPT, Claude, or similar technologies to improve productivity. - Strong critical thinking and problem-solving skills. - The ability to collaborate effectively across multiple teams. - An interest in process improvement, operational excellence, and building scalable systems. - Experience working in a fast-paced startup environment is a plus. We'll put these as
    • . Now Pay: "$72,000 plus equity. Because it's part of a structured program, we offer the same compensation package to everyone in the program and therefore is non-negotiable." We'll put as

      . Now ensure we don't include any boilerplate like EEO statement. Now produce HTML fragment. We must not include or . Just the sections. Let's craft:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Pay

      ...

      Make sure no extra whitespace issues. Now write the content precisely. Let's copy the About the role paragraph exactly as we wrote. Check for any stray lines. Now Responsibilities bullets: need to be concise but preserve all detail. We'll write each bullet as a single sentence or multiple sentences but within
    • . Let's craft. Bullet 1: Own the member journey: Own member issues from beginning to end across app messaging, phone, SMS, and email. You'll coordinate across teams, communicate proactively, remove blockers, and ensure every member feels taken care of throughout their experience. Solving the immediate problem is expected. Owning the outcome is the standard. Bullet 2: Solve today's problems while eliminating tomorrow's: Every recurring member issue should trigger a deeper question: Why did this happen? How do we prevent it? Can we automate it? Should we document it? Does another team need to know? Your job isn't complete when the ticket is resolved. It's complete when you've helped reduce the likelihood another member experiences the same problem. Bullet 3: Use AI to multiply your impact: Leverage AI tools like Claude and ChatGPT to eliminate repetitive work, improve documentation, automate workflows, and increase your effectiveness. We expect everyone on the team to actively experiment with new tools, test ideas, and continuously improve how work gets done. Bullet 4: Improve The Member Experience: Member Success sits at the center of the member experience. You'll partner closely with Sales, Walkthrough Specialists, Field Operations, Billing, Product, Marketing, Recruiting, and other teams to surface trends, advocate for change, and help implement better ways of working. Our responsibility is the entire member journey, not just the conversations that reach our queue. Bullet 5: Own a functional area: In addition to supporting members, every Member Operations Associate owns an area of the business. This might include onboarding, messaging, knowledge management, phone operations, AI tools, NPS, reporting, documentation, or another operational focus area. You'll become the team's subject matter expert and be responsible for continuously improving how that area operates over time. Bullet 6: Operate with high agency: We don't wait for someone else to identify problems. We expect every teammate to proactively find opportunities, propose solutions, build improvements, measure their impact, and share what they've learned. Curiosity, ownership, systems thinking, and continuous improvement aren't nice-to-haves—they're core expectations of the role. Bullet 7: What Success Looks Like: Deliver consistently exceptional experiences for Honey Homes members. Develop expertise in your operational ownership area and drive