Software Architect at Tactile Medical | JobsWithPay

Wait…

Define and maintain the architecture strategy, technical standards, design principles, and reference architectures for backend services, shared platform capabilities, APIs, integrations, and connected-product software systems.
Establish clear architectural boundaries between regulated medical device functionality, supporting system functionality, and non-medical-device functionality through documented interfaces, service boundaries, risk isolation, data ownership, access controls, and deployment strategies.
Define reusable backend and platform patterns that support mobile applications, web applications, connected devices, customer-facing workflows, internal tools, and future shared service needs.
Serve as the senior technical authority for backend and platform architecture decisions, with responsibility for data flows, identity, integrations, telemetry, observability, and operational reliability.
Lead architecture reviews, technical trade-off discussions, design assessments, risk reviews, and decision-making for new products, major features, platform changes, and modernization efforts.
Design and govern secure, scalable, resilient, maintainable, and observable cloud-based service architectures that support connected medical device products and related digital services.
Guide cybersecurity architecture for cloud and platform services, including secure design patterns, threat modeling, access control, data protection, monitoring, vulnerability management, and secure update support.
Create and maintain review-ready architecture documentation, including system diagrams, interface definitions, data flows, architecture decision records, deployment models, and design content that supports traceability.
Ensure architecture artifacts support design controls, Design History File inputs, FDA 510(k) submission support, cybersecurity documentation, software change assessments, risk management, verification planning, and controlled release activities.
Collaborate cross-functionally with internal teams and external development partners to build alignment, improve architecture governance, and strengthen internal ownership of critical technical decisions.