Full-stack engineer (P4 - senior/staff) - Remote
Company: Awell
Salary: $140,000 - $210,000
Posted on: April 11, 2024
Job Description
_Hi, all! Quick note: *_ I will be rejecting applications from applicants
without experience working with US healthcare data* _. If you do not have this
experience but you know of someone who does, please forward this posting to
them! In the future, Awell will have more generalized engineering positions
open._
### 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](https://awell.health/) is a **technology company** active in
healthcare building the best [CareOps](https://careops.org/) 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 [Awell
Handbook](https://awellhealth.atlassian.net/wiki/spaces/AH) and find out for
yourself.
**To get you going:**
* [Mission](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3499655169)
* [Vision](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3503783957) (company) and [Product Vision](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3499261987)
Our customers are tech-forward care providers who want to 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](https://octopusventures.com/),
[S16](https://s16vc.com/), [LocalGlobe](https://localglobe.vc/),
[Moonfire](https://www.moonfire.com/), and others, and having just 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 :smiling_imp:.
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.
Read about our [design](https://developers.awellhealth.com/awell-
studio/docs/getting-started/design-ontology) and
[orchestration](https://developers.awellhealth.com/awell-
orchestration/docs/getting-started/orchestration-ontology) ontologies
👉 **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](https://awellhealth.atlassian.net/wiki/spaces/AWELL/pages/3490185310)
sessions (“see one, do one, teach one”) and knowledge-share with teammates;
you’ll hack away at problems during one of our
[Offsites](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3511517185);
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
[Awell Handbook](https://awellhealth.atlassian.net/wiki/spaces/AH) that might
be of interest to you:
* [Engineering culture @ Awell](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3503620106)
* [Product Principles](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3499229614)
* [Our Take on Roadmaps](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3509518385)
### Responsibilities
Here's the scope of a P4 (borrowed from
[engineeringladders.com](https://engineeringladders.com)
**System**
Owns: owns the production operation and monitoring of the system and is aware
of its SLAs
**Technology**
Evangelizes: researches, creates proofs of concept and introduces new
technologies to the team
**Influence**
Multiple Teams: makes an impact not only his/her team but also on other teams
**People**
Mentors: mentors others to accelerate their career-growth and encourages them
to participate
**Process**
Challenges: challenges the team processes, looking for ways to improve them
**Business**
Initiates: proactively engages with customers and colleagues to improve
currently working processes
**Other responsibilities**
* Lead projects, help your team to clear the [uphill work](https://basecamp.com/shapeup/3.4-chapter-13#work-is-like-a-hill) 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, and you have strong Typescript chops, even some system
design experience.
* [What we do at Awell](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3499196421), our company [Values](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3503882307), and [How we roll](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3503816800) resonate with you.
* You have a strong **sense of ownership & autonomy**.
* You are a **team player** and understand that cross-functional teams yield superior results over individual efforts.
* **You love solving hard problems** and are not afraid of a challenge because healthcare is all about solving hard problems.
* You are a **clear communicator** , both written and verbal.
### 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** : 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
* 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 [Holidays](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3500900467))
* Your choice of computing equipment
* The chance to work with amazing people and join our amazing [Offsites](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3511517185/Offsites)
### Location
We’re a fully remote team so this is a remote position.
### Compensation
Our compensation policy is transparent and straight forward (really!). The
broad range is due to the broad range in levels.
### How to apply
Send your application to
[[email protected]](mailto:[email protected])
### Interview process
You can find more information about our interview process on
[Hiring](https://awellhealth.atlassian.net/wiki/spaces/AH/pages/3519578135).
Awell focuses on Mobile, SaaS, and Healthcare Services. Their company has
offices in Encinitas and Brussels. They have a small team that's between 11-50
employees.
You can view their website at <http://www.awellhealth.com>