Acquire Senior Software Engineer​/Architect

If you are unable to complete this application due to a disability, contact this employer to ask for an accommodation or an alternative application process.

Full Time Denver, Denver, CO, US

Salary Range: $ To $ Annually

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 Type Script 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 Type Script, 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.
• 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…