I started in recruiting. Now I build the platforms recruiting runs on.

I spent the first half of my career in technical recruiting, covering engineering and data roles in Berlin, San Francisco, and Chicago, and kept ending up on the systems side of it. I ran a Greenhouse implementation, scoped Workday Recruiting business processes, instrumented funnels, and built the headcount models recruiting leaders argued over.

That pulled me into analytics. At a 23,000-employee healthcare enterprise I built the People Analytics function from scratch, governed a very large Workday reporting estate, chaired the committee that set conventions for 80+ analysts, and built forecasting models that changed hiring plans before capacity gaps showed up in revenue.

Then the tooling changed, and the thing I could do about it changed too. Today I work as an engineer: I architect and ship the platforms: governed HR data warehouses, integrations, agentic systems in production, rather than filing tickets for someone else to. My identity in one line is builder-in-residence for People Technology. I don't adopt tools; I build the infrastructure other people and other agents build on.

I work unusually publicly: decisions narrated in project channels, misfires owned openly, documentation written so the next person, or the next agent, can pick up an in-flight epic. That habit is why the work compounds instead of stranding with me.