Senior Software Engineer
Atlas Medical Data Group · United States
FULL-TIME
Posted Nov 15, 2026
Job Description
About Atlas Medical Data Group
We are a founder-owned portfolio of healthcare businesses. The anchor is a healthcare price intelligence company that processes the price transparency files insurers are required to publish. These files disclose the rates they have negotiated with providers but are so massive and messy that almost no one can use them. We build the technology to turn the raw data into price intelligence, which has powerful applications across the US healthcare landscape.
One of the first applications is in care delivery. The data shows us which clinics have room to negotiate better rates on their commercial contracts. We buy or partner with those clinics, help them win those rates, and run their back office through our management services organization. This year we acquired the first one, a multi-site autism therapy (ABA) practice.
About the role
We are hiring a senior software engineer to build and run the applications that power our growing autism therapy (ABA) platform: the practices we operate and the management services organization (MSO) that provides them with their non-clinical operations. The role sits with the operations team and works directly with the people who run the practices on real workflow problems: referrals and intake, authorizations, scheduling, billing and collections, and the reporting that runs on top of them.
The platform is built to grow. We expect to bring additional ABA practices into the portfolio and to offer the MSO's services to practices outside it. The applications this person builds are meant to run across many practices, not one.
Our practices provide ABA therapy to children with autism and their families. The software available to ABA practices is poor, and the cost of that lands on clinicians, who spend time on administration that should go to clients, and on families, who wait longer to get into care. Better tools change both.
Why this role exists
The off-the-shelf software available to ABA practices (practice management, claims, scheduling) does not serve them well. We intend to replace or supplement those systems with purpose-built tools, using AI tooling and open source where it fits, rather than keep configuring vendor software. The goal is software, built with our clinical and operations team, that is better than the commercial products ABA practices pay for today.
The MSO will provide billing, credentialing, scheduling, finance, and reporting services to our practices and to others that join the portfolio. The applications and data that support those services are being built now, and the design has to anticipate more than one organization.
What you will do
Build applications end to end: understand the operational problem with the people who do the work, design the solution, build the data model, back end, and front end, deploy it, and support it in production.
Work the practice's core workflow one capability at a time, following the client journey with priority going to the current pain points: outreach and referral management, intake and benefits verification, authorizations, clinic scheduling (a first application is already in place), session documentation through to claims, billing, payment posting, and collections, and operational reporting over each of the above.
Automate manual and repetitive operational work where a purpose-built tool, a script, or an AI-enabled workflow does the job better than the current system.
Build on our open-source ERP, which is the one fixed point in the platform. The practice management, claims, and scheduling software around it is poor, and much of the work is replacing it. Until a replacement is in place, you integrate with what is there.
Build on the established platform: deploy following the patterns in place, write deployment scripts and small infrastructure changes when needed, and contribute to the data warehouse as applications create or consume data.
Build with AI as a core part of how you work, and keep finding better ways to do it as the tools change. Build applications that make use of AI where it adds something for the operators.
Run the product side of what you build. You work directly with the operators and with company leadership to draw out requirements, shape what gets built and in what order, and put working software in front of them early. The business sets the priorities; you own turning them into a product that works.
Who we are looking for
A senior full-stack software engineer. Comfortable across data, back end, front end, and deployment. Real depth in at least one area and working competence in the rest. Which languages and frameworks you have used matters less than how well you build.
Exposure to data engineering or data warehousing is a plus.
6 or more years building and shipping software, with a record of owning and running production systems and of staying in a role long enough to grow in it and to live with the decisions made there.
Has shipped applications that real users depend on and has supported them after launch.
A self-starter. Faced with an unfamiliar system or problem, you dig in and work it out without being told how.
Works well with ambiguity. Can take a loosely defined operational problem, ask the right questions of the people doing the work, and get to a usable first version quickly.
Biases toward getting a working tool into the hands of the business and improving it from there, rather than building the complete version before anyone sees it.
AI-forward. You develop with AI every day, you keep changing how you work as the tools improve, and you can show what that looks like in your own work.
Communicates clearly and directly with non-technical people. You will be working with clinic operators and company leadership, not picking up tickets.
Healthcare, revenue cycle, or ABA experience is helpful but not required. Experience working with healthcare data or protected health information under HIPAA is preferred. Willingness to learn the domain by sitting with the operators matters more.
Comfortable working remotely with a small, distributed team and communicating clearly in writing.
A public GitHub profile, open source work, or a portfolio of things you have built is a plus. Include a link if you have one.
What the role offers
You own what you build end to end, from the first conversation with the operators through design, build, deployment, and support. There is no hand-off to another team.
You ship to real users on short cycles. The people using what you build are a few steps away, and feedback comes back the same week.
You have real say in the technology. We favor open source, and the open-source ERP at the center of our platform is settled. Most of what gets built on and around it, including frameworks, tooling, and the architecture of new applications, is yours to shape.
We are an AI-forward team, and how we build software keeps changing. If that is the work you want to be doing, you will have the room and the company to do it.
The role grows with the business. As the portfolio adds practices and the engineering footprint grows with it, the person in this seat is positioned to lead that work.
What is hard about it
Small team. You will be the engineer on most of what you build, and there is no larger engineering organization behind you to lean on.
Healthcare. The applications handle protected health information, and HIPAA and payer requirements constrain how things get built, deployed, and accessed.
Vendor systems. The practice management, claims, and payer systems our practices use today are poor and will not go away all at once. Some of the work is living with them and integrating around them while replacements get built.
Ambiguity. Requirements come from operators describing their work, not from a product team with written specs. Part of the job is doing that translation yourself.
Technical environment
Applications have been deployed on Azure Container Apps so far, and we expect to follow established or emerging patterns as we stand up and expand the technical capabilities and infrastructure.
Data warehouse on Azure; multi-organization support still to be designed.
A Python-based open-source ERP as the ERP and finance platform and a base for new applications. We prefer open source and build on it where we can.
Existing clinic scheduling application as the reference pattern for build and deploy.
Languages and frameworks are not fixed. Existing code is largely Python (data engineering, the scheduling app, and the ERP), and choices for new applications are at the engineer's discretion based on what is being built.
AI developer tooling (Claude Code or equivalent) in daily use.
Logistics
Location: remote, US-based.
Work authorization: you must be authorized to work in the United States. We are not able to sponsor work visas for this role.
Employment type: full-time employee. This is a long-term, direct-hire role, and that is where we want to end up. If you are not in a role right now, or are otherwise free to start right away, we are glad to begin with a short paid contract. Working together is the fastest way for both sides to decide, and it shortens our process considerably.
We are a founder-owned portfolio of healthcare businesses. The anchor is a healthcare price intelligence company that processes the price transparency files insurers are required to publish. These files disclose the rates they have negotiated with providers but are so massive and messy that almost no one can use them. We build the technology to turn the raw data into price intelligence, which has powerful applications across the US healthcare landscape.
One of the first applications is in care delivery. The data shows us which clinics have room to negotiate better rates on their commercial contracts. We buy or partner with those clinics, help them win those rates, and run their back office through our management services organization. This year we acquired the first one, a multi-site autism therapy (ABA) practice.
About the role
We are hiring a senior software engineer to build and run the applications that power our growing autism therapy (ABA) platform: the practices we operate and the management services organization (MSO) that provides them with their non-clinical operations. The role sits with the operations team and works directly with the people who run the practices on real workflow problems: referrals and intake, authorizations, scheduling, billing and collections, and the reporting that runs on top of them.
The platform is built to grow. We expect to bring additional ABA practices into the portfolio and to offer the MSO's services to practices outside it. The applications this person builds are meant to run across many practices, not one.
Our practices provide ABA therapy to children with autism and their families. The software available to ABA practices is poor, and the cost of that lands on clinicians, who spend time on administration that should go to clients, and on families, who wait longer to get into care. Better tools change both.
Why this role exists
The off-the-shelf software available to ABA practices (practice management, claims, scheduling) does not serve them well. We intend to replace or supplement those systems with purpose-built tools, using AI tooling and open source where it fits, rather than keep configuring vendor software. The goal is software, built with our clinical and operations team, that is better than the commercial products ABA practices pay for today.
The MSO will provide billing, credentialing, scheduling, finance, and reporting services to our practices and to others that join the portfolio. The applications and data that support those services are being built now, and the design has to anticipate more than one organization.
What you will do
Build applications end to end: understand the operational problem with the people who do the work, design the solution, build the data model, back end, and front end, deploy it, and support it in production.
Work the practice's core workflow one capability at a time, following the client journey with priority going to the current pain points: outreach and referral management, intake and benefits verification, authorizations, clinic scheduling (a first application is already in place), session documentation through to claims, billing, payment posting, and collections, and operational reporting over each of the above.
Automate manual and repetitive operational work where a purpose-built tool, a script, or an AI-enabled workflow does the job better than the current system.
Build on our open-source ERP, which is the one fixed point in the platform. The practice management, claims, and scheduling software around it is poor, and much of the work is replacing it. Until a replacement is in place, you integrate with what is there.
Build on the established platform: deploy following the patterns in place, write deployment scripts and small infrastructure changes when needed, and contribute to the data warehouse as applications create or consume data.
Build with AI as a core part of how you work, and keep finding better ways to do it as the tools change. Build applications that make use of AI where it adds something for the operators.
Run the product side of what you build. You work directly with the operators and with company leadership to draw out requirements, shape what gets built and in what order, and put working software in front of them early. The business sets the priorities; you own turning them into a product that works.
Who we are looking for
A senior full-stack software engineer. Comfortable across data, back end, front end, and deployment. Real depth in at least one area and working competence in the rest. Which languages and frameworks you have used matters less than how well you build.
Exposure to data engineering or data warehousing is a plus.
6 or more years building and shipping software, with a record of owning and running production systems and of staying in a role long enough to grow in it and to live with the decisions made there.
Has shipped applications that real users depend on and has supported them after launch.
A self-starter. Faced with an unfamiliar system or problem, you dig in and work it out without being told how.
Works well with ambiguity. Can take a loosely defined operational problem, ask the right questions of the people doing the work, and get to a usable first version quickly.
Biases toward getting a working tool into the hands of the business and improving it from there, rather than building the complete version before anyone sees it.
AI-forward. You develop with AI every day, you keep changing how you work as the tools improve, and you can show what that looks like in your own work.
Communicates clearly and directly with non-technical people. You will be working with clinic operators and company leadership, not picking up tickets.
Healthcare, revenue cycle, or ABA experience is helpful but not required. Experience working with healthcare data or protected health information under HIPAA is preferred. Willingness to learn the domain by sitting with the operators matters more.
Comfortable working remotely with a small, distributed team and communicating clearly in writing.
A public GitHub profile, open source work, or a portfolio of things you have built is a plus. Include a link if you have one.
What the role offers
You own what you build end to end, from the first conversation with the operators through design, build, deployment, and support. There is no hand-off to another team.
You ship to real users on short cycles. The people using what you build are a few steps away, and feedback comes back the same week.
You have real say in the technology. We favor open source, and the open-source ERP at the center of our platform is settled. Most of what gets built on and around it, including frameworks, tooling, and the architecture of new applications, is yours to shape.
We are an AI-forward team, and how we build software keeps changing. If that is the work you want to be doing, you will have the room and the company to do it.
The role grows with the business. As the portfolio adds practices and the engineering footprint grows with it, the person in this seat is positioned to lead that work.
What is hard about it
Small team. You will be the engineer on most of what you build, and there is no larger engineering organization behind you to lean on.
Healthcare. The applications handle protected health information, and HIPAA and payer requirements constrain how things get built, deployed, and accessed.
Vendor systems. The practice management, claims, and payer systems our practices use today are poor and will not go away all at once. Some of the work is living with them and integrating around them while replacements get built.
Ambiguity. Requirements come from operators describing their work, not from a product team with written specs. Part of the job is doing that translation yourself.
Technical environment
Applications have been deployed on Azure Container Apps so far, and we expect to follow established or emerging patterns as we stand up and expand the technical capabilities and infrastructure.
Data warehouse on Azure; multi-organization support still to be designed.
A Python-based open-source ERP as the ERP and finance platform and a base for new applications. We prefer open source and build on it where we can.
Existing clinic scheduling application as the reference pattern for build and deploy.
Languages and frameworks are not fixed. Existing code is largely Python (data engineering, the scheduling app, and the ERP), and choices for new applications are at the engineer's discretion based on what is being built.
AI developer tooling (Claude Code or equivalent) in daily use.
Logistics
Location: remote, US-based.
Work authorization: you must be authorized to work in the United States. We are not able to sponsor work visas for this role.
Employment type: full-time employee. This is a long-term, direct-hire role, and that is where we want to end up. If you are not in a role right now, or are otherwise free to start right away, we are glad to begin with a short paid contract. Working together is the fastest way for both sides to decide, and it shortens our process considerably.
Additional Details
- City
- United States
- Country
- US
Apply and matching require a free OVN account. Browse listings anytime without signing in.