Hello!

Hi there, I’m Benjamen Pyle.

I’m a genuine and resourceful technology creator who enjoys pairing the best of people with the best of technology to solve domain-specific problems. All that means is that I love working with people to help them be their best with modern cloud-native tooling.

My background is a blend of many unique experiences that have shaped me into what I am today and is a guiding light in who I want to be tomorrow. I grew up as a competitive golfer whose sole focus was on playing golf as a profession. Those hopes were dashed in college due to injury, but I had cultivated two other passions. One of those was programming, which I learned in high school and completed my degree during college. The second was writing. If I wasn’t striving for a career in golf as a child, I wanted to be a writer.

Fast forward 20 years later and I had the realization while traveling home from a conference that I was at a point in my life that I wanted to go all-in on being a part of a technology community. Seven years ago I crossed into the AWS cloud and my curiosity was instantly peaked around solving problems with cloud-native design. Since then, I’ve become a recognized AWS Community leader in the areas of Event-Driven and Serverless Architecture

I pride myself on being able to connect individually with those whom I work with. It’s through that relationship-building that I’m able to do what I enjoy most, which is guiding technical talent to become better while balancing growth through innovation, continuous improvement and delivery

Core Values

Below are the 5 core values that I hold close and when working with me, they shine through as I’m guided by their meaning.

Selflessness

Giving of my time is something I do freely and without strings. I love to teach, mentor and guide others through their tech journey.

Authenticity

I only have one version of myself at home and work. I will be me through and through and value this in others.

Creativity

In solving problems with technology, the answer from me is always “it depends”. I try to not be attached to what I’ve done before but use it to shape what I will do in the future.

Empathy

I will never ask someone to do something I’m not willing to do myself. Building software is hard. I get that. And I want those that I’m working with to understand that. It’s vitally important to me.

Pragmatism

Technology should stay as simple as possible. I want to build things that are easy to maintain and easy to extend.

It’s through that relationship-building that I’m able to do what I enjoy most, which is guiding technical talent to become better while balancing growth through innovation, continuous improvement and delivery