Yunus Emre Alpak

Engineering quietly at the edges of inference, scheduling, and the systems that hold them together.

I'm a software engineer. For the last several years I've worked on the machinery underneath large language models — the routers, schedulers, and storage layers that keep inference cheap and predictable at scale.

Before that I spent a long time writing client software, mostly on Flutter. The two halves of the job inform each other more than I expected: latency budgets, the cost of a wrong abstraction, the value of plain code.

I write here when I have something I'd want to read myself.

Essays · Selected

Work

I work on inference infrastructure — request routing, GPU scheduling, and the storage shapes that sit alongside them. Most of what I build is invisible to the people it serves, and I prefer it that way.

Earlier in my career I worked on client software, including a long stretch in Flutter; that work taught me to take latency, accessibility, and the small textures of an interface as seriously as anything on the server.

Open to thoughtful conversation, occasional advising, and rarely a new seat. Write to me — I read everything.