Tyler Hillery

About Me

Lifelong learner passionate about understanding the “how” and “why” behind software by peeling back the layers of abstraction all the way to the silicon. My main interests are in hardware/software co-design, computer architecture, operating systems, networking, compilers and the tooling used to understand and debug these systems in production.

Today, I’m focused on growing as a software engineer at the hardware/software boundary, combining my broad curiosity and pragmatic mindset to build and operate the systems that great products depend on.

Currently working as a Software Engineer at Supabase on the Storage team.

Co-organizer of Madison Systems meetup, a community run meetup focused on system internals.

Driven by curiosity, grounded in gratitude.

Background

I studied finance and started my career in investment operations. After 1.5 years, I realized I was more interested in computers, software, and data.

In 2021, I began teaching myself programming through books, videos and online courses. My favorite way to learn is by first getting a general high-level understanding of a topic and then diving into building projects.

After leaving investment operations, I worked in various data related roles, leveraging my finance background. While I enjoyed working with data, I often felt removed from the actual product and wanted to be closer to the systems and software creating values for users. That desire is what pulled me further into software engineering.

As I have continued building my computer science foundation as a self-taught software engineer, I have become increasingly interested into how computers work from computer architecture and operating systems to networking and compilers. That curiosity led me to talks from people like David Patterson, Chris Lattner and Bryan Cantrill, where I kept encountering a recurring theme that the free performance gains software relied on for decades are slowing down.

The future of computing will require rethinking hardware which may look increasingly specialized and heterogenous. I believe this next era of computing with reward software engineers who understand hardware.

That is the kind of engineer I am working to become. Someone who can reason across the hardware/software boundary to build software for the next era of computing.