Snyk

Snyk was in a scaling phase, and the engineering problem was as organizational as it was technical. Monolithic legacy logic made new ecosystem coverage harder to add and created coordination costs between teams. The work required identifying boundaries that could support independent extension without obscuring responsibility for the system as a whole.

My contribution combined staff-level architecture guidance with implementation. I advised the VP of Architecture on cross-team improvements, designed and built a plugin-driven microservice architecture to replace the monolithic logic, and integrated CocoaPods specifications into vulnerability scanning to extend coverage of the iOS ecosystem.

This work sharpened my preference for boundaries that match how teams need to reason and collaborate. Modularity is useful when it reduces coordination cost and makes ownership clearer; distributing a system without those properties only redistributes the confusion.