Backend & APIs
Backend APIs
I design and build backend APIs where contracts, validation, business rules, failure paths, and operational guardrails stay visible to the next engineer.
Approval workflow API walkthrough
Guided workflow scenarios where request and response behavior, implementation excerpts, and tests stay in the same line of sight.
Open the evidenceScope
Specific capabilities
The narrower skills inside this area.
Examples
Where this shows up
Public examples and pages that connect the skill to code, decisions, or delivery work.
Can lead and explain
There is enough structure, tradeoff reasoning, and explanation to evaluate leadership depth.
- Approval workflow API walkthrough
Guided workflow scenarios where request and response behavior, implementation excerpts, and tests stay in the same line of sight.
- Operating an event-driven workflow under failure
Models submit/status API behavior where idempotency, stored state, and failure signaling remain visible after intake.
Professional context
Where I have used it
Across product and consulting work, I have built backend APIs in both C#/.NET and TypeScript/Node.js environments. The work usually sits where contract design, validation, workflow rules, persistence, integrations, and operations all have to agree, so I do not treat the API surface as a thin wrapper over data.
Same area