> Markdown version of [/jobs/ext/3751162-staff-software-engineer-ingestion](https://www.wearedevelopers.com/jobs/ext/3751162-staff-software-engineer-ingestion). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - Ingestion - **Company:** Snowflake Inc. - **Location:** Bellevue, WA, United States - **Experience:** Experienced - **Salary:** $160,000.0 - $230,000.0 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Apache HTTP Server, C++ (Programming Language), Cloud Computing, Computer Engineering, Software Debugging, Distributed Systems, Apache Zookeeper, Snowflake, Data Lakes, Information Technology, Low Latency, Apache Kafka, Codebase - **Published:** October 15, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=1aa22b4311f85ac1 ## About the Role * 3-6+ years building and operating large-scale distributed systems or cloud infrastructure in production. You have shipped something hard that other teams depend on, not only application features. * Track record of end-to-end ownership: you took an ambiguous, cross-cutting problem, wrote the design, landed the code, and lived with it in production. Comfortable operating above your level, influencing adjacent teams and helping sequence larger bets without waiting to be told what to do. * Strong proficiency in Java (this codebase is Java-first). C++ or systems-level experience is a plus. You write concurrent, failure-aware code and you care about the invariants. * Experience in at least one of: multi-tenant control planes, durable queues and at-least-once processing, distributed locking / leases / membership, cluster scheduling, or streaming/ingest execution engines. * Instinct for correctness under failure. You think carefully about crashes, retries, redelivery, and exclusive ownership. * Clear written and verbal communication. You can write a clear design for engineers on neighboring product teams, and you can hold a technical argument without ego. * BS, MS, or PhD in Computer Science, Computer Engineering, or equivalent practical experience. Bonus Points * Experience building internal platforms used by multiple product teams (orchestration, job/runtime frameworks, multi-tenant schedulers). * Background in multi-tenant isolation and fairness: resource accounting, request throttling, quota systems, or load-aware placement. * Hands-on with transactional or consensus-backed metadata stores (for example etcd, ZooKeeper, or Spanner-style systems). * Familiarity with open table formats (Apache Iceberg, Delta Lake), Kafka-style streaming, or warehouse scheduling. * Performance work at scale: tail latency, memory and thread accounting, I/O batching, or cost-per-unit efficiency. * You have used AI as a serious engineering collaborator (design review, debugging, test generation) and can show how it made you faster without lowering the bar. Snowflake is growing fast, and we're scaling our team to help enable and accelerate our growth. We are looking for people who share our values, challenge ordinary thinking, and push the pace of innovation while building a future for themselves and Snowflake. ## Description * Design and ship core platform capabilities. Work on areas such as multi-tenant isolation, fair scheduling, ownership and placement, durable queues, source monitoring, or compute allocation. You own the work from design through production. * Strengthen isolation and fairness. Build and evolve the primitives that let many products and pipelines share one platform safely: quotas, backpressure, resource accounting, and intelligent placement. * Raise reliability and observability. Improve availability and latency for pipeline health, ingest APIs, and compute allocation. Instrument the system so behavior is visible and actionable. * Build a clean platform surface. Give product teams a consistent way to express pipelines and processing steps, so they can ship on shared primitives rather than special-casing the stack. * Scale the control plane. Design for more concurrent pipelines, higher ingest volume, and efficient use of compute and metadata as customer usage grows. * Operate what you ship. This platform sits on the critical path for production ingest. You will participate in production support, improve observability, and automate operational work. Mentorship of junior engineers is part of the job. You will also work closely with engineers on larger platform bets.