Projects are evidence, not the identity. This selection shows where I changed the direction of a difficult system, helped a team take on harder work, carried product responsibility, or built in public long enough for the work to be examined.
Professional work where the important boundary crossed implementation, product behavior, operations, or team capability. Private architecture and current-employer work remain excluded.
Learn the unfamiliar stack, then make it usable by the whole team.
Worked on customer-facing and internal banking systems while turning new frontend and cloud approaches into shared delivery practice.
Founder-level product responsibility, including what the software proved and what it could not solve for the company.
Developer products, maintained public work, and accepted contributions inside existing architectures. Metrics are dated and scoped instead of combined into one score.
Smaller public chapters that support the trajectory without being stretched into full case studies.