Technical Support Engineer

<div class="content-intro"><p>Yugabyte is the company behind <strong>YugabyteDB</strong>, the AI-ready, multi-modal, distributed PostgreSQL database for cloud-native apps. Trusted by industry leaders including Shopify, Paramount+, GM, Kroger, Fiserv, and NPCI, YugabyteDB has been deployed in over 100 countries and powers more than 5 million clusters worldwide.</p> <p>Together, our hard-working team of experts and our industry-leading technology are uniquely positioned to meet the demands of modern workloads: geo-distributed, ultra-resilient, and built to scale without limits.</p> <p>Our Yugabeings (distributed, like our database) span 12+ countries and multiple time zones, sharing expertise from diverse backgrounds and industries.</p></div><h1>Technical Support Engineer</h1> <p>Remote (Americas)&nbsp;</p> <p>At <strong>Yugabyte</strong>, we are on a mission to become the default transactional database for enterprises building cloud-native applications. YugabyteDB is our PostgreSQL-compatible distributed SQL database — resilient, scalable, and built to run anywhere. We're not just building software; we're watching major enterprises throw out Oracle and build something better, and the people who help them get there are the ones sitting in this team.</p> <p>&nbsp;</p> <h2>About This Role</h2> <p>We're looking for someone who gets genuinely excited when a customer's database is on fire, because they are eager to dive in and help.</p> <p>This isn't a "ticket-monkey" role. You won't be copy-pasting canned responses into a queue. You'll be working live cases — distributed systems behaving unexpectedly, replication lag climbing, certificates expiring in production — alongside a global team that actually cares about getting to the root of things. You'll learn YugabyteDB, cloud infrastructure, and distributed systems the way everyone learns them best: by necessity, with great people around you.</p> <h2>What You'll Do</h2> <ul> <li>Triage and own technical support tickets from enterprise customers, collaborating with a global team across time zones</li> <li>Investigate incidents methodically — reading logs, running queries, tracing replication issues — and surface the root cause, not just the fix</li> <li>Write clear internal notes and handover documentation so the next engineer can pick up exactly where you left off (this is not optional; notes are the job)</li> <li>Attempt repros of customer issues and document the steps for others to replicate</li> <li>Escalate to engineering when warranted, with enough evidence that they can act immediately</li> <li>Contribute to the team's shared knowledge base and improve how we handle problems we've seen before