Senior Software Engineer, Patient Conversions
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Learn more about our culture and benefits here: athenahealth.com/careers https://www.athenahealth.com/careers/equal-opportunity". Also remove "Our vision..."? That's part of about athenahealth; we can keep substantive content.
We need to include sections only when posting has real specific content. So we will have sections: About the role (role summary + team summary?), Responsibilities (essential + additional?), Requirements (expected education & experience), Pay (expected compensation), Benefits (what we can do for you), maybe About Athenahealth as a section? Could be "About the company" but not in list; but we could treat as "About Athenahealth" as a section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Probably we should stick to those headings where applicable. We have role summary, team summary, responsibilities, education/experience, compensation, benefits. Could also have "About Athenahealth" as a section but not in list; maybe we can incorporate into "About the role" or omit. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we could also use other headings if needed, but better to stick to those. So we can have:
About the role
containing role summary and team summary.
Responsibilities
containing essential and additional responsibilities (maybe combine).
Requirements
containing expected education & experience.
Pay
containing expected compensation.
Benefits
containing what we can do for you (benefits/perks).
We should not include Schedule as not present.
We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like technologies, etc.
We need to format lists with - . For prose use
.
We must not repeat job title. No markdown.
Let's extract content.
Role Summary: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. Role Summary The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager."
Team Summary: "Team Summary Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale."
We can combine into About the role section.
Responsibilities: Essential Job Responsibilities list (multiple sentences). Additional Job Responsibilities list.
We need to turn each bullet into
- . The text currently is sentences separated by periods. We'll split each sentence as a list item.
Essential responsibilities:
- Develop and maintain full stack features using React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, HAPI FHIR, Gradle, and athenahealth’s Forge design system.
- Build user-facing experiences and service APIs that support patient communication workflows across SMS, secure web chat, and voice-enabled experiences.
- Design and implement scalable backend services, event-driven workflows, and integrations that support reliable conversation handling and data exchange.
- Collaborate with product, design, architecture, and quality engineering to translate requirements into well-structured technical solutions.
- Write clean, testable, well-documented code and participate in code reviews, design reviews, and troubleshooting.
- Improve application performance, reliability, observability, and maintainability across the full stack.
- Support secure handling of healthcare data and apply sound engineering practices for privacy, access control, and compliance requirements.
- Use AI tools and AI-assisted workflows to improve engineering productivity, evaluate outputs critically, and apply judgment when incorporating AI-generated suggestions into code, design, or troubleshooting.
- Contribute to technical discussions and help identify practical implementation patterns for new product capabilities and platform enhancements.
Additional responsibilities:
- Support production issue investigation and root-cause analysis when needed.
- Participate in release planning, deployment readiness, and post-release validation.
- Help refine engineering standards, coding conventions, and reusable patterns.
- Contribute to documentation for technical design, APIs, and system behavior.
- Assist with mentoring peers through code reviews, pairing, and knowledge sharing.
- Participate in cross-functional discussions to help clarify requirements and implementation tradeoffs.
- Support continuous improvement of engineering processes, tooling, and developer experience.
Expected Education & Experience: list each bullet.
- Bachelor’s degree in Computer Science, Software Engineering, or a related field, or equivalent practical experience.
- 4 to 8 years of software development experience building production applications.
- Experience developing modern front-end applications with React and TypeScript.
- Experience building production-grade backend services with Java and Spring Boot.
- Experience with Kafka or similar event streaming / messaging systems.
- Experience working with PostgreSQL or similar relational databases.
- Experience integrating with healthcare interoperability standards or APIs, including HAPI FHIR.
- Experience using build tooling such as Gradle.
- Experience working with a design system, including Forge or similar reusable component libraries.
- Experience designing and delivering full stack features in a collaborative product engineering environment.
- Experience writing automated tests and supporting code quality, reliability, and maintainability.
- Understanding of secure software development practices in regulated or data-sensitive environments.
- Familiarity with API design, service-to-service communication, and operational debugging.
- Experience working on systems that require clear documentation and cross-functional coordination.
Pay: Expected Compensation $113,000 - $193,000 plus description.
We need to keep the description: "The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, including job-related experience, relevant knowledge and skills, how your qualifications compare to others in similar roles, and geographical market rates. Base pay is only one part of our competitive Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans."
We'll put that in
after maybe a
? It's prose.
Benefits: "What We Can Do For You Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs. We also encourage a better work-life balance for athenistas with our flexibility. While we know in-office collaboration is critical to our vision, we recognize that not all work needs to be done within an office environment, full-time. With consistent communication and digital collaboration tools, athenahealth enables employees to find a balance that feels fulfilling and productive for each individual situation. In addition to our traditional benefits and perks, we sponsor events throughout the year, including book clubs, external speakers, and hackathons. We provide athenistas with a company culture based on learning, the support of an engaged team, and an inclusive environment where all employees are valued."
We can turn some into list: perks list: commuter support, employee assistance programs, tuition assistance, employee resource groups, collaborative workspaces (some offices even welcome dogs). Also events: book clubs, external speakers, hackathons. Also flexibility, learning culture, etc. We'll keep as prose maybe but better to list.
We'll create - for each distinct perk.
We must not include boilerplate like "Learn more about our culture and benefits here: athenahealth.com/careers https://www.athenahealth.com/careers/equal-opportunity". Remove.
Also remove "Our vision..."? That's part of about athenahealth but we didn't include a section for that. Could include in About the role? Actually the opening sentence "Join us as we work to create a thriving ecosystem..." is part of the intro; we can keep that in About the role section as prose.
Now produce HTML fragment.
Structure:
About the role
Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager.
Team Summary: Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale.
Then Responsibilities:
Responsibilities
- ...
...
We need to split essential and additional? Could combine into one list but maybe better to keep separate headings? Not required. We'll just list all responsibilities.
Then Requirements:
Requirements
- ...
...
Pay:
Pay
$113,000 - $193,000 base salary range. The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, including job-related experience, relevant knowledge and skills, how your qualifications compare to others in similar roles, and geographical market rates. Base pay is only one part of our competitive Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans.
Benefits:
Benefits
- Health and financial benefits
- Commuter support
- Employee assistance programs
- Tuition assistance
- Employee resource groups
- Collaborative workspaces (some offices welcome dogs)
- Flexibility for work‑life balance
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we could also use other headings if needed, but better to stick to those. So we can have:
About the role
containing role summary and team summary.
Responsibilities
containing essential and additional responsibilities (maybe combine).
Requirements
containing expected education & experience.
Pay
containing expected compensation.
Benefits
containing what we can do for you (benefits/perks).
We should not include Schedule as not present.
We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like technologies, etc.
We need to format lists with - . For prose use
.
We must not repeat job title. No markdown.
Let's extract content.
Role Summary: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. Role Summary The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager."
Team Summary: "Team Summary Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale."
We can combine into About the role section.
Responsibilities: Essential Job Responsibilities list (multiple sentences). Additional Job Responsibilities list.
We need to turn each bullet into
- . The text currently is sentences separated by periods. We'll split each sentence as a list item.
Essential responsibilities:
- Develop and maintain full stack features using React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, HAPI FHIR, Gradle, and athenahealth’s Forge design system.
- Build user-facing experiences and service APIs that support patient communication workflows across SMS, secure web chat, and voice-enabled experiences.
- Design and implement scalable backend services, event-driven workflows, and integrations that support reliable conversation handling and data exchange.
- Collaborate with product, design, architecture, and quality engineering to translate requirements into well-structured technical solutions.
- Write clean, testable, well-documented code and participate in code reviews, design reviews, and troubleshooting.
- Improve application performance, reliability, observability, and maintainability across the full stack.
- Support secure handling of healthcare data and apply sound engineering practices for privacy, access control, and compliance requirements.
- Use AI tools and AI-assisted workflows to improve engineering productivity, evaluate outputs critically, and apply judgment when incorporating AI-generated suggestions into code, design, or troubleshooting.
- Contribute to technical discussions and help identify practical implementation patterns for new product capabilities and platform enhancements.
Additional responsibilities:
- Support production issue investigation and root-cause analysis when needed.
- Participate in release planning, deployment readiness, and post-release validation.
- Help refine engineering standards, coding conventions, and reusable patterns.
- Contribute to documentation for technical design, APIs, and system behavior.
- Assist with mentoring peers through code reviews, pairing, and knowledge sharing.
- Participate in cross-functional discussions to help clarify requirements and implementation tradeoffs.
- Support continuous improvement of engineering processes, tooling, and developer experience.
Expected Education & Experience: list each bullet.
- Bachelor’s degree in Computer Science, Software Engineering, or a related field, or equivalent practical experience.
- 4 to 8 years of software development experience building production applications.
- Experience developing modern front-end applications with React and TypeScript.
- Experience building production-grade backend services with Java and Spring Boot.
- Experience with Kafka or similar event streaming / messaging systems.
- Experience working with PostgreSQL or similar relational databases.
- Experience integrating with healthcare interoperability standards or APIs, including HAPI FHIR.
- Experience using build tooling such as Gradle.
- Experience working with a design system, including Forge or similar reusable component libraries.
- Experience designing and delivering full stack features in a collaborative product engineering environment.
- Experience writing automated tests and supporting code quality, reliability, and maintainability.
- Understanding of secure software development practices in regulated or data-sensitive environments.
- Familiarity with API design, service-to-service communication, and operational debugging.
- Experience working on systems that require clear documentation and cross-functional coordination.
Pay: Expected Compensation $113,000 - $193,000 plus description.
We need to keep the description: "The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, including job-related experience, relevant knowledge and skills, how your qualifications compare to others in similar roles, and geographical market rates. Base pay is only one part of our competitive Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans."
We'll put that in
after maybe a
? It's prose.
Benefits: "What We Can Do For You Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs. We also encourage a better work-life balance for athenistas with our flexibility. While we know in-office collaboration is critical to our vision, we recognize that not all work needs to be done within an office environment, full-time. With consistent communication and digital collaboration tools, athenahealth enables employees to find a balance that feels fulfilling and productive for each individual situation. In addition to our traditional benefits and perks, we sponsor events throughout the year, including book clubs, external speakers, and hackathons. We provide athenistas with a company culture based on learning, the support of an engaged team, and an inclusive environment where all employees are valued."
We can turn some into list: perks list: commuter support, employee assistance programs, tuition assistance, employee resource groups, collaborative workspaces (some offices even welcome dogs). Also events: book clubs, external speakers, hackathons. Also flexibility, learning culture, etc. We'll keep as prose maybe but better to list.
We'll create - for each distinct perk.
We must not include boilerplate like "Learn more about our culture and benefits here: athenahealth.com/careers https://www.athenahealth.com/careers/equal-opportunity". Remove.
Also remove "Our vision..."? That's part of about athenahealth but we didn't include a section for that. Could include in About the role? Actually the opening sentence "Join us as we work to create a thriving ecosystem..." is part of the intro; we can keep that in About the role section as prose.
Now produce HTML fragment.
Structure:
About the role
Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager.
Team Summary: Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale.
Then Responsibilities:
Responsibilities
- ...
...
We need to split essential and additional? Could combine into one list but maybe better to keep separate headings? Not required. We'll just list all responsibilities.
Then Requirements:
Requirements
- ...
...
Pay:
Pay
$113,000 - $193,000 base salary range. The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, including job-related experience, relevant knowledge and skills, how your qualifications compare to others in similar roles, and geographical market rates. Base pay is only one part of our competitive Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans.
Benefits:
Benefits
- Health and financial benefits
- Commuter support
- Employee assistance programs
- Tuition assistance
- Employee resource groups
- Collaborative workspaces (some offices welcome dogs)
- Flexibility for work‑life balance
. We must not repeat job title. No markdown. Let's extract content. Role Summary: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. Role Summary The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager." Team Summary: "Team Summary Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale." We can combine into About the role section. Responsibilities: Essential Job Responsibilities list (multiple sentences). Additional Job Responsibilities list. We need to turn each bullet into
after maybe a
- ? It's prose.
Benefits: "What We Can Do For You Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs. We also encourage a better work-life balance for athenistas with our flexibility. While we know in-office collaboration is critical to our vision, we recognize that not all work needs to be done within an office environment, full-time. With consistent communication and digital collaboration tools, athenahealth enables employees to find a balance that feels fulfilling and productive for each individual situation. In addition to our traditional benefits and perks, we sponsor events throughout the year, including book clubs, external speakers, and hackathons. We provide athenistas with a company culture based on learning, the support of an engaged team, and an inclusive environment where all employees are valued."
We can turn some into list: perks list: commuter support, employee assistance programs, tuition assistance, employee resource groups, collaborative workspaces (some offices even welcome dogs). Also events: book clubs, external speakers, hackathons. Also flexibility, learning culture, etc. We'll keep as prose maybe but better to list.
We'll create
- for each distinct perk.
We must not include boilerplate like "Learn more about our culture and benefits here: athenahealth.com/careers https://www.athenahealth.com/careers/equal-opportunity". Remove.
Also remove "Our vision..."? That's part of about athenahealth but we didn't include a section for that. Could include in About the role? Actually the opening sentence "Join us as we work to create a thriving ecosystem..." is part of the intro; we can keep that in About the role section as prose.
Now produce HTML fragment.
Structure:
About the role
Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. The Senior Full Stack Developer designs and builds modern web and service-layer capabilities that support patient communication experiences at athenahealth. This role works from Austin, TX in a hybrid model and combines front-end and back-end engineering to deliver reliable, maintainable software across React, TypeScript, Java 21, Spring Boot, Kafka, PostgreSQL, and HAPI FHIR. The position reports to the Senior Engineering Manager.
Team Summary: Patient Conversations creates modern communication experiences that connect patients with their care teams through SMS, secure web chat, and voice channels. The team is building a strategic platform that supports real-world patient and practice workflows, including conversational support, escalation paths, and secure handoffs across channels. The SMS and secure web chat experiences are already in use, and voice is an important next step in the roadmap. This work spans product experiences, backend services, data handling, integrations, and operational reliability. You would join a small engineering team with a mix of front-end, back-end, and full-stack contributors, partnering closely with product, design, architecture, and quality engineering to deliver high-impact capabilities at scale.
Then Responsibilities:Responsibilities
- ... ...
Requirements
- ... ...
Pay
$113,000 - $193,000 base salary range. The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, including job-related experience, relevant knowledge and skills, how your qualifications compare to others in similar roles, and geographical market rates. Base pay is only one part of our competitive Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans.
Benefits:Benefits
- Health and financial benefits
- Commuter support
- Employee assistance programs
- Tuition assistance
- Employee resource groups
- Collaborative workspaces (some offices welcome dogs)
- Flexibility for work‑life balance