Engineering, Product, and Education Leader

Technical education at scale through teaching & product.

I’m a programmer who founded Flatiron School and taught its first cohorts myself. As the school grew to 13 campuses, my job became turning what worked in my classroom into curriculum, instructor development, standards, and software so other instructors could deliver the same experience. Today I build with AI every day, and I keep doing the same work: turning what works into training, tools, and teams that scale.

2012

Started teaching engineers in the room

13

Flatiron campuses running one curriculum

10,000+

Flatiron alumni

70%+

Online completion on Learn.co

$30M

Flatiron acquisition by WeWork

Taught first. Built the systems second.

Innovent Capital

Jun 2025–present

Chief Technology & Product Officer / Entrepreneur-in-Residence

Hands-on AI product development inside a small team of founders, operators, and investors.

  • Build with Claude Code and the Claude API daily: agents, tool use, structured outputs, prompt versioning, and evals, shipped in production Rails applications.
  • Built a Rails application generator with an AI development harness of versioned instructions, skills, conventions, hooks, and scripts. The model writes the code and the harness defines the process. An eval confirms the harness follows the workflows and conventions.
  • Taught non-engineers on the team to ship product and code through that harness, with review and guardrails that kept quality high. A small field-readiness program in practice.
  • Built and launched VCMatch, using embeddings over investor portfolios and theses to match founders with relevant investors and explain the fit.
  • Built PostMoney, which extracts KPIs from founder updates, emails, and PDFs into portfolio reporting. Currently in private beta.
  • Created PromptEngine, an open-source Rails engine that manages prompts as data with versioning, rollback, and a testing playground for OpenAI and Anthropic models.
  • Advise four portfolio companies on technical direction and lead Innovent’s CTO Huddle.

Revature

Oct 2020–Aug 2023

Chief Technology & Product Officer

Technical training at scale: thousands of trainees a year moving through instructor-led programs into engineering roles.

  • Built eXa, a learning platform for instructor-led technical training, and RevUP, a free preparation course, connecting candidate preparation, live instruction, and progress tracking.
  • Built a training-event tracking system that connected data across tools so training and marketing teams could see what was working and act on it.
  • Led a remote product and engineering team of 50. Introduced Ruby on Rails to cut sprint time by 50% and reworked AWS infrastructure to cut cloud costs by 30%.
  • Helped scale the company from $60M to more than $260M in annual revenue.

Kode With Klossy

Program design, curriculum & train-the-trainer guide

Conceived of and designed the program and curriculum with Karlie Kloss. Wrote the teaching guide that let instructors who were not expert engineers run the program well: short explanations followed by exercises, questions rather than taking over, and small, achievable projects.

The program has run every summer since 2015 with a new cohort of instructors each year. The guide is what makes that repeatable.

NYC on Rails

Founder · Founded 2007

Built a community around Ruby on Rails through technical talks, events, and shared work. Where I first learned to explain code to a room.

Designer Pages

Co-founder · 2008–2012

Built a search and specification platform for architects and designers, indexing more than one million products. Patented the ad-matching approach.

The teaching is the portfolio.

Talks, guides, and a case study, all of them public.

“Have them do
the typing.”
From the KWK teaching guide
A rule for helping without taking over.

The problem I have kept returning to is how you transfer technical capability from a small number of experts to a much larger population without lowering the bar. At Flatiron the question stopped being whether I could teach a thing and became whether someone in another classroom, on another campus, with another instructor, would get an equally good experience.

The answer was never a script. It was a small set of beliefs that changed what an instructor did next: give people a reason to care before the mechanics, keep the keyboard in the learner’s hands, keep the challenge but remove the needless friction, and make the philosophy observable so feedback can improve the lesson. I build software and teams the same way.

Read my teaching philosophy