Concurrency and isolation — Build visibility and isolation semantics for non-linear, multi-context execution patterns.
Executor-storage interface — Own buffer management, prefetch behavior, and cost model correctness when storage is remote.
Agentic tooling — Use AI coding agents critically on a large C/C++ codebase. Know where they fail.
Technical leadership — Drive implementation-level decisions across global engineering teams.
Who You’ll Work With
You will be part of a high-performing engineering team building core components of Teradata’s AI platform. You will collaborate closely with other engineers, AI/ML specialists, product managers, cloud architects, and partner teams across the company. The role offers opportunities to contribute directly to Teradata’s AI product roadmap and technological direction.
What Makes You a Qualified Candidate
Bachelor’s / Master’s / PhD degree in Computer Science or equivalent from a recognized institution.
15+ years of experience on backend services, distributed systems, or data platform development.
Strong proficiency in C, C++, Rust for development.
Internals experience with PostgreSQL or postgres based relational engine — source-level, not API-level
Deep understanding of the WAL write path, checkpointing, and crash recovery mechanics
Ability to trace and resolve concurrency anomalies through the engine's MVCC implementation
Clear mental model of where traditional storage assumptions live in the executor and buffer manager
Practical experience with AI coding assistants on production systems engineering work
What You’ll Bring
Deep expertise in systems or database engineering, with meaningful time spent inside a relational engine at the source level
Demonstrated contributions to PostgreSQL or an equivalent open-source engine — patches, extensions, or fork-level work
Production experience with storage or replication subsystems under real failure conditions
Comfort operating across distributed teams with high autonomy and low process overhead
A track record of technical decisions that held up — and the judgment to know when to revisit them
#LI-PB1