A timeline of my professional growth and learning progression. This isn't a resume—it's a story of how I've evolved as an engineer, the pivotal moments that shaped my thinking, and the skills I've developed along the way.
Joined Horizon3.ai to lead the Application Platform Team, moving from consumer e-commerce into cybersecurity. Inherited a 9-person team with no defined charter and spent the next two years building it into the platform layer the rest of the product depends on.
Took on leadership of 4 teams of engineers split across the Philippines and Boston at Perch. The first time managing across that much time zone distance, which meant rebuilding how work got planned, reviewed, and communicated instead of leaning on the informal, same-room alignment that had worked everywhere before.
Joined Perch as a software engineering team lead, architecting Django REST APIs for a growth team running ad campaigns and pricing across a multi-channel consumer products portfolio. A shift from Indigo's futures-and-logistics domain into e-commerce, and the first role with team lead responsibility attached from day one.
Joined Indigo Agriculture to build automations and microservices for a three-sided grain marketplace, including algorithmically determined transport pricing and execution management tied to Chicago Mercantile Exchange futures. The largest company by headcount worked for, peaking around 1,600 people during that tenure, a different kind of scale problem than a startup: navigating a much bigger organization rather than helping build one from scratch.
Traveled to Singapore to speak at QuantCon toward the end of my time at Quantopian, presenting to a quantitative finance audience outside the usual Boston/New York circuit.
Presented a webinar on working with alternative data at Quantopian, covering the standardization work behind making disparate vendor data sources usable for quantitative trading strategies.
Gave a talk at the Boston Python meetup on Python decorators, digging into how they work under the hood and where they earn their complexity in real codebases.
Joined Quantopian, a quantitative trading platform, as a software engineer building third-party data integrations. My first startup, full stop, and the place that sparked a lasting love of startups: the pace, the proximity to the actual product decisions, and the sense that the work you shipped mattered immediately rather than eventually.
Left environmental modeling for enterprise finance, building a portfolio modeler and rebalancer in C# and .NET for back-office financial advisors. A hard swing from scientific Python to enterprise .NET architecture, and a first real exposure to software built for a regulated, back-office audience.
Started as a software engineer on Stanford's Natural Capital Project, building Python-based GIS models to evaluate environmental risk and the cost-benefit trade-offs of conservation decisions. Straight out of a computer science degree, into a domain with almost no overlap to anything covered in school.