01 / The challenge
Where the work began.
Enterprise delivery means working with existing platforms, distributed content teams, accessibility expectations, and real release constraints. The software must serve both the person using the site and the person maintaining it.
02 / The approach
Enterprise engineering, end to end.
I built and maintained Java/Sling, JavaScript, React, and AEM implementations, contributed to discovery and UAT, led demonstrations and training, and mentored developers. I also led work on a reusable Digital Front Door accelerator for future engagements.
03 / Engineering decisions
The choices that mattered.
Give authors useful control
Authorable components, dialogs, content policies, and reusable modules let content teams manage experiences without relying on code changes.
Build access into the interaction
Keyboard flow, focus management, semantic markup, and screen-reader behavior are engineering concerns throughout implementation.
Reuse without hardcoding the client
Provider and location search, filtering, sorting, and a data abstraction layer support reuse across engagements and data sources.
04 / The result
What shipped.
- Delivered enterprise AEM components, responsive navigation, authoring features, and accessibility improvements.
- Built reusable provider and location modules for the Digital Front Door accelerator.
- Shipped AEM AI Starter Kit dashboard auto-refresh and metadata scoring with 16 automated tests.
- Promoted from Associate Consultant to Consultant within six months of joining Slalom.
Selected work across several Slalom engagements and internal accelerators. Accessibility improvements are described without claiming blanket site-wide compliance.
05 / What stayed with me
The most useful systems accommodate the people, constraints, and workflows that already exist.