Software Engineer
AndHealth · Columbus, OH · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Content:
- Intro about AndHealth mission.
- "The Opportunity": description of role.
- "What You'll Do In The Role": list of duties.
- "Education & Licensure Requirements": Bachelor’s degree in Computer Science, Engineering, or related field preferred.
- "Other Skills Or Qualifications": bullet list of attributes.
- "Here's What We'd Like To Offer You": description of benefits: Equal investment..., fun start-up environment..., ability to demonstrate creativity..., team..., ongoing opportunities..., Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more.
- Also EEO boilerplate etc to remove.
- No explicit Pay or Schedule mentioned. So we should NOT include Pay or Schedule sections.
- Benefits: we have specific benefits listed: Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more. Also mention "Full-time employees are eligible to participate in our benefits package". That's enough for Benefits section.
- About the role: we can have a section "About the role" summarizing mission and opportunity? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to include About the role if there is real specific content. The posting includes mission and opportunity description. That's suitable.
- Responsibilities: from "What You'll Do In The Role": list of duties.
- Requirements: Education & Licensure Requirements (Bachelor’s degree...). Could also include other requirements? We'll put that.
- Qualifications: maybe combine with Skills? The posting has "Other Skills Or Qualifications". Could treat as Qualifications or Skills. We need both sections if content. We have "Other Skills Or Qualifications" list: Patient first attitude, Metric-Driven Engineering & Decision Making, Systems & Integration Expertise, Cross-Functional Collaboration, Growth Mindset & Craft Orientation. That's more like qualifications/skills. We could split: Qualifications (education) and Skills (these). But we already have Education & Licensure Requirements as Requirements. Could treat Requirements as education, Qualifications as other skills. Or we could have Requirements (education) and Skills (the list). The instruction says we can include sections only when posting has real specific content. We have both.
Thus sections:
- About the role: mission and opportunity description.
- Responsibilities: list of duties from "What You'll Do In The Role".
- Requirements: Bachelor’s degree in Computer Science, Engineering, or related field preferred.
- Skills: list of patient-first attitude etc.
- Benefits: list of benefits.
We should not include Qualifications if we used Skills; but we could also have Qualifications as the same list. Better to follow typical: Requirements (education), Qualifications (other skills), Benefits. But we have both Requirements and Qualifications. The instruction gave example headings including Qualifications. So we can have Requirements (education) and Qualifications (the list). Then Skills maybe not needed. However we have also "Other Skills Or Qualifications". That could be Qualifications. So we can have Requirements (education) and Qualifications (the list). Skills section maybe not needed. But we could still include Skills if we want to split but risk duplication. Better to follow: Requirements (education), Qualifications (the list). Benefits.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check if any Pay or Schedule: none, so omit.
Now we need to format.
About the role: combine mission and opportunity description into prose.
Responsibilities: list each duty from "What You'll Do In The Role". Let's extract bullet points:
- partner with our care team to build a world-class mobile experience to help patients manage chronic illness.
- Create an initial first impression that delights our patients, leading to success is achieving our enrollment goals, while also focusing on building the right windows into the metrics that matter so we can experiment rapidly.
- Improve both internal and external user experiences in addition to business processes, by integrating with modern services via third-party APIs.
- Leverage Google Cloud Platform services to architect, build, and deploy scalable and robust backend systems that support new features and functionaly.
- Collaborate closely with data analysts and engineers to improve reporting and analytics insights, while also optimizing the user experience and automating decision-making processes.
- Practice continuous integration and deployment to minimize feedback cycles.
- Decide when to sprint and when to be deliberate in your software engineering practices.
- Continuously improve our toolset to make future development easier.
We need to preserve all substantive information; do not invent or summarize away detail. So we keep each as list item.
Requirements: "Bachelor’s degree in Computer Science, Engineering, or related field preferred."
Qualifications: list of attributes:
- “Patient first” attitude: Ability to design and evaluate tools and experiences through a patient-first lens, with a strong instinct for usability, empathy, and quality that leads to “wow” experiences.
- Metric-Driven Engineering & Decision Making: Skilled in defining success metrics upfront and using data to guide technical decisions, prioritize work, and iterate quickly based on outcomes and feedback.
- Systems & Integration Expertise: Proven ability to design, build, and maintain integrations across complex systems, databases, and third-party APIs, ensuring reliable data flow and cohesive end-to-end experiences.
- Cross-Functional Collaboration: Strong communicator and partner who works effectively with Product, Care, and Enrollment teams to align technical solutions with real-world operational and patient needs.
- Growth Mindset & Craft Orientation: Demonstrates genuine passion for building, continuous learning, and improving one’s craft—motivated by impact, ownership, and the desire to improve patient care through technology.
We need to keep the quotes? Probably keep as is.
Benefits: "Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more." Also earlier sentences about fun environment etc. Those are also benefits? They are more about culture. Could include them as part of Benefits section? The instruction: Benefits section only if posting actually states them. The posting includes "Here's What We'd Like To Offer You" with several bullet-like sentences: Equal investment and support for our people and patients. A fun and ambitious start-up environment with a culture that takes on important things, takes risks, and learns quickly. The ability to demonstrate creativity, innovation, and conscientiousness, and find joy in working together. A team of highly skilled, incredibly kind, and welcoming employees, every one of whom has something unique to offer. We know that the overall success of our business is a collaborative effort, and we strive to provide ongoing opportunities for our employees to learn and grow, both personally and professionally. Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more.
Thus we can include all those as benefits. So Benefits section will have a list of items: Equal investment and support for our people and patients; A fun and ambitious start-up environment with a culture that takes on important things, takes risks, and learns quickly; The ability to demonstrate creativity, innovation, and conscientiousness, and find joy in working together; A team of highly skilled, incredibly kind, and welcoming employees, every one of whom has something unique to offer; Ongoing opportunities for employees to learn and grow, both personally and professionally; Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more.
We should not include boilerplate EEO etc.
Now produce HTML fragment:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to include About the role if there is real specific content. The posting includes mission and opportunity description. That's suitable.
- Responsibilities: from "What You'll Do In The Role": list of duties.
- Requirements: Education & Licensure Requirements (Bachelor’s degree...). Could also include other requirements? We'll put that.
- Qualifications: maybe combine with Skills? The posting has "Other Skills Or Qualifications". Could treat as Qualifications or Skills. We need both sections if content. We have "Other Skills Or Qualifications" list: Patient first attitude, Metric-Driven Engineering & Decision Making, Systems & Integration Expertise, Cross-Functional Collaboration, Growth Mindset & Craft Orientation. That's more like qualifications/skills. We could split: Qualifications (education) and Skills (these). But we already have Education & Licensure Requirements as Requirements. Could treat Requirements as education, Qualifications as other skills. Or we could have Requirements (education) and Skills (the list). The instruction says we can include sections only when posting has real specific content. We have both.
Thus sections:
- About the role: mission and opportunity description.
- Responsibilities: list of duties from "What You'll Do In The Role".
- Requirements: Bachelor’s degree in Computer Science, Engineering, or related field preferred.
- Skills: list of patient-first attitude etc.
- Benefits: list of benefits.
We should not include Qualifications if we used Skills; but we could also have Qualifications as the same list. Better to follow typical: Requirements (education), Qualifications (other skills), Benefits. But we have both Requirements and Qualifications. The instruction gave example headings including Qualifications. So we can have Requirements (education) and Qualifications (the list). Then Skills maybe not needed. However we have also "Other Skills Or Qualifications". That could be Qualifications. So we can have Requirements (education) and Qualifications (the list). Skills section maybe not needed. But we could still include Skills if we want to split but risk duplication. Better to follow: Requirements (education), Qualifications (the list). Benefits.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check if any Pay or Schedule: none, so omit.
Now we need to format.
About the role: combine mission and opportunity description into prose.
Responsibilities: list each duty from "What You'll Do In The Role". Let's extract bullet points:
- partner with our care team to build a world-class mobile experience to help patients manage chronic illness.
- Create an initial first impression that delights our patients, leading to success is achieving our enrollment goals, while also focusing on building the right windows into the metrics that matter so we can experiment rapidly.
- Improve both internal and external user experiences in addition to business processes, by integrating with modern services via third-party APIs.
- Leverage Google Cloud Platform services to architect, build, and deploy scalable and robust backend systems that support new features and functionaly.
- Collaborate closely with data analysts and engineers to improve reporting and analytics insights, while also optimizing the user experience and automating decision-making processes.
- Practice continuous integration and deployment to minimize feedback cycles.
- Decide when to sprint and when to be deliberate in your software engineering practices.
- Continuously improve our toolset to make future development easier.
We need to preserve all substantive information; do not invent or summarize away detail. So we keep each as list item.
Requirements: "Bachelor’s degree in Computer Science, Engineering, or related field preferred."
Qualifications: list of attributes:
- “Patient first” attitude: Ability to design and evaluate tools and experiences through a patient-first lens, with a strong instinct for usability, empathy, and quality that leads to “wow” experiences.
- Metric-Driven Engineering & Decision Making: Skilled in defining success metrics upfront and using data to guide technical decisions, prioritize work, and iterate quickly based on outcomes and feedback.
- Systems & Integration Expertise: Proven ability to design, build, and maintain integrations across complex systems, databases, and third-party APIs, ensuring reliable data flow and cohesive end-to-end experiences.
- Cross-Functional Collaboration: Strong communicator and partner who works effectively with Product, Care, and Enrollment teams to align technical solutions with real-world operational and patient needs.
- Growth Mindset & Craft Orientation: Demonstrates genuine passion for building, continuous learning, and improving one’s craft—motivated by impact, ownership, and the desire to improve patient care through technology.
We need to keep the quotes? Probably keep as is.
Benefits: "Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more." Also earlier sentences about fun environment etc. Those are also benefits? They are more about culture. Could include them as part of Benefits section? The instruction: Benefits section only if posting actually states them. The posting includes "Here's What We'd Like To Offer You" with several bullet-like sentences: Equal investment and support for our people and patients. A fun and ambitious start-up environment with a culture that takes on important things, takes risks, and learns quickly. The ability to demonstrate creativity, innovation, and conscientiousness, and find joy in working together. A team of highly skilled, incredibly kind, and welcoming employees, every one of whom has something unique to offer. We know that the overall success of our business is a collaborative effort, and we strive to provide ongoing opportunities for our employees to learn and grow, both personally and professionally. Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more.
Thus we can include all those as benefits. So Benefits section will have a list of items: Equal investment and support for our people and patients; A fun and ambitious start-up environment with a culture that takes on important things, takes risks, and learns quickly; The ability to demonstrate creativity, innovation, and conscientiousness, and find joy in working together; A team of highly skilled, incredibly kind, and welcoming employees, every one of whom has something unique to offer; Ongoing opportunities for employees to learn and grow, both personally and professionally; Full-time employees are eligible to participate in our benefits package which includes Medical, Dental, Vision Insurance, Paid time off, Short- and Long-Term Disability, and more.
We should not include boilerplate EEO etc.
Now produce HTML fragment:
About the role
AndHealth is on a mission to radically improve access and outcomes for the most challenging chronic health conditions, with the goal of making world-class specialty care accessible and affordable to all. We partner with health systems, community health centers, and independent practices to remove barriers to care to ensure all people have access to the care they deserve. The Opportunity We are looking for a Software Engineer to join our team to build a world-class patient experience through the AndHealth mobile, web and desktop applications, while also ensuring the privacy and security of our patients’ data. In this role, you’ll work across the entire software development lifecycle and work collaboratively with our Product and Care teams to build and deliver an excellent patient experience. Both the company and the Product & Engineering team are on a path of significant growth. We're looking for someone who is excited about growing with us by contributing to the company’s success while also pursuing personal and professional development. The role may start with gaining comfort with the tech stack (mainly Flutter & GCP) by developing tweaks and bug fixes, and over time grow into more significant feature development.
But note: The instruction says 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 shortor drop it. That's fine. We need to ensure we don't include any navigation etc. Now Responsibilities:
Responsibilities
- partner with our care team to build a world-class mobile experience to help patients manage chronic illness.
- Create an initial first impression that delights our patients, leading to success is achieving our enrollment goals, while also focusing on building the right windows into the metrics that matter so we can experiment rapidly.
- Improve both internal and external user experiences in addition to business processes, by integrating with modern services via third-party APIs.
- Leverage Google Cloud Platform services to architect, build, and deploy scalable and robust backend systems that support new features and functionaly.
- Collaborate closely with data analysts and engineers to improve reporting and analytics insights, while also optimizing the user experience and automating decision-making processes.
- Practice continuous integration and deployment to minimize feedback cycles.
- Decide when to sprint and when to be deliberate in your software engineering practices.
- Continuously improve our toolset to make future development easier.
Requirements
Bachelor’s degree in Computer Science, Engineering, or related field preferred.
Qualifications:Qualifications
- “Patient first” attitude: Ability to design and evaluate tools and experiences through a patient-first lens, with a strong instinct for usability, empathy, and quality that leads to “wow” experiences.
- Metric-Driven Engineering & Decision Making: Skilled in defining success metrics upfront and using data to guide technical decisions, prioritize work, and iterate quickly based on outcomes and feedback.
- Systems & Integration Expertise: Proven ability to design, build, and maintain integrations across complex systems, databases, and third-party APIs, ensuring reliable data flow and cohesive end-to-end experiences.
- Cross-Functional Collaboration: Strong communicator and partner who works effectively with Product, Care, and Enrollment teams to align technical solutions with real-world operational and patient needs.
- Growth Mindset & Craft Orientation: Demonstrates genuine passion for building, continuous learning, and improving one’s craft—motivated by impact, ownership, and the desire to improve patient care through technology.
Benefits
- Equal investment and support for our people and patients.
- A fun and ambitious start-up environment with a culture that takes on important things, takes risks, and learns quickly.
- The ability to demonstrate creativity, innovation, and conscientiousness, and find joy in working together.
- A team of highly skilled, incredibly kind, and welcoming employees, every one of whom has something unique to offer.
- Ongoing opportunities for employees to learn and grow,