Technical Support Engineer US

YugabyteDB

7d•$90,000 - $120,000•Remote

About The Position

At Yugabyte, 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. 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. 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.

Requirements

Bilingual in English and Spanish — not conversational, genuinely fluent.
Willing to work weekends (Saturday and Sunday) with days off during the week.
Proactive in investigating unfamiliar issues.
Embraces not knowing the answer as a learning opportunity.
Willing to ask for help when stuck and help others when they are stuck.
Technical background in any discipline — software, systems, automotive, aerospace, networking, electronics, etc.
Familiarity with Linux tools -- used find and grep to navigate a filesystem.
Takes detailed notes on findings, actions taken, and next steps.

Nice To Haves

Experience with any relational database — even if it's just writing queries
Experience on a support team for a large software product

Responsibilities

Triage and own technical support tickets from enterprise customers, collaborating with a global team across time zones
Investigate incidents methodically — reading logs, running queries, tracing replication issues — and surface the root cause, not just the fix
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)
Attempt repros of customer issues and document the steps for others to replicate
Escalate to engineering when warranted, with enough evidence that they can act immediately
Contribute to the team's shared knowledge base and improve how we handle problems we've seen before
Be the calm, professional voice a customer hears when their weekend just got complicated