Skip to main content

Snowflake

Software Engineer - Database Engineering

US-CA-Menlo Park$160k–$230kfulltimemidAdded today

About this role

Snowflake is seeking Software Engineers for the Database Engineering team to design and optimize a petabyte-scale cloud data warehouse. You'll work on distributed systems, query optimization, and performance engineering while building highly reliable software for enterprise customers.

What you'll do

  • Design, develop, and support petabyte-scale cloud database systems with high parallelism and fault tolerance
  • Analyze performance and scalability bottlenecks, identify root causes, and implement solutions
  • Design and implement query optimization and distributed data processing algorithms
  • Architect and build new service infrastructure for the Snowflake Data Cloud
  • Develop tools and instrumentation for customer workload visibility and insights
  • Conduct testing, debugging, and documentation of complex distributed systems

What they're looking for

  • Java or C++
  • Linux development environment
  • Data structures and algorithms
  • Distributed systems design
  • Multi-threading and concurrency
  • SQL and database technologies
  • Query optimization and execution
  • Large-scale data processing systems
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Snowflake

Snowflake builds a cloud data platform with marketplace capabilities, analytics infrastructure, and AI-powered data solutions, supported by robust security and streaming systems. The company is hiring full-stack engineers, analytics engineers, solution engineers, security-focused software engineers, and principal engineers to enhance its platform and infrastructure.

View all jobs at Snowflake

Likely interview questions

  • Describe a complex performance bottleneck you've diagnosed and resolved in a distributed system—what was your approach?
  • How would you design a query optimizer for a petabyte-scale data warehouse, and what trade-offs would you consider?