First Commit
2012
Software engineer
Web developer at Rapid Development Group in Grand Rapids: data migrations and payment integrations. Everything else on this map runs on that line.
Route map
Blue line: building software Red line: leading engineers Map not to scale
Chromatic
2015 – Mar 2021
Software Developer, then Senior Software Developer
Client projects built side by side with their designers and agencies, and later a data migration on AWS Lambda.
Lead Developer
Chromatic · Mar 2021 – May 2022
Lead Software Developer
My first time leading: one or two engineers per project, and an accessibility audit for an arts college.
Red line joins here
Arcadia
May 2022 – Apr 2023 · Climate tech
Engineering Manager
A team I was on needed someone to step up. It wasn't a plan, but it's where I've stayed. My first team was a senior-heavy group of five, through a restructuring.
Gen Digital
Engineering Manager
Five engineers who own how partners in MoneyLion's marketplace get set up, paid and reconciled. Real money, so we move fast and carefully.
We went from weekly releases to several a day and retired a legacy billing system. AI is built into how we write, review and grow.
How I run the line
- Engineers should know why their work matters.
- When the why is clear, ownership follows.
- I stay close to the code.
- Including the AI tools I ask the team to use. I use them first.
- AI-written code meets the same bar.
- Same review, same tests. Using it well is part of everyone's goals.
- Speed and quality don't trade off.
- Good process makes both possible.
- Watching someone grow is still what gets me.
- A promotion, a hard problem cracked, an engineer finding their voice.
- Assume good intentions first.
- Being a father of two taught me there's usually more going on.