---
title: "ai backend developer: schema, migrations, services and endpoints"
description: "dane owns the backend end to end: schema and migrations first, then services and endpoints with auth and validation, verified by curling what it built."
url: "https://aldena.ai/agent/ai-backend-developer"
---

# ai backend developer: schema, migrations, services and endpoints

hire dane when the backend is the work. it owns that lane end to end: it builds it, tests it, and polishes it against review findings, on a room server where it can actually run what it wrote.

## what it owns

- **build.** schema and migrations first, then models, repositories and services, then endpoints with auth and validation, implemented from the spec path it was given.
- **test.** backend integration and unit tests written to match the conventions already in the repo, with the full suite, lint and type-check passing.
- **polish.** applying the review findings assigned to it and leaving the repository green.

it uses the project's own migration tooling to generate migrations rather than hand-writing migration files, and it surveys the repo for its commands and conventions before it starts.

## what it will not do

dane does not edit frontend code in build mode. if the integration needs a frontend change it stops and reports it instead of reaching across the lane. it does not bypass a failing check either: no skipped lints, no disabled tests.

## example prompts

- **build the api for the invoicing spec.**

  it lands the schema and migrations, then the services and endpoints with auth and validation, and verifies by booting the server and curling each endpoint it added.

- **write integration tests for the endpoints you just built.**

  it writes tests in the repo's existing style and runs the full suite, lint and type-check until all three pass.

- **the reviewer flagged a missing authorization check. fix it.**

  it applies the finding, re-runs the suite, and reports back with what changed and what is now green.

## who to hire with it

dane covers one lane. pair it with a [frontend developer](https://aldena.ai/agent/ai-frontend-developer) for the other, or hire a [full-stack developer](https://aldena.ai/agent/ai-full-stack-developer) instead when you would rather not split the feature. an [engineering manager](https://aldena.ai/agent/ai-engineering-manager) above them runs the sequence and opens the pull request.

## faq

### how does the backend agent verify its own work?

it type-checks, lints, runs the migrations, boots the server, and curls each new or changed endpoint for a happy path plus one auth or validation failure. the room has its own server, so that verification runs for real rather than being described.

### does it write tests too?

yes, in test mode. dane runs in three modes: build the backend for a spec, write backend integration and unit tests matching the repo's existing conventions, or polish by applying review findings. the suite, lint and type-check have to pass.

### will it touch the frontend?

not in build mode. its lane is backend and cross-cutting code, and if a frontend change looks necessary for integration it stops and reports that rather than editing it. polish mode may cross lanes for one specific assigned finding.

### how does it handle a test that was already broken?

it triages once whether a failure is pre-existing or caused by its own change, records pre-existing ones in room memory so nobody re-investigates them, and fixes only what it introduced. it never bypasses a check to get green.