Cloud & DevOps
Infrastructure as Code with AWS CDK
Used AWS CDK to turn repeated infrastructure wiring into reusable TypeScript and Go patterns that teams could adopt without relearning every AWS detail.
CDK construct library for durable serverless workflows
Connects reusable construct boundaries to developer ergonomics, generated AWS resources, and CDK assertion tests.
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.
- CDK construct library for durable serverless workflows
Connects reusable construct boundaries to developer ergonomics, generated AWS resources, and CDK assertion tests.
- Operating an event-driven workflow under failure
TypeScript CDK stack and assertions for API Gateway, Lambda handlers, DynamoDB, queue/DLQ, alarms, dashboard, and scoped IAM.
Production delivery
This connects to professional delivery experience, with confidential details left out.
- Redis/ElastiCache platform caching across serverless apps
Reflects production CDK/IaC work around shared infrastructure patterns, custom-resource-style provisioning, generated secrets, and app-facing outputs.
Professional context
Where I have used it
In production platform work, I worked on custom CDK constructs that helped developers deploy standardized cloud patterns with less AWS-specific expertise. The balance was keeping the defaults useful without hiding the infrastructure shape completely.