Last 18 months
Content-platform integration with the data platform
Engineering Manager · Tech Lead
Drove the integration between an enterprise content platform and the company-wide data platform — designed the API contract, navigated four review boards, shipped the first stable release across three substrates.
- First stable release shipped across three cloud substrates
- Adopted by partner teams in the first quarter post-GA
- Cross-team recognition from peer platform leads at multiple Salesforce business units
The setup
Two large platforms inside the same company that needed to talk — and a hundred small reasons they currently could not. Different identity models, different data schemas, different release cadences, different on-call rotations.
The work was less engineering than politics-with-a-spec: align the spec, then make the engineering boring.
How I sequenced it
- API contract first. Spent the first six weeks on a written contract — endpoints, error model, identity flow, SLA. No code yet.
- Architectural review. Co-authored the architectural proposal. Defended it across four review boards. Each one sharpened the design — the version that shipped was meaningfully better than the version we walked in with.
- Substrate-by-substrate rollout. Did not ship to all three at once. Substrate A first, learned, fixed, then B, then C.
- On-call merger. Negotiated a shared on-call rotation between the two teams for the integration surface. Pages now go to whichever team is actually closest to the cause.
What was hard
Maintaining momentum across three quarters when the fastest-moving engineers wanted to ship and the most senior reviewers wanted to debate. The cadence I held: weekly demo of something, even if small. Demo > debate.
What it changed
The two platforms now ship integration features without the full review-board choreography for each one. The first release was the expensive one; everything since has been incremental.