Full Stack Enginner

Who are we

In an industry where the focus should be on helping patients hear the voices of their loved ones, hearing care professionals spend too much of their time navigating disconnected software and administrative work. OpenHearing is changing that.

We are building the operating system for modern hearing care practices. Starting with conversational intelligence, we capture and understand what happens across the patient journey, helping hearing care teams to reduce time spent on documentation, coach their providers, spot missed opportunities, and make better decisions. OpenHearing is already live across 700+ clinics, has processed 200,000+ appointments and over 6 million minutes of conversations.

We were founded in 2025 by Kenneth and Raghav who met at Harvard Business School. Kenneth has spent more than five years in strategy and leadership roles across the hearing care industry and beyond, most recently at GN Group - the company behind ReSound and Jabra. Raghav has spent more than a decade building products and technology at Myntra and Jumbotail. We are backed by some of the most prominent names in hearing care and are a team of under ten people across the US and Bangalore.

The role and what would you own

Let's break the “roles and responsibilities” and “own” into 2 separate sections

Role

As one of the initial engineers in our early engineering team, you will be contributing across our conversational intelligence, OMS, automation layers. It can be either frontend, backend or building AI agents. You are going to be one of the key pillar in shaping up the engineering and companies culture

What you would actually do, week to week
Autonomously deliver beautiful & robust code with considerations on code structure design and scalability
Design, build, and maintain high-performance systems by keeping excellence, security, alerting and monitoring mechanisms forefront
Ensure system stability and reliability; participate in regular code and design reviews and team on-call rotation
Communicate effectively in an async manner with team members to share updates, discuss challenges, and propose solutions

The stack

• Backend - Java with Spring Boot
• Frontend - React & React Native(for app)
• Infra - AWS (RDS, WAF, Agent core, Strands, Bedrock, ECS, etc.,), Pulumi
• Others -Livekit, Deepgram

What ownership means in practice

Think about the restaurant owner who wakes up at 5:00 am to get the fresh produce from the market so that it enhances the taste of the dishes that he serves to the customers. He goes to bed at 11:00 pm or 12:00 at night because he needs to close the accounts, get the restaurant deep cleaned, and make everything ready for the next day.

He doesn't stop there. He becomes a server in the absence of a server. He becomes the chef in the absence of a chef. This is the level of ownership that we expect. Go above and beyond to meet our northstar

Think about the restaurant owner who wakes up at 5:00 am to get the fresh produce from the market so that it enhances the taste of the dishes that he serves to the customers. He goes to bed at 11:00 pm or 12:00 at night because he needs to close the accounts, get the restaurant deep cleaned, and make everything ready for the next day.

He doesn't stop there. He becomes a server in the absence of a server. He becomes the chef in the absence of a chef. This is the level of ownership that we expect. Go above and beyond to meet our northstar

Click here for JD