D

Backend Engineer — Agent Experience

Deliveroo
Deliveroo 10 days ago
AI overview

Backend Engineer — Agent Experience at Deliveroo in Deliveroo focuses on About the team Agent Experience builds the AI-powered backend services that power agent-assist tooling on our Astra support. We sit at the intersection of LLM-backed product features and high-volume, latency-sensitive support infrastructure.

About the team

Agent Experience builds the AI-powered backend services that power agent-assist tooling on our Astra support surface — helping support agents resolve customer, merchant, and Dasher issues faster. We sit at the intersection of LLM-backed product features and high-volume, latency-sensitive support infrastructure.

What you'll do

  • Build and maintain backend services for agent-assist features on Astra, taking on feature-level work with increasing independence.
  • Translate requirements into working code: design the feature-level approach, write an RFC when the change affects other engineers, and implement it end-to-end.
  • Integrate with LLM-backed features — wiring up prompt/completion calls, handling provider responses, and validating output quality and correctness.
  • Break down assigned project work into tasks, provide accurate estimates, and keep your own progress and dependencies on track.
  • Apply AI tooling thoughtfully to your own workflow (coding, testing, review) and critically evaluate its output rather than taking it at face value.
  • Participate in code review — both giving and receiving — to help the team hold a high bar for correctness, quality, and standards compliance.
  • Collaborate with senior engineers and partner teams to clarify problem definitions, unblock yourself, and flag risks or blockers early.

What we're looking for

  • Solid backend engineering fundamentals in Go, with experience shipping and maintaining production services.
  • Exposure to LLM-powered features in production (prompt/completion integration, provider APIs) is a plus — we'll ramp you up if you haven't worked with this directly.
  • Ability to independently own feature-level work: from a written requirement to tested, shipped code.
  • Comfort working in a domain with multiple chat/support surfaces — willingness to trace issues to the right service rather than guessing.
  • Clear technical writing (RFCs for feature-level decisions) and good judgment about when to ask for help versus push forward.
  • 2–4 years of backend engineering experience, with a track record of growing ownership and scope.
Experience2–4 years of backend engineering experience
Posted10 days ago

Frequently asked questions