Cloud and API Consulting Bridge Case Study
This period bridged earlier enterprise consulting work into later platform roles by combining cloud data-pipeline work for Microsoft with customer-facing API delivery for Starbucks licensee systems.
Impact Signals
Core Delivery
Problem
The work sat between classic enterprise consulting and later product-platform ownership. It required moving comfortably across client contexts, cloud tooling, data-processing workflows, and external-facing APIs that supported real business operations.
My role
At Slalom, I provided technical leadership on cloud and API projects for clients including Microsoft and Starbucks, helping deliver both internal data-platform automation and customer-impacting service integrations.
Key engineering decisions
- Built Azure pipelines and Cosmos Scope scripts used to process Azure usage metrics in Microsoft's internal big-data environment.
- Developed REST APIs used by thousands of Starbucks licensee locations to support customer rewards earning and redemption.
- Worked in a delivery mode that had to stay pragmatic across cloud tooling, API contracts, and client-specific operational constraints.
Outcome
This period sharpened the transition from enterprise delivery tooling into cloud service and API work, directly setting up the move into later backend platform leadership at Starbucks and then Oracle.
Why This Work Still Matters
The bridge matters because it connects two halves of the career that would otherwise look disconnected. It shows the path from delivery tooling and application modernization into cloud data processing, service APIs, and eventually high-scale platform ownership.
It also reflects a durable pattern in the broader career: the most useful engineering growth often happens in the transition zones where infrastructure, delivery workflows, and product-facing APIs all meet.