Software Engineer - Database

Job Summary

Required Qualifications

• •Fluency in a backend language like C++, Rust, Java, or similar systems languages
• •Comfort working close to the metal
• •Foundation in query engines
• •Foundation in execution plans
• •Foundation in indexing
• •Foundation in performance optimization techniques
• •Experience with cloud infrastructure
• •Experience with networking
• •Experience building low-latency distributed systems
• •Ability to scope and lead projects that span multiple collaborators
• •Ability to manage cross-functional dependencies
• •Clear thinking
• •Careful design
• •Thoughtful tradeoffs
• •Comfort mentoring peers
• •Ability to help build a collaborative, high-agency environment
• •Ability to engage with the wider community
• •Ability to participate in open-source conversations
• •Ability to work directly with DuckDB Labs
• •Ability to align on APIs
• •Ability to shape where DuckDB goes next
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early
• •Ability to clear bottlenecks before they become problems
• •Ability to raise the bar for engineering practices across the team
• •Ability to help shape how modern analytics gets built
• •Ability to work hand-in-hand with the creators of DuckDB
• •Ability to unify local development with cloud operations
• •Ability to bridge the gap between software and data engineering workflows
• •Ability to push the boundaries of embedded database performance
• •Ability to push the boundaries of distributed execution
• •Ability to push the boundaries of user experience
• •Ability to stay closely connected to DuckDB Labs
• •Ability to align on APIs
• •Ability to shape what's next
• •Ability to own the core server and client extension logic
• •Ability to let DuckDB run seamlessly whether it's local or in the cloud
• •Ability to work in C++ right alongside the DuckDB codebase itself
• •Ability to drive major projects in dual execution
• •Ability to handle resource assignment
• •Ability to manage system reliability
• •Ability to handle incoming issues
• •Ability to lend DuckDB expertise to other teams
• •Ability to collaborate across MotherDuck
• •Ability to collaborate with the wider DuckDB community
• •Ability to ensure people get the best of both local and cloud worlds
• •Ability to spot architectural challenges early