Diversity, Equity, and Inclusion

Awell is fully committed to ensuring fair and equal treatment of all employees, job applicants, customers and potential customers:

• We expect all people to have an equal opportunity for employment and advancement on the basis of ability, necessary qualifications and fitness for work irrespective of sex, age, gender reassignment, disability, marital status, civil partnership, sexual orientation, color, race, creed, religion, national or ethnic origin. As an equal opportunities employer, we recognize that diversity is a positive attribute and we understand and welcome the differences that a diverse culture brings.

• We value openness, accessibility, fairness and transparency.

• We will avoid unlawful discrimination in all areas of employment, including recruitment, promotion, training, discipline, redundancy and pay and benefits.

• Employees who become disabled will be given every reasonable and practicable consideration and opportunity to help them remain in employment.

Introduction

Awell is a technology company active in healthcare building the best CareOps platform in the world. We exist because we want to have a positive impact on the lives of patients & care teams. Don’t trust our word for it, have a look at the https://awellhealth.atlassian.net/wiki/spaces/AH and find out for yourself.

To get you going:

• https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3499655169

• (company) and

Our customers are care providers who want to better leverage the work of their care teams (our mission is to “make care flows work harder than care teams”). They both use our software and build on top of our software in order to achieve their goals of better and more efficient patient care.

We are a team of ~20 people, globally distributed, serving customers in Europe and the US. We are backed by Octopus Ventures, S16, LocalGlobe, Moonfire, and other investors. Having recently closed our seed round, we are in the fortunate position of having meaningful runway. We are looking for open-minded people who are committed to continuously improving themselves and the world around them. Our culture is one of responsibility, high productivity, and genuine feedback.

About the role

This role is a fully-remote position.

Here’s a glimpse at some of the product and technical challenges we’ll likely be solving over the next 6-12 months:

EHR Integrations and data

In order to effectively integrate with care operations professionals, it’s important our customers care flows feed back into their systems of record. If you’ve done it before, you know the devil is in the details . We’re looking to leverage the wisdom of a battle-hardened integrations wizard along with new advancements in AI to move quickly and efficiently with EHR integrations.

We have also begun working with some of the FHIR data types but have not yet implemented a FHIR datastore. If you’re coming with previous experience in interoperability (a big plus), then you would likely own this system.

Bootcamps and solutions engineering

Customer contracts are very large, and one of the biggest hurdles we want to continue to solve as a company is reducing our “time-to-publish” metric, which measures the time from our first conversation all the way until the customer publishes the first care flow. One of our great learnings has been the power of a bootcamp, where one or more members of the product development team will travel to our customers' locations and actually build and integrate with them.

This bootcamp usually involves building custom integrations (e.g. connect to a proprietary API), working with our product (dogfooding), and always results with incredible insights that can be piped back to the team and used to help inform future feature development.

Performance and SLAs

A current project to revamp our orchestration domain means you’ll likely own a subsystem inside of orchestration. That might be something event-based such as triggers, rules, scheduling, data ingestion, core orchestration; or something callable like data points, activities, care flows, or our orchestration graph. Whatever it is, you’ll be expected to maintain SLAs for those sub-systems. You’ll also be responsible for maintaining whatever interfaces are necessary for either design or orchestration.

Event-sourcing & CQRS

You’ll be working with an event store, snapshots, and aggregates. In design, where we’ve already implemented event-sourcing/CQRS, users of our studio will expect changes to propagate quickly to the UI. In orchestration, it will be important to be able to rewind and replay a care flow. You may be called upon to help implement parts of this system as we implement it in the second half of this year.

Orchestrating care flows at scale

There is some important work we’ve recently begun and will be continuing likely through all of Q2. Building for scalability is incredibly important on the path toward one million monthly active patients (MAPs - patients enrolled in a care flow over the last month) and beyond. You’ll either be a contributor during this project or will become a beneficiary of it. You’ll want to grok the scalability of our individual subsystems and where bottlenecks are so you can help to contribute toward whichever SLAs you are responsible for.

Other information

As an early member of the team, you will have an opportunity to shape our culture, and to grow as Awell grows. We expect you’ll learn a lot working here. You’ll take part in our bi-weekly SODOTO sessions (“see one, do one, teach one”) and knowledge-share with teammates; you’ll hack away at problems during one of our quarterly hackathons; you’ll meet everybody in person during one of our (spoiler alert, our next offsite is coming up in April and is in Istanbul, Turkey); you’ll perform discovery on new features; you’ll learn about Awell’s customers and the problems they’re looking to solve.

Our goal is that when you decide to move on from your journey with Awell, you’ll look back fondly at your time knowing it was very well spent, you’ll have made some great colleagues and/or friends, and you’ll feel a drive to “pay it forward” and coach others so they can also find fulfillment in their work the way you did.

Finally, as a software engineer, there might be some additional pages in the that might be of interest to you:

Responsibilities

Here’s the scope of a P4 (stolen from engineeringladders.com and modified to our levels and needs)

• Lead projects, help your team to clear the uphill work as early as possible

• Use code reviews to up-level your team, insist on growing your team’s test suite so continuous delivery can turn into continuous deployment

• Work with customers, understand their problems, and use your knowledge to help shape future product work

• Regularly contribute to our SODOTOs (held bi-weekly), helping to boost the knowledge and skills of the rest of the team

• Provide feedback often

Requirements / Background

You have been considered a leader by your peers in a strong engineering organization, raising the bar for your teammates and helping to define what it means to be a strong engineer. You have perhaps been part of a complex initiative or have even led teams doing this kind of high-impact, complicated work. You are insatiably curious.

You are very comfortable working in React and have likely followed Next into 13+, for either production or personal projects. You’ve operated comfortably in backend systems. You have strong Typescript chops and system design experience.

• What we do at Awell, our company , and resonate with you.

• You have a strong sense of ownership & autonomy.

• You love solving hard problems and are not afraid of a challenge.

• You understand that criticism should be kind and clear, while praise should be specific and sincere.

Tech Stack

You do not have to be an expert in each of these areas, but it's important you are able to communicate to us your strengths, weaknesses, and desired areas of growth:

• Frontend frameworks: React + NextJS

• UI Prototyping, Testing and Review: Figma, Storybook, Chromatic

• API: Express, GraphQL / Apollo

• Backend: GCP, Typescript/Node.js, Moleculer.js (microservices), ArangoDB (graph), Redis, BigQuery

• Architecture / patterns: Event-driven, event sourcing & CQRS, message queues, borrowing quite a bit from DDD

Benefits & Logistics

• A competitive salary (California and New York residents: $155,000 - $211,000, based on equity election and metropolitan area)

• Yearly learning and development stipend

• Strong growth opportunities (as we’re still relatively small but expanding fast)

• Equity

• ⏱️ Flexible work hours

• 🛫 Flexible vacation policy (see )

• Your choice of computing equipment

• The chance to work with amazing and join our amazing

Location

We’re a fully remote team so this is a remote position.

How to apply

Send your application to jonathan@awellhealth.com

Interview process

You can find more information about our interview process on .