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.
San Francisco · New York City · United States · San Francisco, California, United States
Open 3 months, first seen by us 101 days agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Build and scale the log ingestion and processing pipeline
Design high-throughput, low-latency data processing systems
Own storage, indexing, and query systems for logs
Keep backend systems reliable, scalable, and cost-efficient
Debug and optimize performance across the whole stack
Build and scale our log ingestion and processing pipeline
Design systems for high-throughput, low-latency data processing
Own storage, indexing, and query systems for logs
Ensure reliability, scalability, and cost-efficiency of our backend systems
Debug and optimize performance at every layer of the stack
Strong experience with distributed systems and data infrastructure
Familiarity with streaming systems, databases, and large-scale data pipelines
Deep understanding of performance tradeoffs (latency, throughput, cost)
Ability to design systems from scratch, not just maintain them
Comfort working close to the metal when needed
Bonus: experience with observability platforms, logging systems, or time-series data
From the employer’s posting.
Open 3 monthsWe first saw this posting 101 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$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.
Day 101
Up longer than most. Similar jobs usually come down between day 6 and day 56.
From 14,766 similar postings that came down. Coming down is not always a hire.
1 open job
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.
Our tech Our stack is TypeScript end-to-end. We use PostgreSQL for relational data, Temporal for durable execution, and the Vercel AI SDK to orchestrate our AI agents against the latest models. At the infrastructure layer, we use Terraform, Kubernetes, and AWS. Some of the most interesting engineering problems we grapple with are:
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
In 2026, we're on the verge of an "infinite software crisis." How will we support, maintain, and operate the explosion in application development?
Our answer is Sazabi: the AI-native observability platform for fast-moving engineering teams.
Sazabi gives teams a single place to ask questions about their production systems in plain language, automatically visualize what's happening, and get to the root cause 10x faster. No tedious instrumentation. No dashboard configuration. No alert tuning. Just answers.
We're backed by tastemakers from the world's top AI companies: Vercel, Graphite, Daytona, Browserbase, LangChain, Mastra, Replit, and more.
What you’ll doBuild and scale our log ingestion and processing pipeline
Design systems for high-throughput, low-latency data processing
Own storage, indexing, and query systems for logs
Ensure reliability, scalability, and cost-efficiency of our backend systems
Work on distributed systems that power real-time observability
Debug and optimize performance at every layer of the stack
Strong experience with distributed systems and data infrastructure
Familiarity with streaming systems, databases, and large-scale data pipelines
Deep understanding of performance tradeoffs (latency, throughput, cost)
Ability to design systems from scratch, not just maintain them
Comfort working close to the metal when needed
Bonus: experience with observability platforms, logging systems, or time-series data
Our stack is TypeScript end-to-end. We use PostgreSQL for relational data, Temporal for durable execution, and the Vercel AI SDK to orchestrate our AI agents against the latest models. At the infrastructure layer, we use Terraform, Kubernetes, and AWS.
Some of the most interesting engineering problems we grapple with are:
AI agents at production scale
Log processing at scale
Multi-region data architecture
Real-time streaming infrastructure
Evals and reinforcement learning
Zero-downtime deployments and fast rollbacks
Competitive salary and equity
Free lunches (in-office only)
Health, dental, and vision insurance
Unlimited paid time off
Paid parental leave
Our team comes from Brex, Y Combinator, Rootly, Google, Doppel, and other top tech companies. We move fast and hold a high bar for both the product and each other.
We operate according to six values:
Integrity. We say what we mean, do what we say, and own our mistakes.
Urgency. We treat every week like it matters, because it does.
Craftsmanship. We care deeply about the quality of our work.
Service. We're here to make developers’ and our teammates’ lives easier.
Kindness. We're direct, and we move fast, but we treat each other well.
Fun. We genuinely enjoy working together. If you don't love what you're building and who you’re building it with, what's the point?
You can find out more about us here:
Watch our launch video
Read the manifesto
Sazabi is more than just a tool. It’s also a philosophy. We're taking a radically different approach to observability, centered on three big ideas:
Less is more. Most observability platforms drown you in dashboards and modules that you don’t need. We believe observability needs less UI, not more. Sazabi surfaces exactly the information you need in a simple, beautiful chat interface.
Logs are all you need. The “three pillars of observability” idea is outdated. Sazabi accepts only one kind of telemetry: logs. This simplifies the instrumentation and product experience dramatically.
Monitoring is dead. Creating and maintaining static alerts for a fast-evolving system is a fool’s errand. The future is agentic anomaly detection: AI agents that automatically check your app for issues 24-7.
We came to these beliefs the hard way — after years of building infrastructure and responding to incidents with tools that offered plenty of bells and whistles, but no clear answers when it counted most.
If this way of thinking resonates with you, come build with us.
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.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.