Hi, I'm Tommy

I’m a backend engineer who loves simplifying complex systems, whether that means untangling distributed services, making inventory work at scale, or turning customer pain points into elegant solutions. For the past decade, I've been deep in the ecommerce trenches: inventory management, order flows, channel integrations — the critical infrastructure that makes commerce actually work.

What drives me is building software that real people depend on. I've spent years at Square and Stitch Labs working on systems that handle millions of transactions, and I've learned that the best engineering happens when you understand both the business problem and the humans using your code. Whether I'm designing a new service boundary or debugging why inventory counts are off by three units, I approach problems with curiosity and a healthy dose of skepticism.

I thrive in cross-functional environments where I can work closely with product, support, and business teams. Some of my favorite projects have been integrations that seem simple on the surface but require deep domain knowledge to get right. I believe in clear communication, taking ownership of outcomes, and building systems that the next engineer (who might be you at 2 AM) can actually understand.

I'm also fascinated by how AI is changing our craft. I use modern tools to boost my productivity (from code generation to research) but I'm a firm believer that human judgment, code review, and understanding the business context remain irreplaceable. Technology amplifies good engineering practices; it doesn't replace them.

Places I've Worked

Square (Block)

Jul 2020 – May 2025

Senior Backend Software Engineer

Transitioned from a scrappy startup environment to enterprise software development, learning how to build systems that serve millions of merchants at global scale. I found my groove working deeply on specific problem domains. First on Channels (external marketplace integrations) and later on Platform Inventory (the foundational layer that tracks what merchants have to sell).

What I loved most was the depth of focus this environment allowed. Instead of jumping between different parts of the product, I could really understand the nuances of inventory management and external channel synchronization. I learned how to navigate the complexity of large engineering organizations, collaborate across multiple teams, and build systems that needed to work reliably for businesses depending on them for their livelihood.

Stitch Labs

Jan 2018 – Jul 2020

Software Engineer, Backend

VC-backed San Francisco startup, acquired by Square in July 2020

This was my real introduction to the startup world, and what a ride it was. Stitch Labs aimed to be the central hub for inventory, orders, and logistics for online brands. Essentially the operating system for e-commerce businesses selling across multiple channels. I joined when we were about 20 people and lived through the company's growth to over 100 employees, multiple funding rounds, and the evolution from serving small businesses to moving upmarket to larger brands.

I wore many hats and worked my way up through different roles, from debugging customer issues in support to eventually building core platform features. The team was incredibly close-knit - we were all figuring it out together, iterating on the product based on real customer feedback, and learning how to scale both the technology and the business. It taught me how to work in ambiguous environments, move fast without breaking things (most of the time), and really understand what customers needed versus what they said they wanted.

Stitch Labs

Jun 2017 – Jan 2018

Support Engineer & Technical Escalations

Triaged and performed initial investigation for complex inventory-tracking issues. Partnered with engineering for handoffs and delivered occasional small fixes, accelerating resolution time and informing backlog priorities. This role taught me to see systems from the customer's perspective and became invaluable for my engineering work later. There's nothing like customer support for learning how software actually breaks in the wild.

Early Career

2014 – 2017

Various Roles

Full-stack contract projects, Account Manager at The Resumator (JazzHR), and other early career experiences in the San Francisco Bay Area that taught me the fundamentals of building software and working with customers.

Technical Skills

Languages

  • Go
  • Python
  • PHP
  • SQL
  • JavaScript

Frameworks

  • Laravel
  • Angular
  • React

Data & Storage

  • Amazon RDS
  • Snowflake
  • Vitess
  • Redis

Cloud & Infrastructure

  • AWS (EC2, RDS, S3)
  • Kafka
  • Amazon SQS
  • REST APIs
  • RPC

Practices

  • Agile
  • TDD
  • Observability (Sentry, Datadog)
  • Oncall/Postmortems
  • Code Reviews
  • Pair Programming

Education

University of Michigan

Class of 2012

Bachelor of Arts

Ann Arbor, Michigan


Rithm School

Jan 2017 – Apr 2017

Full-Stack Web Development

San Francisco, California

How I Approach Problems

I'm comfortable learning new stacks and tools, and I care about code quality, observability, and operational excellence because those are how products keep earning trust after launch. When hunting down bugs (which I've gotten pretty good at lassoing over the years) I dig deep into the system's behavior, trace data flows, and often find that the real issue is in the interaction between components, not where it first appears.

If you're building customer-facing features that demand precise domain logic and thoughtful systems design, I'd love to connect. I believe the best software comes from understanding both the business problem and the technical constraints, then finding elegant solutions that serve real user needs.

References

Owen Wendland

Lead Principal Software Engineer at Toast

Former CTO at Stitch Labs

Zack Rosen

Staff Engineer and Tech Lead at Square

Alejandro Carstens-Cattori

Senior Software Engineer at Square

Beyond Coding

When I'm not chasing down elusive bugs or architecting data flows, I'm probably obsessing over the Cincinnati Bengals' playoff chances or lamenting another near-miss in my family's fantasy football league. Always the bridesmaid, never the bride, but I keep showing up with confidence and questionable draft picks.

I share my Brooklyn apartment with my husband and two cats who have strong opinions about my code review process (they prefer the meetings to be shorter and include more treats). In my spare time, I've gotten into the surprisingly complex world of perfume creation. Turns out there are some interesting parallels between layering scent notes and building software architecture. Both require patience, attention to detail, and the ability to iterate until you find the right balance.

After watching the early seasons as a kid, I've recently become a hardcore Survivor fan again. I love the strategy, the alliances, and figuring out how players read the room. It’s satisfying in the same way as debugging: a puzzle that rewards patience, bluffing, and the occasional bold move. When I'm not tinkering with fragrances or cheering on Cincinnati sports teams, you'll find me exploring Brooklyn's incredible food scene or swapping Survivor takeaways with anyone who wants to nerd out over game theory.