Adarna Inc. is building Aura Clarus — a wearable health platform that turns raw signals from the body into something a person can actually understand and act on. It is hard, unglamorous, deeply technical work, and it is being done by a small team in San Francisco, California. This page explains how we work and what it is like to join us.
We would rather tell you the truth about the job than sell you a version of it you will resent in three months. So this page is written plainly, including the parts that are difficult.
1. What We Are Building
Aura Clarus is a wearable device and a set of apps across iOS, Android, macOS and Windows, backed by a cloud pipeline that processes a day of raw sensor data into meaningful wellness insight. The device reads pulse, heartbeat intervals, movement and skin temperature. The pipeline turns those into sleep, recovery, stress, readiness and long-term personal baselines.
It is a general wellness product, not a medical device — a distinction we take seriously in engineering and in how we describe what we do. We do not make claims we cannot stand behind.
2. How We Work
2.1 Small team, wide scope
We are a small company. Nobody here owns a narrow slice of a narrow problem. An engineer may touch firmware in the morning and a cloud pipeline in the afternoon. If you need a job with tightly drawn boundaries and a long approval chain, this is not that job. If you want to see your work reach a real person wearing a real device, it is.
2.2 Everything is written down
Our architecture, parameter definitions, derivation logic and deployment steps live in documentation in the repository, not in one person's head. This is deliberate. It is how a small team stays resilient when someone is ill, on leave, or has simply forgotten why a decision was made eight months ago. If you join, you will be expected to write things down.
2.3 Infrastructure is code
We do not make changes by hand in a console and hope they stick. Infrastructure is defined in code and deployed through a reviewed pipeline, so the running system always matches its definition. It is slower on the first day and far faster on every day after it.
2.4 Honest estimates
We would rather hear "this will take three weeks and here is why" than an optimistic number that quietly slips. Nobody is punished for a realistic estimate or for raising a problem early. Deadlines are real, but they are not more real than the truth.
3. What We Value
- Built with purpose. We build with purpose, not just for profit. Every decision, every component, has meaning.
- Data and empathy. Data and empathy drive every decision. We monitor what matters — heartbeat by heartbeat — and remember there is a person on the other end of the number.
- Big vision, grounded action. We envision a world where health belongs to everyone, and we get there through unglamorous, careful work.
- Genuine care. We care deeply, without any agenda. Every decision starts with a simple question — does this truly help someone?
- Precision over noise. In a category full of overstatement, we would rather ship a smaller claim that is true than a louder one that is not.
4. Working With Health Data
Everyone here works, directly or indirectly, with sensitive health data. That carries obligations that are not negotiable: data is minimised, encrypted, access-controlled, and never sold. We design so that the smallest number of systems and people can reach personal data, and we treat a privacy shortcut as a defect, not a trade-off.
If you join an engineering role, you will be expected to understand why a feature that would be convenient is sometimes the wrong thing to build.
5. Where We Work
Our registered office is in San Francisco, California, and hardware work is inherently physical — boards, prototypes, test rigs and a bench. Hardware and test roles are on-site. Software, design and cloud roles can be hybrid or remote within the United States, with periodic time on-site, because being near the device matters more than people expect.
We are a young company and we will say plainly that we cannot yet match the compensation of a large multinational. What we offer instead is unusual ownership, direct access to decisions, and work that ships.
6. Areas We Hire For
We do not always have a formal opening posted. We do always read a thoughtful application. These are the areas where good people change what we can build:
- Embedded and firmware engineering — low-power sensor firmware, signal acquisition, BLE communication, battery behaviour.
- Signal processing and algorithms — deriving heart, sleep, movement and recovery metrics from noisy real-world data.
- Mobile and desktop engineering — iOS and Android, macOS and Windows clients.
- Cloud and backend engineering — data pipelines, APIs, storage and cost-aware infrastructure.
- Hardware and industrial design — enclosure, mechanical fit, comfort, manufacturability.
- Design and front-end — interface, motion, and the website you are reading.
- Operations, quality and compliance — testing, certification, documentation and supply coordination.
7. How We Hire
Our process is short on purpose, because long processes mostly test patience:
- A conversation. What you have built, what you want to build, and whether this is the right room for you.
- A practical exercise. A real problem close to the work, scoped to a few hours. We do not use puzzle interviews, and we do not ask for unpaid work we would ship.
- A technical discussion. We walk through your exercise or your prior work together.
- A decision, with a reason. We tell you either way, and we tell you why.
We read applications from people without conventional credentials. Show us something you have made and how you thought about it. That carries more weight here than a degree.
8. Internships and Early-Career Roles
We take a small number of interns and early-career engineers, and we give them real work — not a slide deck about work someone else did. In exchange we ask for curiosity, a willingness to read documentation before asking, and the honesty to say when you are stuck. Being stuck is normal. Hiding it is expensive.
9. Equal Opportunity
Adarna Inc. is an equal opportunity employer. We do not discriminate on the basis of caste, religion, race, colour, sex, gender identity or expression, sexual orientation, marital status, pregnancy, age, disability, language, or place of origin. Hiring decisions are made on capability and fit for the work.
If you need an adjustment to the interview process for any reason — timing, format, accessibility — tell us when you apply and we will arrange it. Asking will never count against you.
10. How to Apply
Write to contact@adarna.us with the subject line "Careers — [the area you are interested in]". Include:
- A short note on what you want to work on and why this, specifically.
- Your CV, or a link to work we can look at — repository, portfolio, project write-up.
- One thing you have built that you are genuinely proud of, and what was hard about it.
We read every application. We aim to reply within two weeks, and if we are slower than that it is a backlog, not a silent rejection — you are welcome to follow up.
11. Your Data When You Apply
Information you send us as an applicant is used only to assess your application. We keep it for up to twelve months in case another suitable role opens, and we delete it on request at any time. We do not share it outside the company. For the full picture, see our Privacy Policy.