{{Company name}} is hiring a Backend Engineer to build the services our product runs on. You will design APIs, model data, and keep the systems behind the interface fast, correct, and reliable as we grow.

What you'll do

• Design, build, and maintain backend services and APIs in {{Primary language / framework}}.
• Model data carefully: schemas, migrations, and queries that stay fast as tables grow.
• Write tested, reviewable code and participate honestly in code review — giving and receiving.
• Own features from technical design through deployment and production monitoring.
• Debug production issues, find root causes, and fix the class of bug rather than the instance.
• Improve performance and reliability: caching, queues, indexes, and sensible service boundaries.
• Collaborate with frontend and product teammates on API contracts that are pleasant to consume.

What we're looking for

• {{Years of experience}} years building backend systems in production.
• Strong command of at least one backend language and its ecosystem, with the fundamentals to pick up ours.
• Solid SQL and practical understanding of relational database design and indexing.
• Experience designing and evolving APIs (REST or similar) that other teams depend on.
• Working knowledge of testing practices: what to test, at which layer, and why.
• Comfort operating what you build — logs, metrics, and alerts are part of done.

Nice to have

• Experience with {{Cloud provider or infrastructure stack}}.
• Familiarity with event-driven architectures, queues, or background job systems.
• Exposure to containerization and CI/CD pipelines.
• Contributions to open-source or a codebase you can show us.

Compensation and benefits

• {{Salary range}}
• {{Benefits summary}}
• {{Location / remote policy}}

How to apply

{{Application instructions}} Tell us about a production system you built or significantly improved — the constraint that made it hard, and the trade-off you chose.