Interview Resources
Skills: React, SQL
Behind every report is a pipeline that searches the open web, reads what it finds, extracts candidate questions, grades each one by the strength of its evidence, and throws away the rest. It runs for minutes, costs real money per run, and has to produce something defensible at the end or we refund the credit. This role owns that pipeline. You will work on retrieval quality, prompt and schema design, the grading logic that decides whether a question is evidence-backed or merely inferred, the budget tracker that stops a run before it burns a customer's balance, and the job infrastructure that will move this work off the request path. Back-end leaning means the centre of gravity, not the boundary. You will still open React files, because a pipeline change that nobody can see in the report is not finished. Own the research pipeline end to end: search, extraction, grading, caching, and the report artefact it produces. Improve output quality with evaluations rather than vibes. Build the harness if we do not have the one you need. Keep cost per run predictable: budget tracking, model selection, caching, and hard stops that fire before the money is gone. Move long-running work onto a durable queue with retries, idempotency, and cancellation that actually cancels. Design and migrate the Postgres schema, and keep migrations safe to run against production traffic. Build and maintain the credits ledger, payment webhooks, and the reconciliation that catches it when they disagree. Instrument everything. When a run degrades at two in the morning, the logs should already answer why.
Sign in to see the original posting
Browse more developer jobs on RoleBurst