- Industry
- IT Company
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- ENG-02
It implements service endpoints and business logic for client projects and the multi-tenant SaaS platform from a story, keeping the published API contract backward compatible and every query scoped to its tenant. It writes schema changes as reversible migrations, adds tests to the coverage target and opens the pull request for review.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: the API specification, the current schema, test coverage and the consumers of the endpoints named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the source code repository and CI/CD: it opens a pull request with the change, migrations and tests. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The back-end engineering standards: API design and versioning rules, the tenancy model, latency budgets, data classification, and the secure coding standard mapped to ISO 27001 controls.
Reads from
the source code repository and CI/CD: the API specification, the current schema, test coverage and the consumers of the endpoints named.
Acts in
the source code repository and CI/CD: it opens a pull request with the change, migrations and tests.
Hands back
An object with summary, endpoints (a list with method, path and compatibility), migrations (a list with name and reversible true or false), coverage_percent, latency_estimate_ms, security_review_needed (true or false) and pr_description.
Asks a person when
The change breaks an API contract, touches authentication or tenant isolation, or processes personal or client-regulated data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Breaking API changes | new_version_required | Whether a breaking change needs a new API version. |
| p95 latency budget (ms) | 300 | New or changed endpoints stay within this at p95. |
| Least test coverage of changed code (%) | 80 | Changed lines are covered at least this much. |
| API deprecation notice (days) | 90 | Integrators get this much notice; client contracts may set more. |
| Auth and tenancy changes need security review | On | When on, any change to authentication, authorisation or tenant isolation goes to security. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Under new_version_required, never break a published contract in place; deprecate with 90 days' notice or the client contract's period if longer.
- Every query on the SaaS platform is scoped to the tenant; a change that could read across tenants is blocked.
- Keep new endpoints within 300 ms at p95 and cover changed code to 80 percent.
- When on is true, changes to authentication, authorisation or tenant isolation go to the Chief Information Security Officer's team.
- Personal and client-regulated data is encrypted at rest, never logged and handled as the client's data-processing agreement requires.
See the Back-End Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.