Staff Software Engineer

Posted 4mo ago

The employer’s full description could not be read from their board. This is a summary of the posting — follow the apply link for the original.

Design, build, and maintain Rust-first connectivity layers, execution APIs, and adapter scaffolding
Partner with teams building the dbt compiler, semantic layer, and runtime to evolve adapter interfaces and system boundaries
Contribute to Arrow/ADBC and other open-source specifications or implementations
Own CI, testing frameworks, profiling, error reporting surfaces, and release readiness for Fusion adapters
Debug complex interoperability and performance issues across drivers, engines, and compute domains
Collaborate with internal and community maintainers to review PRs, write RFCs, and evolve public code architectures
Mentor engineers on systems best practices and contribute to shared patterns around resilience, debuggability, and API clarity

Strong programming background in Rust, Go, C++ or similar performance-oriented languages
Experience designing or maintaining SDKs, libraries, connectors, or compute/data integration codebases
Exposure to data warehouses, query engines, Arrow/columnar ecosystems, or execution runtimes
A desire to build foundational platform components that other teams and community members rely on
Comfort working in public code review loops, async-first communication, and collaborative RFC processes
A mindset grounded in debuggability, reliability, and ownership in ambiguous problem spaces
6+ years experience in software engineering, with strong systems-level skills
2+ years working in open-source, SDK, runtime, or low-level integration environments
Bachelor’s degree in Computer Science / related field or equivalent experience through industry OSS contributions

Contributed to or interacted with Arrow, ADBC, DuckDB, Presto, DataFusion, Spark, ClickHouse, or similar engines
Experience shaping adapter/plugin standards, driver contracts, or architectural interfaces used by others
Familiarity with Rust async ecosystems (tokio, tower, tracing) or Go concurrency practices
Prior OSS governance experience — triaging issues, reviewing PRs, or working with community maintainers
An interest in building developer-experience layers or scaffolding frameworks for adapter authors

Skills