Acquire Senior Software Engineer/Architect

Job Description

Job Description

About Acquire Learning

Acquire Learning builds software for Applied Behavior Analysis therapy. Clinicians and behavior technicians use Acquire during care, and the data they collect helps shape treatment decisions. Our product includes a web application and an offline-capable iPad app used in clinical sessions.

We are a small product and engineering team working in a HIPAA-regulated environment. Reliability, privacy, and data correctness are part of the product. A defect can interrupt a session or change the information a clinician relies on, so we take quality seriously.

About the role

This is a cross-functional product engineering role for a Senior Software Engineer who wants broad ownership. You will move between our TypeScript and Express backend, React web app, React Native iPad app, automated tests, manual product testing, and releases. You will also work directly with the Product Owner, Lead Engineer, CTO, and clinical subject-matter experts to turn real workflow problems into useful software.

This is not a role with a fixed frontend, backend, mobile, or QA lane. The work changes with the product's needs. You might build an API and web workflow for one initiative, debug an offline iPad problem in the next, and then help validate and release a change that spans all three applications.

Acquire does not have a separate QA department. Engineers own the quality of what they ship. You will write automated tests, test the product by hand, help assess release risk, and verify behavior after deployment. You do not need equal expertise in every part of the stack, but you must be willing to work across it and learn the parts you do not know yet.

This role requires architecture experience beyond a small product footprint. You must have helped a multi-tenant system grow in users, data volume, or traffic while preserving tenant isolation and data correctness. You must also have worked in healthcare or another regulated environment where privacy, access control, auditability, and release discipline are engineering requirements.

Our development cycle is fast. We want someone who can keep pace because they know how to divide work, automate checks, and verify what ships. Speed without control is not useful here.

You will report to J.J. Tomash, our CEO. You and the Lead Engineer will work as engineering peers, with each of you owning initiatives from discovery through release.

What you will do

• Own product changes from problem framing and scope refinement through implementation, testing, release, and production follow-up.
• Build and maintain backend services with TypeScript, Express, and MongoDB.
• Design application and data architecture that remains correct as the number of tenants, users, records, and requests grows.
• Build clinician and administrative workflows in our React web app.
• Contribute to our React Native iPad app, including offline behavior, shared-device workflows, synchronization, and native release quality.
• Write and maintain unit, integration, and end-to-end tests. Improve the code when it is difficult to test reliably.
• Perform hands-on exploratory and regression testing in real browsers and on iPads. Reproduce defects and document them with enough evidence to act.
• Partner with the Product Owner and clinical experts to clarify the problem, define acceptance criteria, find missing cases, and cut scope when a smaller solution is safer.
• Plan and execute application releases with the Lead Engineer and SRE. Assess migrations, backward compatibility, staged deployment, rollback, and installed mobile versions.
• Verify releases with product behavior, logs, error monitoring, and data-level evidence when appropriate. Treat a successful deployment as the start of verification, not proof that the feature works.
• Investigate production defects and customer reports. Trace them across the user experience, application code, API, and persisted data without exposing patient information.
• Build security, privacy, tenant isolation, auditability, and clinical-data correctness into every change that touches regulated data.

How we work

Product owns the problem, priority, and intended outcome. Engineering owns the technical approach and helps make the outcome specific enough to build and test. We expect engineers to ask product questions, challenge assumptions, and explain tradeoffs in plain language.

Quality is shared work. There is no handoff where an engineer declares a feature complete and waits for someone else to find the defects. The owner chooses the right automated coverage, performs the manual checks that automation cannot replace, and brings evidence to the release decision.

We write down important decisions, review each other's work, and disagree openly without turning disagreement into a contest. Small changes with clear evidence are better than large changes that depend on trust.

Who you are

• You have 5+ years of software engineering experience (or equivalent) and have shipped production software across the full stack.
• You are proficient in TypeScript, Node, and React, capable of reasoning about systems holistically from API to UI.
• You own the quality of your work: you write automated tests (unit/integration/E2E), perform exploratory manual testing, and verify deployments through logs and data evidence.
• You have hands-on experience scaling systems and designing multi-tenant architectures, ensuring rigorous isolation across authorization, storage, and background processes.
• You are experienced in HIPAA-regulated or similar high-compliance environments, where auditability, access control, and data privacy are core design constraints.
• You excel in collaborative environments, turning ambiguous requests into clear scope and communicating effectively through technical documentation and code reviews.
• You can navigate unfamiliar codebases independently and make steady progress, prioritizing clear, maintainable solutions.
• You are interested in learning the clinical and ABA workflows our software supports.

Helpful experience

• React Native in production, especially offline-capable or shared-device applications.
• MongoDB schema and query design, migrations, or data-integrity work.
• Cypress, Jest, API integration testing, mobile testing, or release automation.
• App Store and TestFlight release processes, including compatibility with older installed versions.
• Security engineering, threat modeling, audit design, or access control architecture.
• Small-team experience where engineers share product discovery, quality, support, and release work.
• Monorepos using pnpm, Turborepo, or similar tooling.

How we use AI

Agentic tools are part of our daily engineering workflow and a major reason we can move quickly with a small team. We are not looking for someone who has only sampled them, or for someone whose engineering process begins and ends with a prompt.

The right person has strong engineering habits that predate their use of agents, then deliberately changed those habits as the tools improved. They use agents throughout the day for investigation, implementation, tests, review, and repetitive work. They also know that faster generation moves the constraint to review and verification.

You should be able to explain where agents fail, how you keep changes reviewable, what you enforce with tools, and how you check claims against the codebase and running system. We will ask you to demonstrate that process during interviews.

What success looks like

• You can own a product problem across the application layers it touches instead of stopping at a team boundary.
• Your changes arrive with the automated and manual evidence needed to make a release decision.
• Product partners trust you to sharpen an ambiguous request without losing the clinical need behind it.
• You improve quality and release confidence while continuing to ship useful product work.
• You can anticipate the next scaling constraint without building machinery the current product does not need.
• You increase delivery pace without weakening tenant isolation, regulatory controls, or release evidence.
• You make the team more capable by sharing context, writing down decisions, and leaving clearer systems behind you.

Compensation & Benefits

• Base salary: $100,000-$120,000, with growth expected as the role grows.
• Semi-annual performance reviews with potential for raises.
• Hybrid schedule: 3-4 days per week in office
• Kaiser Permanente Health benefits
• Dental and Vision Insurance
• 401K
• Professional development assistance
• Generous Paid Time Off
• Additional benefits