Expel · Software Engineer · Prior role
Production API surface
Expel Workbench API
Helped grow a production REST API that served both internal platform needs and external customer integrations.
The problem
Expel needed one API surface that internal teams and customers could both depend on. Early endpoints worked, but security, consistency, and scale became harder as integrations multiplied.
What I worked on
Built and evolved endpoints, tightened access control, and supported customer automation use cases that later influenced platform features.
Key decisions
Followed JSON:API conventions, enforced RBAC at the boundary, and split responsibilities so a growing route surface stayed testable and observable.
How I handled failure
Tracked load and latency for mixed internal and external traffic, and treated the public docs as part of the product contract.
Result
Helped evolve the API into a documented integration surface with clearer semantics, access control, and operational visibility. Public docs remain the reference for supported behavior.
Evidence
Public API documentation
Customer-facing reference for the Workbench API.
Technologies
Screenshots
