Recruiter
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting includes "About EliseAI", "About The Role", "Key Responsibilities", "Requirements", "Why join", "Benefits", "Job Compensation Range". Also there is "Move at rocket speed..." paragraph after responsibilities? Actually after responsibilities there is a paragraph about culture: "Move at rocket speed, build something massive..." That's part of description maybe could be part of About the role? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we need sections: About EliseAI? Not listed in allowed headings but could be considered "About the role"? Actually they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About EliseAI". However we can still include a heading if content exists? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical headings we may use. It doesn't forbid other headings, but we should follow the pattern. Probably we should include "About EliseAI" as a section? 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." It doesn't forbid other headings. But they gave examples; we can include "About EliseAI" as a heading if we want. However they said "Prefer a few substantive sections over many thin ones." So maybe combine About EliseAI and About the role into one "About the role" section? But there is distinct content about EliseAI mission. Could be part of "About the role" or separate "About EliseAI". The instruction: "include a section ONLY when the posting has real, specific content for it". So we need to decide which sections to include. We have content for: - About EliseAI (mission, housing, healthcare, funding) - About The Role (description of role, working with team, owning life cycle) - Key Responsibilities (list) - Requirements (list) - Why join (growth and impact paragraph) - Benefits (list) - Job Compensation Range (Pay) - Possibly Schedule? Not mentioned explicitly except "Willingness to work in person at our office 4-5 days a week" which is schedule/location expectation. That could be considered Schedule? It's about in-person expectation. Could be placed under Requirements or a separate Schedule section. Since they said include Schedule only if posting actually states them. It does state willingness to work in person 4-5 days a week. That's schedule info. So we could create a Schedule section with that detail. - Qualifications? Not separate; Requirements covers qualifications. - Skills? Not separate. Thus we can have sections: About EliseAI, About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, Why join (maybe "Why join" could be part of Benefits or culture). But "Why join" is a paragraph about growth and impact; could be its own section like "Why join EliseAI". Not in examples but okay. We need to use
for headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, accommodation contact, etc. Also remove duplicated lines. Also remove application instructions (none present). Also remove navigation/cookie/legal.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About EliseAI paragraph:
"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 need to keep that as prose
.
About The Role:
"EliseAI is growing rapidly - to support that growth, we are looking to add an ambitious Recruiter to our recruiting team. You will work closely with other Recruiters, Recruiting Coordinators and EliseAI leadership to bring exceptional talent to EliseAI, owning the entire recruiting life cycle. The ideal candidate will have passion and experience around innovative sourcing and outreach strategies, technology and recruiting best practices, and has a track record of success bringing top talent to SaaS companies."
That's prose.
Key Responsibilities list:
- Support all aspects of the recruiting process across technical and non-technical roles, while working closely with hiring managers and EliseAI leadership
- Collaborate and establish relationships with leaders across the company to understand their hiring objectives and ideal candidate profile
- Build a strong pipeline of candidates by utilizing a range of sourcing techniques, including LinkedIn and other outside-the-box sourcing strategies, while staying on top of hiring market trends
- Identify, prescreen, and evaluate both passive and active candidates to ensure high quality talent
- Hold intake meetings with interviewers to ensure a thorough and comprehensive hiring process and high-quality candidate experience
- Maintain our ATS to ensure effective reporting and a data driven recruiting approach
- Run debriefs on the hiring process and continuously implement improvements
- Own creation of job descriptions and practical assessments
- Manage relationships with our external recruiting agencies
- Plan campus and lateral recruiting events, career fairs, meetups, etc.
- Ensure all candidates in the recruitment process have a positive experience with EliseAI
- Support other ad-hoc recruiting projects
- Attract top-tier talent to join our driven team
After that there is a paragraph: "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."
That's more description; could be part of About the role or a separate "Culture" section. Since we already have About the role, we could append that paragraph to About the role. But we need to preserve all substantive info; we can include it as part of About the role
after the earlier paragraph. That's fine.
Requirements list:
- 1-8 years of experience as a full-cycle Recruiter
- Experience working at a high growth startup or fast paced environment
- Excellent networker and understand how to effectively engage high caliber candidates across multiple business functions
- Ability to multitask and prioritize multiple tasks and projects
- Excellent organization skills with great attention to detail
- Strong EQ and analytical skills
- Strong verbal and written communication skills
- Willingness to work in person at our office 4-5 days a week
Note: The last item about willingness to work in person 4-5 days a week could be moved to Schedule section. But it's also a requirement. We could keep it under Requirements and also maybe create Schedule section with that detail. However to avoid duplication, we should not repeat same content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but better to avoid. We could treat the in-person expectation as part of Requirements (makes sense) and not create a separate Schedule section. However they said include Schedule only if posting actually states them. It does state willingness to work in person 4-5 days a week. So we could create a Schedule section with that detail, and remove it from Requirements to avoid duplication. But then we would lose that detail from Requirements if we remove it. We could keep it in Requirements and also have Schedule referencing it? That would be duplication. Better to move it to Schedule and keep Requirements without that line. But then we lose the explicit "Willingness to work in person at our office 4-5 days a week" from Requirements; but it's still present in Schedule section, so overall preserved. That's acceptable.
Thus Requirements list will have 7 items (excluding the in-person line). We'll need to ensure we keep all other requirements.
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!
Also note "competitive salaries along with the following benefits:" preceding list.
Pay section: "The salary range for this role is $90,000 - $175,000. EliseAI offers a competitive total rewards package which includes base salary, equity, and a comprehensive benefits & perks package. Exact compensation inclusive of salary and any bonuses is determined based on a number of factors including experience and 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 need to output Pay section with that prose. Not to include filler like "commensurate with experience". It's fine.
Why join section: paragraph:
"Growth and impact. It’s not often that you can get in on the ground floor of a funded (unicorn!) startup that’s scaling so fast. That means that instead of following a playbook, you’ll be writing it. Every single day you will be challenged to identify how we can scale and execute on it. You’ll learn what works when you succeed and what doesn’t when you fail. Either way, the rest of the team will be here to support you."
We'll put that as
under heading "Why join EliseAI" or "Why join". Use
Why join
.
Now we need to decide ordering. Typically: About EliseAI, About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, Why join. Or maybe Why join before Benefits. We'll follow logical flow: About EliseAI, About the role, Responsibilities, Requirements, Benefits, Pay, Why join, Schedule. But schedule is about in-person expectation; could be after Requirements. Let's put Schedule after Requirements before Benefits? Actually schedule is about work arrangement; could be after Requirements. We'll do: About EliseAI, About the role, Responsibilities, Requirements, Schedule, Benefits, Pay, Why join.
Check that we have content for each section.
Now we need to strip boilerplate: EEO statement, accommodation contact, etc. Also remove "EliseAI provides equal employment opportunities..." etc. Also remove "Employment with EliseAI is on an “at-will” basis..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "If you need assistance or a reasonable accommodation..." etc.
Also remove duplicated lines: none.
Now produce HTML.
We'll need to wrap each section in heading then content.
For lists:
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, accommodation contact, etc. Also remove duplicated lines. Also remove application instructions (none present). Also remove navigation/cookie/legal. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About EliseAI paragraph: "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 need to keep that as prose
. About The Role: "EliseAI is growing rapidly - to support that growth, we are looking to add an ambitious Recruiter to our recruiting team. You will work closely with other Recruiters, Recruiting Coordinators and EliseAI leadership to bring exceptional talent to EliseAI, owning the entire recruiting life cycle. The ideal candidate will have passion and experience around innovative sourcing and outreach strategies, technology and recruiting best practices, and has a track record of success bringing top talent to SaaS companies." That's prose. Key Responsibilities list: - Support all aspects of the recruiting process across technical and non-technical roles, while working closely with hiring managers and EliseAI leadership - Collaborate and establish relationships with leaders across the company to understand their hiring objectives and ideal candidate profile - Build a strong pipeline of candidates by utilizing a range of sourcing techniques, including LinkedIn and other outside-the-box sourcing strategies, while staying on top of hiring market trends - Identify, prescreen, and evaluate both passive and active candidates to ensure high quality talent - Hold intake meetings with interviewers to ensure a thorough and comprehensive hiring process and high-quality candidate experience - Maintain our ATS to ensure effective reporting and a data driven recruiting approach - Run debriefs on the hiring process and continuously implement improvements - Own creation of job descriptions and practical assessments - Manage relationships with our external recruiting agencies - Plan campus and lateral recruiting events, career fairs, meetups, etc. - Ensure all candidates in the recruitment process have a positive experience with EliseAI - Support other ad-hoc recruiting projects - Attract top-tier talent to join our driven team After that there is a paragraph: "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." That's more description; could be part of About the role or a separate "Culture" section. Since we already have About the role, we could append that paragraph to About the role. But we need to preserve all substantive info; we can include it as part of About the role
after the earlier paragraph. That's fine. Requirements list: - 1-8 years of experience as a full-cycle Recruiter - Experience working at a high growth startup or fast paced environment - Excellent networker and understand how to effectively engage high caliber candidates across multiple business functions - Ability to multitask and prioritize multiple tasks and projects - Excellent organization skills with great attention to detail - Strong EQ and analytical skills - Strong verbal and written communication skills - Willingness to work in person at our office 4-5 days a week Note: The last item about willingness to work in person 4-5 days a week could be moved to Schedule section. But it's also a requirement. We could keep it under Requirements and also maybe create Schedule section with that detail. However to avoid duplication, we should not repeat same content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but better to avoid. We could treat the in-person expectation as part of Requirements (makes sense) and not create a separate Schedule section. However they said include Schedule only if posting actually states them. It does state willingness to work in person 4-5 days a week. So we could create a Schedule section with that detail, and remove it from Requirements to avoid duplication. But then we would lose that detail from Requirements if we remove it. We could keep it in Requirements and also have Schedule referencing it? That would be duplication. Better to move it to Schedule and keep Requirements without that line. But then we lose the explicit "Willingness to work in person at our office 4-5 days a week" from Requirements; but it's still present in Schedule section, so overall preserved. That's acceptable. Thus Requirements list will have 7 items (excluding the in-person line). We'll need to ensure we keep all other requirements. 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! Also note "competitive salaries along with the following benefits:" preceding list. Pay section: "The salary range for this role is $90,000 - $175,000. EliseAI offers a competitive total rewards package which includes base salary, equity, and a comprehensive benefits & perks package. Exact compensation inclusive of salary and any bonuses is determined based on a number of factors including experience and 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 need to output Pay section with that prose. Not to include filler like "commensurate with experience". It's fine. Why join section: paragraph: "Growth and impact. It’s not often that you can get in on the ground floor of a funded (unicorn!) startup that’s scaling so fast. That means that instead of following a playbook, you’ll be writing it. Every single day you will be challenged to identify how we can scale and execute on it. You’ll learn what works when you succeed and what doesn’t when you fail. Either way, the rest of the team will be here to support you." We'll put that as
under heading "Why join EliseAI" or "Why join". Use