Who is the person behind all of this?
I build systems that help people do their best work.
I’m Irin Berry, an engineering leader, software engineer, educator, and lifelong game developer.
For more than twenty years, I’ve worked at the intersection of people and technology—building games, engineering platforms, development tools, teams, and organizational systems.
My career has taken me from writing gameplay code to leading engineering organizations. Along the way, I discovered that the problems I find most interesting are rarely just technical problems. They’re the places where technology, process, and people intersect.
That realization has shaped how I approach engineering today.
MY STORY
I started by building games.
I learned to build the systems behind them.
I entered the game industry as a software engineer because I loved solving technical problems and making things people could experience.
Over the years, I worked across gameplay, architecture, tools, platforms, and technical leadership on more than 30 shipped titles. As my responsibilities grew, so did the kinds of problems I was solving.
A difficult build process affected every engineer using it. An unclear career ladder affected whether people understood how to grow. A new technology only became valuable when people understood it, trusted it, and could incorporate it into their work.
Eventually, I realized much of my career had been driven by the same instinct:
Find the friction that makes good work harder, understand why it exists, and build something better.
HOW I THINK
Technology is the mechanism.
People are the outcome.
I care deeply about good software architecture, but engineering excellence doesn't end with the code. The systems surrounding engineers matter too.
How people learn. How teams communicate. How decisions are made. How software gets built and shipped. How engineers grow and leaders develop.
That's why my work has expanded into developer experience, engineering leadership, organizational design, AI enablement, and education.
They may look like different disciplines. To me, they're different ways of answering the same question:
How do we create an environment where people can consistently do great work?
LEADERSHIP
Build capability, not dependency.
One of the most important lessons I've learned as a leader is that being needed isn't the same thing as being effective.
I don't want to be the person every decision has to pass through. I want teams to have the context, tools, confidence, and authority to make good decisions themselves.
That means coaching rather than prescribing, and creating clarity instead of control. I want to build systems that continue working when I'm no longer in the room.
A successful leader shouldn't become the most important part of the system. They should help make the system stronger.
WHERE I AM TODAY
Still building. Still learning. Still teaching.
Today, I build games and engineering systems, teach software engineering and game development, coach engineers and technical leaders, and explore how AI can meaningfully improve the way we work.
The tools have changed considerably since I started my career.
My motivation hasn't.
Every day, I work to make tomorrow easier.