Personal Readme
Beyond what's on my resume, here's a little bit more about me, my personal life, as well as my approach to the many different parts of my job as an Engineering leader.
About Me
I'm a husband to my wife Michelle, a father to our two children Theodore and Olivia, and our dog Laney.
I love listening to all kinds of music, anything with a catchy beat or fun lyrics. Live music is the best, though I haven't been able to go to any shows since before the pandemic.
I'm an avid golfer. My handicap is ~12, and I've got a personal goal to reach a single digit handicap at least once in my life.
I enjoy delicious food, craft beer, and whiskey-based cocktails.
I was born in Hobart, went to school in Perth, and shortly after graduating from University I moved to Seattle.
I really enjoy travelling and experiencing different parts of the world. My favourite places I've visited are Iceland, Italy, and Singapore.
My Working Style
I really enjoy cross-functional collaboration between leadership, product, engineering, and user experience members of the organisation.
I take an empathetic perspective on all situations and decisions I need to make.
I strive to build strong, highly functioning working relationships between my cross-functional teams.
I believe in giving all members of the team an opportunity to show their strengths, as well as grow in areas of needed improvement.
I work with my direct reports and skip-level reports to coach and guide them in the careers, through mindful goal-setting and technical growth planning.
I enjoy high-bandwidth brainstorming and solutioning around problems the team is facing.Â
My Communication Style
I believe in being transparent and honest with my cross-functional teams.
I use inclusive language to respect how everyone identifies, as well as to respect everyone's beliefs.
I believe in creating space for anyone and everyone to freely and safely share thoughts and ideas.
When communicating with leadership, I try to best understand their communication style so that I can best present information to them.
I lean on async communication very heavily in my day-to-day, using apps like Slack for 1:1 messaging as well as topic-based discussions.
Email is always open on my computer, but checked less regularly than Slack.
My Approach to Leadership
As a leader my job exists first and foremost to help, support, and serve my team. Unblocking them, coaching them, connecting them with others, making decisions, prioritising work, or getting in there and problem solving with them... it all helps the team win.
I partner closely with executive leadership, product management, UX, and data scientists to help design, build, and deliver impactful results towards achieving company goals.
Create a psychologically safe space for everyone to freely and openly express themselves and their ideas.
Be vulnerable, share highs and lows. This inspires trust and further helps to support a safe space for discussions.
When setting strategy or execution plans, I always start with why. Creating a common understanding of how our org's strategy ladders up to company success will inform priority of work teams picks up, and inspire new ideas to help us achieve success.
I will freely admit that just because I'm a leader doesn't mean that I know everything, and happily bring in other technical experts to the conversation to help steer the team in the right direction.
When working with the team in meetings, I'll often try to find natural breaks to summarise the ideas and steer the team to a decision. "So, what I'm hearing is ____" is very effective in helping the team achieve mutual understanding and alignment on the path forward.
I always make sure to let those I work closely with know they're always free to block time on my calendar to connect and chat about whatever is on their minds.
My Approach to Engineering
I work with my teams to find an agile development process that helps predictably deliver high priority projects, and easily accommodate shifts in priority.
I believe in a design review process that engages a technical audience from within the team as well as outside the team, where the problem space can be reviewed along with possible solutions and their pros/cons.
There are many tools in the engineering toolbox, and teams should always be willing to objectively explore what technologies may exist to solve problems (along with their pros/cons).
TDD along with a streamlined CI/CD pipeline helps to improve team velocity without sacrificing quality.
Building in feature flags or A|B tests for deployments enables both measurement of success as well as fast ways to rollback if needed.
Projects aren't complete without adequate design documentation, runbooks, and monitoring.
I help my teams establish living working agreements to provide clarity around how the team defaults in all aspects of software engineering, and allow the developers on the team to work together harmoniously.
Information (design decisions, FAQs, troubleshooting docs, MVP specs, etc) related to projects needs to be easily discoverable by anyone interested.