Apple Hardware Engineering · EPM Interview Presentation
Chami
Rupasinghe
A product leader who builds teams, ships products at scale, and turns complexity into clarity.
Where engineering
meets strategy.
As a data and AI native product leader, I've spent 15+ years at the intersection of business ambition and technical execution. From incubating enterprise grade data platforms at Microsoft, to five ancillary revenue products at American Airlines, I turn high-stakes ambiguity into measurable outcomes.
Microsoft · 2015–Present
Azure
Principal PM Manager
2019 – Present
Incubating a product that transforms data structures using GenAI.
Microsoft Research
Principal Product Manager
2019 – 2021
Led Azure Health Data Services from Research to GA at HIMSS 2021. 7B+ monthly API requests in Year 1.
Azure
Sr. Data & Applied Scientist
2016 – 2019
Analyzed Azure consumption patterns to devise share shift strategies. Azure churn model (F1: 0.904); partner ranking algorithm for ~3,000 Azure sellers.
Sales
Technical Sales Professional
2015 – 2016
Attained 104% of target on a $36M portfolio of 82 enterprise accounts.
American Airlines · 2005–2013
Ancillary Revenue Products
Sr. Product Manager
2010 – 2013
Incubated 4 products with $41M ARR.
AAdvantage Loyalty
Sr. Marketing Manager
2007 – 2010
Launched AA's most exclusive elite tier and revenue driving loyalty products.
Field Operations Planning
Financial Analyst
2005 – 2007
Developed staffing analysis and optimization tool, saving $4M annually.
Education
Duke University, Durham NC
MBA — Fuqua School of Business
Austin College, Sherman TX
B.S. Economics & Finance
What I bring.
What I'm here to learn.
What I Can Bring
Platform experience building tools for engineers
At Microsoft I build systems used by enterprise developers, which aligns closely with building internal platforms that support hardware engineering teams.
Software development excellence at scale
Experience operating in large engineering organizations with complex dependencies, structured planning, and disciplined delivery.
Thriving in ambiguity
Experience incubating new platforms and navigating unclear problem spaces while bringing structure and alignment.
What I'm Excited to Learn
Closer proximity to hardware innovation
The opportunity to enable the engineering systems that support the design and development of Apple's hardware products.
Hardware–software co-design
Learning how tightly integrated engineering teams collaborate to deliver Apple's product experience.
Apple's culture of product craftsmanship
How deep technical work across hardware and software translates into simple, elegant products.
Launching Azure Health Data Services
at HIMSS 2021.
"Ship to the world's largest healthcare conference — or miss a once-a-year market window."
The Product — Azure Health Data Services
A cloud-native healthcare data platform that exchanges clinical, imaging, and device data and exposes it through standards-based APIs — powering the Microsoft ecosystem and customer-built applications as systems of engagement.
- —Clinical Data — FHIR API for interoperability
- —Imaging Data — DICOM API for interoperability
- —Device Data — Proprietary standards transformation
- —Compliant & secure — HIPAA, ISO 27001; 99.9% uptime
Customer Segments
Hospital systems · Insurers · Medical Device Manufacturers
Use Cases
Patient Intelligence · Clinical Research · Remote Monitoring
Me + My Team
Responsibilities: Product strategy + Program Execution.
Drove clarity for internal and external teams, established repeatable processes that scaled across six engineering teams, eliminated overhead by sourcing all tracking directly from DevOps, and continuously surfaced risks early so leadership could make decisions — not be surprised by them.
- Release Manager — Program execution: QPR (set OKRs), MBRs, Release Management, T-minus tracking
- Two Data Engineers — Product Market Fit through product telemetry and business metrics
- Technical Writer — Technical documentation
- Program Manager — User Interface
Internal Stakeholders
- Product
- Engineers x56 (across 6 engineering teams)
- Technical Program Managers x10
- Executives x3
- Privacy, Compliance, Legal
External Stakeholders
- Price - Business planning, Finance, Commerce
- Placement - Sales (training and enablement)
- Promotion - Marketing (PR content, Launch plan)
Three fires.
Simultaneously.
New Azure Mandate Redefines Product Scope at T-Minus 6 Months
A company-wide security edict ensuring security consistency across all services forced a complete redefinition of GA scope. Smaller, less mature teams lacked spare capacity to absorb the new requirements without cutting committed features entirely.
01Last-Minute Name Change Cascades Across Every Asset
"Health Data Platform" was rejected by Marketing LT — "platform" was reserved for Azure. Rippled through: all docs, press release, domain naming, landing page, and all customer decks — weeks from launch.
02Billing Not Finalized by Launch Readiness Date
Resource constraints impacts if the billing engineering would be ready for launch, creating high commercial risk: sellers could not confidently quote, buyer conversations would stall, and event-day messaging risked customer confusion.
03Every risk tracked.
Every mitigation owned.
| Risk | Impact | Mitigation Path | Level | Status |
|---|---|---|---|---|
| Unplanned Security Features Engineering Risk |
Change the product or move launch date | ① Reprioritize backlogs via updated Pugh Chart weights ② Borrow capacity from sister teams ③ Negotiate APEX deferrals for immature services |
High | Resolved |
| Hero Features at Wire Marketing Risk |
Marketing BOM built on uncertain foundation | Each team got at least one hero feature and development went down to the wire; parallel BOM track with pre-agreed 48hr publication cycle triggered on feature confirmation | High | Resolved |
| Product Name Change Marketing Risk |
Cascades: all docs, web, press, domain | Asset inventory → single source of truth → sequenced updates: domain → docs → marketing. Tracked as DevOps work items. | Med | Resolved |
| Missing Billing Commercial Risk |
Sellers can't quote; customer confusion at HIMSS | No pricing announced at launch, and customers use the product for free. Private disclosure of future pricing enabled sales. Billing / pricing was announced three months post GA. | Med | Accepted |
I move an organization
by pulling, not pushing.
Clear Strategy
Semester-level LT strategy design. Every team knew the destination, their lane, and the definition of done — before the first sprint started. Ambiguity is the enemy of velocity.
Minimal Overhead Process
QPR designs the quarterly engineering plan. MBR reviews its progress. All output flows directly from DevOps — no duplicate tracking, no separate spreadsheets, no wasted cycles.
Over-Communicate
T-minus weekly dashboards. End-of-sprint check-ins. Release notes. A newsletter. R/Y/G status always visible — no one is ever surprised, especially not senior leadership.
A battle plan for every
level of the org.
Quarterly
QPR
Engineering plan design; OKR setting; resource & dependency mapping across all 6 teams
Monthly
MBR
Progress review with exec leadership; trade-off discussions; risk escalation with recommended decisions
Per Sprint
Prioritize + Demo + Release
End-of-sprint demos; release notes published; backlog refined with CAB customer feedback
Weekly
T-Minus Update & OKR review
R/Y/G dashboard all workstreams; blocker triage; milestone countdown for major releases; OKR progress review
Monthly API requests — in the first year of general availability
✓ On Time
Shipped at HIMSS 2021
Hard deadline met
6
Engineering Teams
Coordinated to GA
→ Azure
Graduated from
Microsoft Research
Azure Health Data Services shipped on schedule at HIMSS 2021, exceeded all adoption projections in Year 1, and successfully transitioned from Microsoft Research into Azure — validating both the product strategy and the operating model used to build it.
Ready to build something
extraordinary at Apple.
I bring the technical depth, stakeholder fluency, and relentless execution mindset this EPM role demands — and I'm excited to bring that to Apple Hardware Engineering.
Name
Chami Rupasinghe
Location
Austin, TX
Phone
903-744-6200
crupasinghe@gmail.com
linkedin.com/in/rupasinghe