About — Sezgin Ege

From Istanbul

I was born and raised in Istanbul, Turkey, and studied computer science there. I enjoyed the academic side of the subject and considered continuing in it, but chose to begin my career in industry. I have not ruled out returning to academic work at some point.

Madrid and Amazon

I later moved to Madrid, which remains one of the best periods of my life. There, I worked on Prime Wardrobe as it grew into a major success. It was one of my first large-scale projects and my first opportunity to take meaningful ownership of a programme operating at that scale.

I helped launch Prime Wardrobe across the UK and Japan, coordinating changes for multiple markets at the same time. My work sat directly on Amazon’s cart and checkout paths, where downtime carried commercial risk measured in hundreds of millions. Delivering those changes without disrupting checkout was a demanding engineering challenge; we did it with zero downtime.

Berlin and AWS

From Madrid I moved to Berlin and joined AWS while CodeCatalyst was still taking shape. It was a greenfield effort to simplify how teams plan, build, and deliver software on AWS. I helped turn that idea into a product and built its project-management experience, including the ticketing system.

I was closely involved in building the team, including helping hire my eventual manager. Across my time at Amazon and AWS, I conducted more than 150 technical interviews.

At AWS, I worked directly with security experts and reliability specialists, and later took on the team’s internal reliability champion role. That meant anticipating failure modes, reviewing designs critically, and helping the wider team build systems that could be trusted in production.

London and Meta

I then joined Meta and moved to London. I started in the privacy organisation, building foundational systems related to preventing cross-app data sharing and meeting the requirements of the Digital Markets Act.

Over time, I realised that my strongest interest was still developer tooling. I moved back into that space by joining the end-to-end testing infrastructure team. Today I work on company-wide infrastructure and tools that allow teams across Meta to verify their changes safely.

The kind of work I do

These roles have taken me through the full lifecycle of software: building products from a blank page, extending mature systems without disrupting them, and maintaining services where reliability matters every day. I have supported high-traffic customer systems and built the internal platforms that help other engineers support theirs.

I value being able to move between greenfield design, careful evolution, and long-term operation. Each requires a different kind of judgement, and experience in one tends to improve the others.

Current interests

I have recently been learning more about runtimes and compilers simply because I find them interesting. I do not have a grand plan for that interest, but perhaps one day it will turn into something worth building.

I am also exploring how AI agents fit into engineering workflows. The part I find most interesting is verification: if agents are going to make changes at scale, how do we test their work, contain failures, and decide when to trust the result?

Small apps

I also use AI-assisted coding to flesh out small ideas as iOS apps. They are deliberately simple: a way to try an idea, learn a different part of software development, and ship something useful or fun.

Joyful Outlines, a drawing app for children.
Just Fed!, a feed, sleep, and nappy tracker for tired parents.
ByeByeSugar!, a simple way to commit to cutting out added sugar.
Put It Back, a focus timer with a sense of humour.
RingLeap, a small one-tap arcade game.

Life now

These days, most of my time is split between work and looking after our baby daughter. Before becoming a parent, I boxed, played football, and ran regularly. Those things happen less often for now, but I still value the balance they gave me and hope to make room for them again.