Selected work
Experience Digital
Cross-functional engineering work spanning legacy modernization, backend delivery, infrastructure automation, and cloud data platform architecture across application and platform layers.
- Modernized legacy product surfaces while keeping compatibility with existing systems and database constraints.
- Improved application performance and delivery flow through more disciplined frontend, backend, and platform work.
- Moved into DevOps and platform work across CI/CD, infrastructure automation, observability, and delivery workflows.
- Contributed to cloud data architecture and reporting systems across Azure and AWS.
Context
Cross-functional engineering across legacy modernization, backend delivery, DevOps, and cloud data platform work.
Why it mattered
Proved end-to-end range across product code, delivery systems, observability, and cloud data work without losing engineering clarity.
What I owned
- Product engineering across legacy and modern web application surfaces
- Delivery and platform work across CI/CD, infrastructure automation, and observability
- Contribution to cloud data and reporting architecture across AWS and Azure
Constraints
- Legacy systems and database realities that could not be ignored
- Delivery and infrastructure work that directly affected release speed and reliability
- Moving across product, platform, and data concerns without losing clarity
What I changed
- Modernized application surfaces while preserving compatibility with existing constraints
- Improved performance and delivery flow through better frontend, backend, and platform discipline
- Expanded into infrastructure and cloud data work that supported reporting and operational visibility
Context
Experience Digital was broad engineering work across product delivery, infrastructure, and data systems. The role started in hands-on application engineering and expanded into frontend performance, DevOps delivery, observability, and cloud data platform work.
What I owned
- Product engineering across legacy modernization and modern application delivery
- Frontend, backend, and delivery improvements that reduced product and platform drag
- Support for CI/CD, infrastructure automation, observability, and cloud data/reporting work
Technical constraints
The constraint set went well beyond feature delivery:
- legacy constraints without freezing progress
- frontend and application performance without shallow optimization theater
- CI/CD and infrastructure concerns that affect delivery speed and reliability
- cloud data architecture that had to support reporting workflows and data movement across AWS and Azure
What I changed
The work moved across several layers:
- Application modernization: Updating legacy systems, extending schemas, integrating APIs, and introducing newer application patterns with Next.js, Tailwind, Jotai, tRPC, and Prisma.
- Frontend performance: Improving React application behavior with better state and rendering discipline to reduce load and interaction friction.
- DevOps and delivery: Supporting CI/CD pipelines, infrastructure automation, observability, and cross-functional release flow to reduce operational drag.
- Cloud data platform work: Contributing to data pipelines, reporting architecture, and platform behavior for Power BI environments spanning Azure and AWS.
Why it mattered
The value was learning to move across product code, delivery systems, and platform concerns without losing engineering clarity.