Founding full-stack engineer
Creation Workspace Services
CWS was a full-stack internal platform and AWS serverless API ecosystem built to reduce friction between creation, design, and development teams. It became the technical spine for workflows supporting 5,000+ daily users.
An internal platform for creation workflows.
CWS was designed to make complex creator workflows more legible and less fragmented. Rather than relying on ad hoc handoff paths, the platform centralized workflow states, API-backed interactions, and the connective tissue between teams moving from concept to production.
Design-to-development handoff was too slow and too opaque.
The teams involved in creation needed a system that reduced ambiguity, improved flow between roles, and exposed a cleaner interface for the work moving through the pipeline.
Full-stack system design with product and workflow judgment.
Architecture
Defined the platform shape across front-end surfaces, backend services, API design, and data movement.
Workflow logic
Translated real team operating needs into usable system states, interfaces, and handoff patterns.
AWS backend
Used Lambda, API Gateway, and DynamoDB to support a scalable internal-service model with clear boundaries.
Delivery
Helped turn an innovation-center concept into a working internal platform with daily usage and operational relevance.
A serverless API backbone with workflow-facing UI.
- React front end for internal user workflows and platform surfaces.
- Node.js services and AWS Lambda functions for business logic and API orchestration.
- API Gateway as the shared entry surface for internal service communication.
- DynamoDB for high-availability workflow and state-backed system interactions.
Optimize for reliability, speed, and operating clarity.
- Choose serverless primitives that reduced infrastructure drag while supporting scale.
- Make workflow state explicit so handoffs were visible rather than informal.
- Bias toward APIs and structured interfaces instead of one-off process exceptions.
Constraints
Internal platforms need adoption, not just correctness. The system had to fit real team behavior and enterprise expectations.
Impact
The platform reduced design-to-development handoff time by 70% and supported 5,000+ daily users across creator teams.
Next
If I revisited it, I would push further on workflow analytics and clearer visibility into bottlenecks by team and stage.