Back to jobs

Senior Data Engineer

Pay
Pay not listedSimilar roles state $127K–$189K
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: SALARIED_FT
From the employer’s posting

What you’ll work on

Full posting

Mytra is looking for a Senior Data Software Engineer to build the data platform that the rest of our software reads from.

Every robot and station puts out about 2 MB/s of telemetry and uploads a 60 MB recording every couple of minutes, roughly 6 to 8 GB per edge component per hour.

  • Design data capture lanes, storage tiers, and pipeline layout

  • Re-design the ingestion service so it scales

  • Build the transform engine that the team's transforms run on

  • Build the ID keying and crosswalk tables that join stored facts

  • Own retention policies, cost, and site-to-cloud egress as policy

From the employer’s posting
Mytra is looking for a Senior Data Software Engineer to build the data platform that the rest of our software reads from.
Every robot and station puts out about 2 MB/s of telemetry and uploads a 60 MB recording every couple of minutes, roughly 6 to 8 GB per edge component per hour. We're designing for 10,000+ storage cells a site, across many sites. Our control plane records every job, fault, and operator action. We require a system that unifies, aggregates, and transforms this data; as well as unlocking the power of our data for downstream insights.
Design the data capture lanes, storage tiers, and pipeline layout
Re-design the ingestion service with something that scales
Build the transform machinery. You own the engine and what it guarantees
Build the ID keying and crosswalk tables that connect a stored fact to its site, robot, hardware revision, calibration, layout, and pallet
Own retention, cost, and egress as policy instead of plumbing

Before you apply

Employer’s visa record
2 H-1B petitions approved in fiscal 2024 and 2025For the employer as a whole. This posting doesn’t say whether the role is sponsored. US Citizenship and Immigration Services.

What you’ll bring

All qualifications

Core experience

  • 5+ years building and running production backend or data infrastructure
  • Production code in Go, Python, Rust, Java or C++
  • Experience with durable message or streaming systems like Kafka or NATS
  • Production use of columnar, relational and NoSQL databases
  • Run services in production: CI/CD, monitoring, alerting
Qualification wording
5+ years building and running production backend or data infrastructure
You’ve written production code in Go, Python, Rust, Java or C++
You've worked with a durable message or streaming system (NATS/JetStream, Kafka, Pulsar, or similar)
You've used a columnar store, relational databases, and No-SQL databases in production
You've shipped services and kept them running: CI/CD, monitoring, alerting, and being on the hook when they break

About Mytra

We’re creating an entirely new way to solve the most ubiquitous problem in industry - moving and storing material.

In the employer’s words · Read in context

Apply at Mytra

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 9, 202673 days ago
Recorded sightings
97
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$189K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,448 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 73

Up longer than most. Similar jobs usually come down between day 6 and day 56.

From 14,770 similar postings that came down. Coming down is not always a hire.

Mytra is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

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

  • C++
  • Java
  • Python
  • Rust
  • SQL
  • BigQuery
  • ClickHouse
  • GCP
  • Google Cloud Storage
  • Grafana
  • Iceberg
  • Kafka
  • Kubernetes
  • Go
Where the posting names them
- 5+ years building and running production backend or data infrastructure - You’ve written production code in Go, Python, Rust, Java or C++ - You've worked with a durable message or streaming system (NATS/JetStream, Kafka, Pulsar, or similar) and know how delivery guarantees, backpressure, and replay actually behave
- You've worked with a durable message or streaming system (NATS/JetStream, Kafka, Pulsar, or similar) and know how delivery guarantees, backpressure, and replay actually behave - You've used a columnar store, relational databases, and No-SQL databases in production and you have a strong understanding of how trade offs work in these technologies when used in data solutions - You've shipped services and kept them running: CI/CD, monitoring, alerting, and being on the hook when they break
- Experience with robotics, IoT, or industrial telemetry at volume, including formats like MCAP - GCP (GCS, BigQuery/BigLake), Kubernetes, and data systems run on-prem, at the edge, or air-gapped, where you can't lean on a cloud service being reachable - Prep the data store for ML or RL training to read directly
- You've built and run data services yourself; whether ingestion, CDC, or event pipelines, rather than writing jobs on top of someone else's platform - You know how columnar stores like ClickHouse and object-storage lakes like Parquet or Iceberg work, and have opinions about which belongs where. Schema governance, failure modes, and cost are design inputs for you, not afterthoughts. - Uncertainty isn’t scary, and you’re willing to realize mistakes and pivot
- Prep the data store for ML or RL training to read directly - Prometheus and Grafana experience as a consumer of the data pipeline A Final Note:
- You’ve written production code in Go, Python, Rust, Java or C++ - You've worked with a durable message or streaming system (NATS/JetStream, Kafka, Pulsar, or similar) and know how delivery guarantees, backpressure, and replay actually behave - You've used a columnar store, relational databases, and No-SQL databases in production and you have a strong understanding of how trade offs work in these technologies when used in data solutions

Your next step

Complete your application on ats.rippling.com. The employer’s form will show what is required.

Applying through Rippling

  • “The résumé will be parsed to fill in the application details”: check what it filled before you send.

Already applied? Track this application

Job description

View original posting ↗

About Mytra:

We’re creating an entirely new way to solve the most ubiquitous problem in industry - moving and storing material. We’re applying robotics and distributed software to create a new class of product for this $1T market. We’re focused on the supply chain industry first. The industry is in a massive bind with the continued growth of e-commerce, sharp rise in costs, and supply chain disruptions. What has been a “sleepy” industry for decades is now at the epicenter of sustaining the global economy.

About the role

Mytra is looking for a Senior Data Software Engineer to build the data platform that the rest of our software reads from.

Every robot and station puts out about 2 MB/s of telemetry and uploads a 60 MB recording every couple of minutes, roughly 6 to 8 GB per edge component per hour. We're designing for 10,000+ storage cells a site, across many sites. Our control plane records every job, fault, and operator action. We require a system that unifies, aggregates, and transforms this data; as well as unlocking the power of our data for downstream insights.

This includes the services that pull data off the wire, the stores it lands in, the ID keying that lets you join across sources, and the pipeline machinery that turns raw capture into the tables products and agents read. Your services will run inside customer facilities, cloud facilities, be durable for multi-day network outages, and enforces each customer's rules for data egress. As much of the services are not built, you will also have the opportunity to architect your solution from the group up.

What you’ll do:

  • Design the data capture lanes, storage tiers, and pipeline layout
  • Re-design the ingestion service with something that scales
  • Build the transform machinery. You own the engine and what it guarantees; the team writes the transforms that run on it.
  • Build the durable path for what the system does and has to remember
  • Build the ID keying and crosswalk tables that connect a stored fact to its site, robot, hardware revision, calibration, layout, and pallet
  • Own retention, cost, and egress as policy instead of plumbing. Retention policies per record and the site-to-cloud replication path.
  • Run what you build. These services run in our cloud and inside customer sites, so you own their CI/CD, monitoring, and alerting.

Ideal Candidates

  • 5+ years building and running production backend or data infrastructure
  • You’ve written production code in Go, Python, Rust, Java or C++
  • You've worked with a durable message or streaming system (NATS/JetStream, Kafka, Pulsar, or similar) and know how delivery guarantees, backpressure, and replay actually behave
  • You've used a columnar store, relational databases, and No-SQL databases in production and you have a strong understanding of how trade offs work in these technologies when used in data solutions
  • You've shipped services and kept them running: CI/CD, monitoring, alerting, and being on the hook when they break
  • You've designed schemas or data contracts that had to survive change
  • BS/MS in Computer Science, or the equivalent from having done the work
  • You've built and run data services yourself; whether ingestion, CDC, or event pipelines, rather than writing jobs on top of someone else's platform
  • You know how columnar stores like ClickHouse and object-storage lakes like Parquet or Iceberg work, and have opinions about which belongs where. Schema governance, failure modes, and cost are design inputs for you, not afterthoughts.
  • Uncertainty isn’t scary, and you’re willing to realize mistakes and pivot
  • You can convey complex ideas and technical concepts to a diverse audience
  • Openness, inquisitiveness, and constant ambition are important values
  • You enjoy collaborative working and taking time to help others
  • You seek and value ownership, accountability, and taking on responsibility

Nice to have:

  • Experience with robotics, IoT, or industrial telemetry at volume, including formats like MCAP
  • GCP (GCS, BigQuery/BigLake), Kubernetes, and data systems run on-prem, at the edge, or air-gapped, where you can't lean on a cloud service being reachable
  • Prep the data store for ML or RL training to read directly
  • Prometheus and Grafana experience as a consumer of the data pipeline

A Final Note:

If this role excites you, we encourage you to apply — even if you don’t check every box. At Mytra, we build bots, but we hire humans. We value thoughtful challengers who communicate with clarity and respect, and we’re lifelong learners committed to getting better every day. We move fast, learn faster, and show up for each other under pressure. The best outcomes come from diverse perspectives working together to build something meaningful and built to last

Benefits Include:

  • Competitive compensation and equity grants at a high-growth company backed by top-tier VCs
  • Fully subsidized health coverage, including medical (baseline plans), dental, and vision for employees and dependents
  • 401(k) plans and employer-subsidized life insurance
  • Fully subsidized lunch and snacks at HQ—we eat and share stories together at the “long” table
  • Generous PTO and company-paid holidays, including one week over the winter break so everyone can recharge together
  • Voluntary pet insurance, Voluntary Life Insurance, Accident, Critical Illness, and Hospital Indemnity
  • Fully subsidized tax advisory services and education to help you understand your equity
  • Commuter benefits, including a up to $150 monthly commuter benefit
  • Lively, modern combined office and lab space where we rapidly iterate through design, build, and test phases
  • Fully equipped onsite gym and showers at headquarters

Pay Notice

Compensation for this position will be set based on the candidate's experience level and location. The posted salary band is applicable only to the San Francisco Bay Area and is subject to change.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

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.

About the role

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.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Brisbane, CA

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.