Full-Stack Builder (Python) —

Specification-Driven +AI

Mission
Operate with high autonomy to turn clear specifications into production systems fast. Maintain
an observable, auditable trail of delivery (code, tests, demos, and metrics) without heavy
supervision.

Key Outcomes:
Ship features that meet written acceptance criteria on time and budget.
Work independently: break down specs, estimate, unblock yourself, and escalate risks early.
Keep services testable, observable, and easy to change.
Maintain a verifiable delivery trail: PRs linked to tickets, passing CI, change logs, weekly
demo recordings, and live dashboards.
Clean handovers: runbooks, on-call notes, and support plan ready.

Responsibilities:
Specs first: draft/maintain OpenAPI, JSON Schemas, and Gherkin tests from discovery notes.
Build: implement FastAPI endpoints, data models, and a small React/Next.js UI; background
jobs & integrations with idempotency/retries.
Quality gates: Pytest/Playwright automation; contract tests; schema-based fuzzing; CI checks
for breaking changes.
AI assist (pragmatic): use LLMs to draft specs, test cases, seed data, and docs with human
review & evals.
Delivery visibility: keep tickets current; small PRs linked to criteria; weekly demo &
changelog; dashboards/alerts for shipped features.
Containerized dev/prod; secrets management; RBAC; basic cost hygiene.

Default Stack:
Backend: Python, FastAPI, SQLAlchemy, Pydantic; Postgres; Redis; Celery/RQ
Frontend: React/Next.js (TypeScript)
Testing/CI: Pytest, Playwright, Spectral/oasdiff, Schemathesis; Docker; GitHub Actions
AI tooling: LangChain/LangGraph (basic), vector store (pgvector/FAISS), prompt/eval
harness

Must-Have Experience:
3–7 years building production APIs/web apps in Python (FastAPI/Django/Flask).
Strong SQL & migrations; performance basics (indexes, N+1).
Auth/OIDC, RBAC; awareness of OWASP Top 10.
Automated testing + CI/CD; API integrations; webhooks with retries/backoff.
Proven self-management in an async environment: planning weekly increments, calling out
blockers, and keeping stakeholders informed.
Comfort keeping code « specs in sync.