# Lead, Office of Software Assurance at Natera

> Remote · United States · Staff · Software engineering · open. Source: https://alderhq.app/jobs/greenhouse%3Anatera%3A6263455004 (read 2026-11-17).

## Facts (observed)

- Company: [Natera](https://alderhq.app/companies/natera)
- Location text: US Remote; US - TX
- Where it can be done from (inferred): Remote · United States (evidence: "Location: US Remote; US - TX")
- Posted: 2026-11-17 (0 days ago)
- First seen by alder: 2026-11-17 · last verified: 2026-11-17
- Reposted: 0 times · edited: 0 times
- Apply on the employer's site: https://job-boards.greenhouse.io/natera/jobs/6263455004

## Pay and sponsorship

- Posted pay: $139k–$174k per year (from the listing's pay field)
- Market band for similar posted roles (United States, n 3053): p25 $185k, median $215k, p75 $253k
- H-1B filings at this company for similar roles, FY26: 14, median offered wage $163k ([US DOL OFLC LCA disclosure data](https://www.dol.gov/agencies/eta/foreign-labor/performance))

## Description (the employer's text)

### 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.

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/greenhouse%3Anatera%3A6263455004 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.
