THE ROLE:

We're looking for a backend engineer who wants to learn Go and build production systems. You don't need to be a Go expert but you should have solid programming fundamentals and a genuine curiosity about how backend systems work: databases, APIs, caching, deployments.

You'll work alongside the backend tech lead, picking up tasks across the stack writing API endpoints, building database queries, setting up integrations, fixing bugs, and gradually owning entire services. We'll teach you the stack; you bring the drive.

WHAT YOU'LL DO:

- Write backend services in Go API endpoints, business logic, database interactions, and background jobs

- Work with PostgreSQL daily: write queries, design simple schemas, understand indexes and migrations

- Build and consume REST APIs following established patterns proper status codes, error handling, request validation

- Write unit tests and integration tests for your code tests are not optional here

- Learn Redis caching patterns and implement them for high-read flows like product catalog and pricing

- Help integrate third-party services: payment gateways, notification systems, search engines

- Participate in code reviews both giving and receiving feedback and improve the codebase as you go

- Learn infrastructure basics on the job: Docker, CI/CD pipelines, Cloud Run deployments, structured logging

- Debug production issues using logs, traces, and metrics and build the instinct for where to look first

YOU SHOULD HAVE:

- Solid programming fundamentals in any language Go, Python, Java, C++, or Rust. You understand data structures, algorithms, and how to write clean, readable code

- Basic understanding of how the web works: HTTP methods, status codes, request/response lifecycle, JSON

- Some exposure to databases SQL queries, table design, joins. Doesn't have to be PostgreSQL specifically

- Familiarity with Git branching, pull requests, merge conflicts, commit hygiene

- Willingness to learn Go if you don't already know it we care about fundamentals more than specific language experience

- A debugging mindset you read error messages carefully, form hypotheses, and test them systematically instead of changing things randomly

- Intellectual curiosity you read documentation, explore how things work under the hood, and ask good questions