Software Engineer - Backend

We're partnering with a fast-growing technology company building sophisticated software on top of modern cloud data infrastructure.

They're looking for a Senior/Staff-level Backend Engineer to help build a customer-facing data product used to turn large, complex datasets into fast, intuitive workflows for nontechnical users.

This is a backend role for someone who likes hard systems problems but still cares deeply about the product those systems enable.

The challenge is deceptively simple:

Underneath that experience are difficult engineering problems involving data processing, distributed systems, performance, reliability, and increasingly real-time architectures.

You'll work on problems like:

• Optimizing queries, caching strategies, and precomputed state
• Designing systems that process and synchronize large amounts of data reliably
• Moving traditionally batch-oriented workflows closer to real time Building event-driven and change-data-capture workflows
• Developing analytics and experimentation capabilities
• Designing backend architecture that works across different customer data environments
• Exploring practical ways generative AI can improve user workflows

The systems underneath the product are complex.

That's a big part of the engineering challenge.

This is not a ticket-execution role.

You'll have meaningful responsibility for technical decisions and will help:

• Design backend systems and architecture
• Own projects from initial design through production
• Make tradeoffs around scalability, reliability, performance, and maintainability
• Solve difficult data-processing and performance problems
• Work through product requirements before implementation
• Collaborate closely with product and engineering
• Use real customer feedback to influence technical decisions
• Mentor other engineers as the team continues to grow

We're looking for engineers who want ownership of both how a system works and whether it solves the right problem.

The strongest candidates have already been trusted with difficult backend problems and significant technical ownership.

You may be a good fit if you've:

• Designed and built sophisticated backend systems
• Solved meaningful scale, performance, or reliability challenges
• Worked with large or complex datasets
• Made significant architecture and systems-design decisions
• Operated successfully in a high-growth technology environment
• Taken on increasingly difficult problems throughout your career
• Worked closely enough with a product to understand the impact of your engineering decisions on actual users
• Mentored engineers or served as a technical leader

We're much more interested in what you've built and the decisions you owned than whether your resume contains our exact technology stack.

You may have experience with some combination of:

Backend: Go, Python, Type Script/Node.js, Java, Kotlin, Rust, or similar

Data: SQL, PostgreSQL, cloud data warehouses, large-scale data platforms, query optimization, data modeling, caching, and precomputation

Distributed Systems: Event-driven architecture, asynchronous processing, concurrency, high-throughput services, workflow orchestration, CDC, batch processing, and streaming systems

Messaging / Streaming: Kafka, SQS/SNS, Pub/Sub, Kinesis, RabbitMQ, Redis, Flink, Spark, or similar technologies

Cloud / Platform: AWS, GCP, Azure, Docker, Kubernetes, observability, and production reliability tooling

Product Backend: APIs, multi-tenant SaaS architecture, integrations, analytics, experimentation, and customer-facing backend services

You do not need experience with every technology listed above.

Strong systems fundamentals and evidence of solving difficult engineering problems matter considerably more than checking every technology box.

We're particularly interested in engineers who can point to things like:

• Improving database or query performance
• Building high-throughput APIs and backend services
• Designing storage or data-processing architecture
• Building event or stream-processing systems
• Solving difficult concurrency, consistency, latency, or reliability problems
• Owning critical customer-facing backend infrastructure
• Taking a system from initial architecture through production and scale

When you describe your work, tell us what was difficult, what you personally…