Automation · integrations · internal tools

I turn messy workflows into tools people use every day.

Sole architect of 40+ systems used by 15,000+ people—still shipping. Customer-service roots, psychology training, production engineering.

Sole owner
Architect of an org’s production tech stack
40+
Production systems still in daily use
15,000+
People who’ve used systems I’ve shipped
4+ yrs
Inventing, shipping, and owning ops software
Also on the record

Results under real pressure

+50%
Amazon — exporting throughput 4.2 → 6.3 units/sec in under two weeks
−28%
PRB — labor share cut with a forecasting model from scheduling data
+34%
PRB — sales up while holding coverage
PII
Trusted with sensitive records — NYS DOL claims + production CRM/LMS data
Diego Martinez in a suit, smiling
Who you’re hiring

One owner who can hear the need and ship the fix

Years in customer service taught me how stakeholders talk when they’re stuck. Psychology taught me why tools fail people. Engineering is how I close the loop—and own it after launch.

Selected work

Proof, not promises

Intake that becomes trusted records. Check-in that works at the door. Automation under load. A sample from systems still in daily use—filter by domain, language, or concept.

Browse all 40+ systems

How I Think

If people keep “misusing” the system, the system is wrong.

That’s how I think about every build. Safety and simplicity over cleverness. Design for tired humans. Customer service instincts for every stakeholder conversation.

Read How I Think

Fit

What hiring teams need to know

What roles are you targeting?
Any seat where inventing process and shipping production software is the core job—automation engineer, integrations / systems engineer, ops tooling, technical ownership, IT leadership, TPM-style build-and-own. Director of IT is my current scope proof, not a title ceiling. Remote preferred. Full-time or contract.
Does this only fit education or nonprofit?
No. The transferable patterns are CRM truth, intake → trusted records, event/ops tooling, platform bridges, and automation under load. A STEM research org is where I’ve proven depth—not the only market I can serve.
How are you different from a typical engineer?
A large customer-service background plus Psychology means I hear stakeholders clearly and design for tired, non-technical users. Then I invent the missing process and ship something staff keep running—not a demo that dies after a pilot.
How do we start?
Email the role—or the painful workflow—plus tools in play and timeline. I’ll tell you quickly whether I’m the right hire, and what I’d need to move fast.
Next step

Got a painful workflow? Send it.

Role or stuck process, tools in play, timeline. I’ll tell you quickly if I’m the right hire. Remote preferred. Full-time or contract.

Email me the role