The ad says“Working understanding of Go’s concurrency model, including goroutines, channels, and the sync package”
The ad says“Experience with major cloud providers, Kubernetes, and container orchestration”
The ad says“Write database migrations that follow the team’s patterns for schema compatibility and safe upgrades”
The ad says“Solid debugging skills and the persistence to work a problem, and to escalate early when stuck”
The ad says“Experience building or operating distributed systems at a meaningful scale”
The ad says“Working understanding of Go’s concurrency model, including goroutines, channels, and the sync package”
The ad says“Experience with major cloud providers, Kubernetes, and container orchestration”
The ad says“Experience with observability, audit, or security features in an enterprise product”
The ad says“Comfortable with SQL, schema changes, and writing migrations”
Values
The ad says“CI/CD: GitHub Actions”
The ad says“Observability: Prometheus, Grafana”
The ad says“Backend: Go, Postgres, Kubernetes, gRPC”
The ad says“Backend: Go, Postgres, Kubernetes, gRPC”
The ad says“Observability: Prometheus, Grafana”
As a Backend Engineer on Coder’s Enterprise Experience team, you’ll build the features that help large organizations run Coder in production with confidence. The team owns what administrators and operators need to run Coder well. That covers how it scales, how it’s upgraded, how reliably it performs, how it’s observed and reported on, how activity is held accountable, and how it’s secured
You’ll join a cross-functional team of backend, platform, and QA engineers who own the operator experience end to end. You’ll ship features from design through production and partner with product and design to solve real operator problems
Build features end to end, from a design you write within the team’s existing approach through production rollout
Write database migrations that follow the team’s patterns for schema compatibility and safe upgrades
Build the observability, reporting, and audit features administrators rely on to see what their deployment is doing
Build features that keep enterprise deployments secure, following the team’s security practices
Help investigate and resolve scalability bottlenecks under production-like load, from database access patterns to concurrency in coderd
Help resolve backend issues surfaced by Coder operators and administrators
Document the features you build so a reviewer and the next engineer do not have to decode them
Participate in code reviews, contribute to RFC-style design discussions, and join the on-call rotation
Our tech stack:
Backend: Go, Postgres, Kubernetes, gRPC
Observability: Prometheus, Grafana
CI/CD: GitHub Actions
General: GitHub, Slack, Discord, Notion
Benefits
4% 401(k) match
Generous medical / dental / vision coverage
Paid sabbatical after 5 years
Fertility benefits through Carrot Fertility and generous parental leave
Monthly “perks” stipend for wellness, learning and development, travel, etc
Flexible time off
Annual workstation allowance for your home office
Remote work from anywhere, or join our Austin or San Francisco offices
Preferred experience
Strong verbal and written communication skills, including surfacing blockers and uncertainty early
Working understanding of Go’s concurrency model, including goroutines, channels, and the sync package
Solid debugging skills and the persistence to work a problem, and to escalate early when stuck
Comfortable with SQL, schema changes, and writing migrations
2+ years of professional software engineering experience
A self-motivated, analytical engineer who enjoys difficult technical challenges
Professional experience writing and shipping Go
Curiosity about the latest developer tooling
Experience building or operating distributed systems at a meaningful scale
Experience with major cloud providers, Kubernetes, and container orchestration
Experience with observability, audit, or security features in an enterprise product
Experience investigating performance under real-world load, including debugging race conditions
(Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!)
Recruitment process
We believe that the interview process should be transparent, consistent, and enjoyable. We value your time and hope to complete the interview process in two to four weeks, if schedules allow. Through your interviews, you will meet a mix of individual contributors, managers, and senior leaders
As an AI company, Coder embraces the use of AI tools, and we want to be transparent about our expectations as you navigate our interview process
Not permitted: Using AI assistance during conversational interviews
Permitted: Using AI tooling for take-home assessments. Please flag where and to what extent it was used in your take-home. Your submission will not be penalized for using AI as long as it is done honestly
We use AI tools to help manage our recruitment process efficiently and fairly. Specifically:
Ashby helps us review inbound applications by surfacing candidates who best match the role requirements we’ve defined. This tool does not make hiring decisions; it helps our team prioritize which applications to review first
Granola takes notes during our interview calls so our team can focus on the conversation with you
All hiring decisions are made by humans. Our team reviews applications, conducts interviews, and makes final selections
