Software Quality Assurance Engineer

DEKA Research & Development is looking for a technically deep, process-driven Software Quality Assurance Engineer to join our cloud engineering team. This is an individual contributor role with outsized organizational impact: you will work alongside cloud-native engineering teams to learn how they work, codify documentation best practices, and scale those practices across teams building similar products.

Additionally, you will champion automation-first, Dev Sec Ops -oriented quality practices to build the documentation and process infrastructure that allows developers to focus on writing great product code — not wrestling with regulatory paperwork. This role does not manage people, it leads through technical credibility, persuasion, and partnership.

• Embed with engineering teams to understand existing documentation practices and automation tools for software design, V&V activities, and change control, then produce standardized templates, work instructions, and SOPs that can be applied consistently across teams with similar cloud-native product lines.
• Serve as the primary author and owner of software lifecycle documentation artifacts including Software Development Plans (SDPs), Software Requirements Specifications (SRS), Software Design Documents (SDD), Verification & Validation Plans and Reports, and Software Risk Management Files
• Drive document change control processes from initiation through approval, coordinating review cycles to keep releases on schedule.
• Establish and maintain traceability matrices linking software requirements, design elements, risk controls, test cases, and defects, ensuring end-to-end objective evidence is audit-ready at any point in the release cycle.
• Own the documentation project plan for each software release, tracking open documentation tasks, review cycles, and approval gates as a parallel workstream to the engineering release schedule.
• Facilitate documentation readiness reviews prior to design freeze, test execution, and regulatory submission milestones. Communicate readiness status to engineering leads; elevate blockers early and drive resolution.

• Bachelor's degree in Computer Science, Software Engineering, or a closely related technical discipline required.
  • Advanced degree or professional certifications (ASQ CSQE, ISTQB, RAC) a plus but not required in lieu of demonstrated experience).
• 5–8 years of combined experience in software quality engineering, software development, or a closely adjacent technical role, with at least 2 years in an FDA-regulated environment (medical devices, digital health, or pharmaceutical software).
• Hands-on software development background — you must be able to read and reason about Go, Java or Python code, Infrastructure-as-Code (Terraform, Ansible), and automated test code (Playwright, pytest) without requiring a developer to walk you through it.
• Demonstrated experience producing IEC 62304-compliant documentation for Class B or Class C software
• Practical knowledge of ISO 14971 risk management methodology as applied to medical device software; experience authoring or materially contributing to FMEAs and software hazard analyses.
• Working knowledge of FDA cybersecurity expectations for medical devices, including familiarity with NIST frameworks and the ability to assess cloud-hosted systems against those standards.
• Familiarity with cloud-native architectures (microservice and event-driven architectures at scale, networking, IAM) sufficient to understand system design documents and workflows.
• Direct experience writing automated tests in Python or Go, or using Playwright for UI/E2E test automation

• You default to automation and repeatability over manual processes, and you can articulate why that matters for regulatory defensibility, not just engineering velocity.
• You are a skilled communicator who can translate between regulatory language and engineering language — equally comfortable in a design review with a Go developer and a regulatory affairs meeting.
• You take documentation…