Pay
Higher than most similar jobs
$195K–$300K against $127K–$189K, the middle half of what similar US postings state.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
Fremont, CA
Actively hiring, first seen by us 3 days agoOur data platform is AWS-native by design: in GovCloud we add no third-party data software, and the platform only reads from the plant, never writes to it. If your experience centers on Snowflake or Databricks, expect to build the equivalent on S3, Iceberg, Athena and OpenSearch, and to own the parts a managed vendor would normally run for you. Compensation. The base salary range for this position is $195,000 – $300,000. This is a good-faith estimate; actual base pay depends on job-related knowledge, skills, experience, and level. This role is also eligible for equity (employee stock options) and benefits including medical, dental, vision, 401(k), and paid time off. Roles with significant travel may be eligible for an assignment premium. Export Control. This position may require access to information controlled under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). Applicants must be a U.S. person as defined in 22 CFR 120.62 (U.S. citizen, lawful permanent resident, or protected individual) or be eligible to obtain any required authorization.Read the full posting
Own data and telemetry architecture from edge historians to the lakehouse and live serving path
Build edge-to-cloud export that survives outages, with durable buffers and idempotent landing
Run the Iceberg lakehouse, including compaction, schema evolution and audited purges
Make multi-tenant isolation provable with CI tests across indexes, IAM and PostgreSQL
Deliver SQL datasets for quality investigations, ML training and dashboards
Own the data and telemetry architecture end to end
Build edge-to-cloud export that survives outages
Run the lakehouse: raw-to-Iceberg conversion, partitioning by tenant and date, compaction and snapshot maintenance, schema evolution, storage tiering, and audited purges
Make multi-tenant isolation provable across index aliases, IAM prefix policies and PostgreSQL row-level security, with CI tests that fail if one customer can read another's data.
Deliver the datasets the business runs on
Applicants must be a US person as defined in 22 CFR 120.62 (US citizen, lawful permanent resident, or protected individual) or be eligible to obtain any required authorization
Bachelor's degree in Computer Science, Computer Engineering or a related field, or equivalent experience.
8+ years building production data infrastructure or distributed systems, including on-call ownership and recovery of a system where data loss was unacceptable.
Qualifications • Bachelor's degree in Computer Science, Computer Engineering or a related field, or equivalent experience. • 8+ years building production data infrastructure or distributed systems, including on-call ownership and recovery of a system where data loss was unacceptable.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Higher than most similar jobs
$195K–$300K against $127K–$189K, the middle half of what similar US postings state.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,771 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
• Deep hands-on experience with a lakehouse table format (Iceberg, Delta Lake or Hudi) on object storage: partitioning, compaction, snapshot management, schema evolution and row-level deletes. • Strong production Python and advanced SQL; comfortable in a second language (Go, Rust, TypeScript, Java or Scala). • Time-series data at scale: high cardinality, late and out-of-order data, bucketing and downsampling, source time versus arrival time.
• Make multi-tenant isolation provable across index aliases, IAM prefix policies and PostgreSQL row-level security, with CI tests that fail if one customer can read another's data. • Deliver the datasets the business runs on: SQL that joins process telemetry to part genealogy for quality investigations, training and feature datasets for ML, and cost-bounded summaries for dashboards. • Bring inspection results, images and video into the same record, correlated to the machine jobs and parts that produced them.
Summary Deterrence builds autonomous production lines for energetics and munitions. Those lines generate process data that cannot be bought or synthesized: millions of signals per facility, tied to individual parts, kept as quality evidence for decades and used to train our models. The Staff Data Platform Engineer owns how that data moves from the factory edge into AWS GovCloud, how it is kept permanently, and how people and models read it: a complete, never-deleted lakehouse record on one path, and a sub-second live feed for line and customer dashboards on the other. The ideal candidate has run production data infrastructure where losing or mislabeling data was not an option, treats correctness and tenant isolation as properties to be tested rather than assumed, and wants their work to be the system of record for real factories. Key Responsibilities
• Distributed-systems correctness in practice: idempotence, retries, replay, backpressure, at-least-once delivery with de-duplication, and durable buffering over unreliable links. • Hands-on AWS data services (S3, Athena, Glue, IAM) and operation of OpenSearch or Elasticsearch: index and shard design, aliases, refresh tuning. • PostgreSQL depth: partitioning, row-level security, query performance.
Preferred Skills • AWS GovCloud or other regulated environments: ITAR, CUI, NIST 800-171, CMMC or FedRAMP. • Multi-tenant data platforms with server-side isolation.
• ML data infrastructure: training datasets, feature pipelines, SageMaker or similar. • Streaming at scale (Kinesis, Kafka or MQTT) and edge or intermittently connected systems (AWS IoT Core, Greengrass). • Manufacturing, quality or traceability data; hardware-adjacent domains.
How We Build Our data platform is AWS-native by design: in GovCloud we add no third-party data software, and the platform only reads from the plant, never writes to it. If your experience centers on Snowflake or Databricks, expect to build the equivalent on S3, Iceberg, Athena and OpenSearch, and to own the parts a managed vendor would normally run for you. Compensation. The base salary range for this position is $195,000 – $300,000. This is a good-faith estimate; actual base pay depends on job-related knowledge, skills, experience, and level. This role is also eligible for equity (employee stock options) and benefits including medical, dental, vision, 401(k), and paid time off. Roles with significant travel may be eligible for an assignment premium.
• 8+ years building production data infrastructure or distributed systems, including on-call ownership and recovery of a system where data loss was unacceptable. • Deep hands-on experience with a lakehouse table format (Iceberg, Delta Lake or Hudi) on object storage: partitioning, compaction, snapshot management, schema evolution and row-level deletes. • Strong production Python and advanced SQL; comfortable in a second language (Go, Rust, TypeScript, Java or Scala).
Key Responsibilities • Own the data and telemetry architecture end to end: the bulk path from edge historians to an S3 and Apache Iceberg lake, and the serving path from MQTT to a low-latency search store and live dashboards. • Build edge-to-cloud export that survives outages: durable edge buffers, export–confirm–delete semantics, idempotent landing, backlog replay, and disk guards, so that a cloud outage never stops a production cell.
• Own signal identity and data contracts: a registry that gives every signal a stable ID, unit and conversion; source-time semantics; clock-drift detection; and canaries that prove the live and historical views agree. • Make multi-tenant isolation provable across index aliases, IAM prefix policies and PostgreSQL row-level security, with CI tests that fail if one customer can read another's data. • Deliver the datasets the business runs on: SQL that joins process telemetry to part genealogy for quality investigations, training and feature datasets for ML, and cost-bounded summaries for dashboards.
• Hands-on AWS data services (S3, Athena, Glue, IAM) and operation of OpenSearch or Elasticsearch: index and shard design, aliases, refresh tuning. • PostgreSQL depth: partitioning, row-level security, query performance. • Infrastructure as code (Terraform or CDK) and CI/CD for data pipelines.
• Multi-tenant data platforms with server-side isolation. • ML data infrastructure: training datasets, feature pipelines, SageMaker or similar. • Streaming at scale (Kinesis, Kafka or MQTT) and edge or intermittently connected systems (AWS IoT Core, Greengrass).
• PostgreSQL depth: partitioning, row-level security, query performance. • Infrastructure as code (Terraform or CDK) and CI/CD for data pipelines. Level Expectations
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Already applied? Track this application
Software Engineer – Data Platform (Staff) – San Francisco Bay Area SummaryDeterrence builds autonomous production lines for energetics and munitions. Those lines generate process data that cannot be bought or synthesized: millions of signals per facility, tied to individual parts, kept as quality evidence for decades and used to train our models. The Staff Data Platform Engineer owns how that data moves from the factory edge into AWS GovCloud, how it is kept permanently, and how people and models read it: a complete, never-deleted lakehouse record on one path, and a sub-second live feed for line and customer dashboards on the other. The ideal candidate has run production data infrastructure where losing or mislabeling data was not an option, treats correctness and tenant isolation as properties to be tested rather than assumed, and wants their work to be the system of record for real factories. Key Responsibilities• Own the data and telemetry architecture end to end: the bulk path from edge historians to an S3 and Apache Iceberg lake, and the serving path from MQTT to a low-latency search store and live dashboards.• Build edge-to-cloud export that survives outages: durable edge buffers, export–confirm–delete semantics, idempotent landing, backlog replay, and disk guards, so that a cloud outage never stops a production cell.• Run the lakehouse: raw-to-Iceberg conversion, partitioning by tenant and date, compaction and snapshot maintenance, schema evolution, storage tiering, and audited purges in a store whose default is never delete.• Own signal identity and data contracts: a registry that gives every signal a stable ID, unit and conversion; source-time semantics; clock-drift detection; and canaries that prove the live and historical views agree.• Make multi-tenant isolation provable across index aliases, IAM prefix policies and PostgreSQL row-level security, with CI tests that fail if one customer can read another's data.• Deliver the datasets the business runs on: SQL that joins process telemetry to part genealogy for quality investigations, training and feature datasets for ML, and cost-bounded summaries for dashboards.• Bring inspection results, images and video into the same record, correlated to the machine jobs and parts that produced them.• Measure before scaling: signal change rates, historian and edge-buffer capacity, and per-tenant query cost, turned into capacity and cost models.• Write and review the architecture decision records for each data component, mentor engineers, and lead technical work across the edge, controls, traceability and front-end teams. Qualifications• Bachelor's degree in Computer Science, Computer Engineering or a related field, or equivalent experience.• 8+ years building production data infrastructure or distributed systems, including on-call ownership and recovery of a system where data loss was unacceptable.• Deep hands-on experience with a lakehouse table format (Iceberg, Delta Lake or Hudi) on object storage: partitioning, compaction, snapshot management, schema evolution and row-level deletes.• Strong production Python and advanced SQL; comfortable in a second language (Go, Rust, TypeScript, Java or Scala).• Time-series data at scale: high cardinality, late and out-of-order data, bucketing and downsampling, source time versus arrival time.• Distributed-systems correctness in practice: idempotence, retries, replay, backpressure, at-least-once delivery with de-duplication, and durable buffering over unreliable links.• Hands-on AWS data services (S3, Athena, Glue, IAM) and operation of OpenSearch or Elasticsearch: index and shard design, aliases, refresh tuning.• PostgreSQL depth: partitioning, row-level security, query performance.• Infrastructure as code (Terraform or CDK) and CI/CD for data pipelines. Level ExpectationsThis is a Staff role. You own the data architecture across edge and cloud, approve the design of every data component, set the standards for data contracts, retention and isolation testing, and are accountable for the platform's correctness and cost. You lead multi-team initiatives and raise the bar for the engineers around you. Your First Year• Measure real change rates and historian capacity on a production cell, and size the platform from the result.• Stand up the lake with tenant isolation enforced and tested, and answer the query it exists for: what was this cell doing while this serial number was being made?• Ship the signal registry, so that the live and historical views of every selected signal show the same series. Preferred Skills• AWS GovCloud or other regulated environments: ITAR, CUI, NIST 800-171, CMMC or FedRAMP.• Multi-tenant data platforms with server-side isolation.• ML data infrastructure: training datasets, feature pipelines, SageMaker or similar.• Streaming at scale (Kinesis, Kafka or MQTT) and edge or intermittently connected systems (AWS IoT Core, Greengrass).• Manufacturing, quality or traceability data; hardware-adjacent domains.• Cost engineering of data platforms: knowing what a query, a message and a stored byte cost, and designing to it. How We BuildOur data platform is AWS-native by design: in GovCloud we add no third-party data software, and the platform only reads from the plant, never writes to it. If your experience centers on Snowflake or Databricks, expect to build the equivalent on S3, Iceberg, Athena and OpenSearch, and to own the parts a managed vendor would normally run for you. Compensation. The base salary range for this position is $195,000 – $300,000. This is a good-faith estimate; actual base pay depends on job-related knowledge, skills, experience, and level. This role is also eligible for equity (employee stock options) and benefits including medical, dental, vision, 401(k), and paid time off. Roles with significant travel may be eligible for an assignment premium. Export Control. This position may require access to information controlled under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). Applicants must be a U.S. person as defined in 22 CFR 120.62 (U.S. citizen, lawful permanent resident, or protected individual) or be eligible to obtain any required authorization. Equal Opportunity. Deterrence Defense, Inc. is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, or any other characteristic protected by law. We are committed to working with and providing reasonable accommodations to applicants with disabilities; if you need an accommodation at any point in the process, contact careers@deterrence.com.New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Our data platform is AWS-native by design: in GovCloud we add no third-party data software, and the platform only reads from the plant, never writes to it. If your experience centers on Snowflake or Databricks, expect to build the equivalent on S3, Iceberg, Athena and OpenSearch, and to own the parts a managed vendor would normally run for you. Compensation. The base salary range for this position is $195,000 – $300,000. This is a good-faith estimate; actual base pay depends on job-related knowledge, skills, experience, and level. This role is also eligible for equity (employee stock options) and benefits including medical, dental, vision, 401(k), and paid time off. Roles with significant travel may be eligible for an assignment premium. Export Control. This position may require access to information controlled under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). Applicants must be a U.S. person as defined in 22 CFR 120.62 (U.S. citizen, lawful permanent resident, or protected individual) or be eligible to obtain any required authorization.
Fremont, CA
Working pattern and location restrictions need checking in the full posting.
This passage needs a closer read in the full description.