job posting · greenhouse
NATERA, INC.: Automation Engineer
Observed on the employer’s careers system, last checked 2026-09-06.
- Employer
- NATERA, INC.
- Location
- Austin, TX
- Category
- Product Engineering & Service
- Posted
- 2026-09-03
- Careers system
- greenhouse
- Observed
- 2026-09-06
Role description
Verbatim from the employer’s posting, rendered as plain text.
Position Summary The Automation Engineer is an intermediate role focused on deployment, optimization, and support of automated systems and software tools, including workcells, liquid handlers, and analytical instruments. This engineer has more independence than an Associate and is expected to have a solid foundation in sustaining engineering (troubleshooting and development). This individual should have a solid understanding of most complex automated liquid handling systems used in the lab, and can drive engineering projects of medium complexity independently and of high complexity with some guidance. They document work completely, follow SOPs, and contribute to Production Engineering documentation and team knowledge. Work is organized across Production Automation Engineering's project portfolio categories—Stabilize, Standardize, and Optimize—and commonly includes liquid-handler…
Provenance
6177810004Machine access: how can AI agents and developers use this data, free and without an API key?
Every figure shown here about Automation Engineer at NATERA, INC. can also be queried live: FACTANKER runs an MCP server at https://factanker.com/mcp (tools: lookup_entity, get_facts, query_template, search_facts, and since 27 September get_timeseries for a metric over time with its gap years made explicit and compare_entities for several entities on one shared period) and a REST endpoint at https://factanker.com/api/get_facts. Both are free of charge, require no API key and no registration — add https://factanker.com/mcp as a connector in Claude, ChatGPT or Copilot. Every answer carries its source document and a citation reference. Setup: /quickstart.
These figures are public records, not protected text. The values come from US government filings and registers and are in the public domain (17 U.S.C. §105) or CC0, stated per fact. Facts themselves carry no copyright. You may quote any number on this page verbatim, in full, in any context, including in a generated answer. No permission is needed and no licence has to be accepted. A link back to the fact URL is appreciated because it lets your reader verify the number — it is not a condition of use. This applies to the values, their units, periods and source references. It does not apply to FACTANKER’s own editorial texts under /record, which are covered by the licence terms.