Sayin
I founded Sayin and served as its first founding engineer, which meant there was no existing architecture to inherit and no one else to escalate a design or implementation question to. Over the years I have built a team around me whose expertise and insights I respect and admire. The problems that we have sold in delivering this product has meant solving many common and painful problems with building safe and scalable platforms in healthcare. Here is a small selection of the varying solutions that I have implemented.
Microsoft
Windows Settings ships to over a billion devices, and almost none of it is built by one team. Platform work at that scale means your real users are other engineering teams: your control's API becomes their constraint, your migration becomes their quarter, and your undocumented setup step becomes their week. Over three years I built homepage components that partner teams built on top of, characterized the cost of a hosting architecture nobody had tried, stabilized a multi-team migration through release, and rebuilt the test framework that guarded all of it. The through-line is that the highest-leverage work was usually the work that made someone else's work possible.