Tailor my application

Lead, Office of Software Assurance

US OnlyFull-timePosted More jobs at Natera

Level
Senior
IST hours
No overlap with IST

Apply on Remote OK (opens in a new tab)

Not listed

Our reading of the listing. No overlap with IST. This is a guess from the text, so check the original post.

Listing check. Checked 22 Nov 2026: no sign it has closed

We opened the apply link and looked for signs that the job had closed. Finding no sign of closure does not confirm that the role is still open or that the employer is hiring.

Why we show this

We work these out from the words of the listing, so they can be wrong. Check the original post before you apply.

India eligibility

Not marked as open to India Inferred by us

The listing puts the role in another country or region, and nothing in it says people in India can apply.

From the location: “US Only”

Whether a job is open to India is a separate question from its working hours.

Working hours

No overlap with IST Inferred by us

The listing names a place but no time zone, so we assumed that place’s usual 9-to-5 day.

From the location: “US Only”

Overlap counts the hours of a 9-to-5 day in the job’s time zone that fall between 9:00 and 19:00 IST.

Hours that suit IST do not mean the employer hires in India. See India eligibility above.

Pay in rupees

No salary listed Not stated

The listing does not state a salary, so there is no rupee estimate.

Read the original listing ↗

About the role

Role Summary

Â

The Office of Software Assurance (OSA) Lead is the senior individual contributor who establishes and leads the Office of Software Assurance, a new shift-left software quality function inside the Agile Office, through technical expertise and influence rather than line management. The OSA embeds right-sized, risk-based assurance into a 1,000+ person Engineering organization, so that compliance evidence is produced as a natural, tool-native output of how teams build, not assembled after the fact.

Â

You will own day-to-day software quality execution across three lifecycle domains (SDLC, Computer Software Assurance, and Infrastructure Qualification). Natera’s Software Quality Assurance department keeps independent oversight, approval authority, and the front-line role in audits and inspections. Your focus is faster, simpler, and compliant delivery, and you do it in a way you can defend to an auditor. The ideal candidate is a software engineer first, someone who understands code, CI/CD, and engineering tooling, and who has worked close enough to regulated environments to apply quality and regulatory expectations without becoming a bottleneck.

Â

What You Will Do

Â

  • Stand up the OSA and execute its charter in phases: Launch (engineering-tool assurance), Extend (product-software assurance planning and evidence-readiness review), and Mature (largely automated, tool-native release-readiness evidence, with SQA operating by exception).
  • Own the OSA Charter and the OSA Responsibility & Governance Matrix, and keep them current with SQA concurrence. Review annually or sooner as responsibilities phase in.
  • Provide technical direction, coaching, and quality review for the OSA assurance resources, and contribute to their hiring and development plans in partnership with the Head of Agile Office. Coordinate, coach, and quality-check the engineers assigned the SQE capability within engineering teams.
  • Define baselines and targets with the Sponsor and report on OSA success metrics: assurance turnaround and cycle time versus the legacy CSV path, deliverables per release versus the 8–10-per-release baseline, intake quality, SQA relief, inspection readiness, and capability milestones.

Deliver right-sized assurance

  • Oversee AL1–AL2 assurance planning and participate in AL3–AL4 assurance under the CSA SOP. This covers the path from CSA Intake through Software Assurance Plan, execution, report and closeout, and Service Catalog registration.
  • Recommend the Assurance Level and assurance approach at CSA Intake. Select assurance activities and acceptance criteria from the Assurance Method Menu within an assigned level. Support SQA's level-confirmation walkthroughs.
  • Drive a documented-critical-thinking culture. Teams should be able to explain their risk-based rationale to an auditor and apply the least-burdensome approach.
  • Provide oversight, guidance, and continued standardization under the SDLC SOP and Infrastructure Qualification.
  • Over time, provide product-software risk-classification input, assurance and verification planning, evidence-readiness review, and periodic review by Assurance Level.

Â

Govern engineering tools and change

  • Own and execute the Engineering Tool Governance Work Instruction, from tool admission through retirement. Own and manage the Engineering Service Catalog, including registration of tools that hold regulated records. Oversee tool qualification.
  • Provide fast-path change oversight and impact disposition on engineering tickets under the Software Change Work Instruction. Route device-software changes to SQA.
  • Consult with Agile Office tooling administration on the assurance impact of tooling decisions.

Â

Partner with Software Quality Assurance (SQA) and the business

  • Operate the inspection-readiness model: the OSA executes and supplies the technical narrative and tool-native evidence, while SQA approves determinations, plans, and closeouts and leads in audits and inspections.
  • Maintain defined escalation triggers to SQA. Escalate unresolved scope or risk questions to the Sponsor and SQA leadership.
  • Work with Product Managers and Lab Directors, who hold charter-level accountability for intended use and business need, so intended use is clearly communicated at intake and confirmed at delivery.
  • Collaborate with the Security Team on lifecycle integration points (cybersecurity methodology stays with Security) and with Regulatory/QA on design-control boundaries.

Â

Build capability and automate

  • Lead delivery of the SQE Upskilling & Competency Development Plan across four tiers: regulatory and standards literacy, risk-based assurance and critical thinking, modern V&V and tool-native evidence practices, and quality judgment.
  • Provide compliant-SDLC coaching, process-feedback management, and training content. Source external training through bodies such as AAMI, ISPE, RAPS, and ASQ.
  • Champion automation: embed evidence capture in the tools of record (for example, source control, ticketing, CI/CD, and test management), so evidence is cited by reference rather than assembled by hand.

Â

Required

  • Bachelor's degree in computer science, software engineering, or a related technical field (or equivalent practical experience).
  • 8+ years of software engineering experience, with hands-on development, test automation, DevOps, or engineering productivity work. You can read code and review pipelines, and you earn credibility with engineers.
  • 4+ years working in or closely alongside a regulated environment, such as medical device, diagnostics, clinical laboratory, pharma or biotech, or another environment under design controls and a quality management system.
  • Working knowledge of risk-based software assurance and validation concepts, such as FDA Computer Software Assurance (CSA) guidance, computer system validation, or software verification and validation.
  • Practical familiarity with several of: IEC 62304, ISO 13485, ISO 14971, 21 CFR Part 820…

Technologies

  • devops

Match your resume to jobs like this

Details

Salary
Not listed
IST hours
No overlap with IST
Level
Senior
Type
Full-time
Location
US Only
Posted
Listed on
Remote OK

More remote jobs

Browse all remote jobs

Applying opens the original listing on Remote OK.