I build systems that earn trust at scale.
Dublin-based. 10+ years in B2B SaaS across internal platforms, trust-sensitive systems, and AI products where the workflow has to hold up in real life, not just in the demo.
Track Record
At Zendesk and HiveNet, I was usually pulled toward messy ownership, live customer risk, and decisions that needed to hold under scrutiny.
Agreement, DPA, and compliance workflow surfaces built for broad internal contribution.
Ryan's role: Ryan owned product work for the internal platform and its cross-team contribution model.
Caveat: The public evidence identifies team reach, not adoption frequency or business impact per team.
Agreement ownership, states, and review paths made turnaround visible and faster.
Ryan's role: Ryan led the trust-sensitive platform surface and the cross-functional operating contract around it.
Caveat: This is an agreement-workflow turnaround measure, not a claim that every compliance process moved at the same speed.
AI quality and taxonomy work grounded in production conversations, not staged demos.
Ryan's role: Ryan reviewed the conversations and shaped the evaluation taxonomy and product feedback loop.
Caveat: Conversation-review volume shows evaluation depth; it is not a standalone model-accuracy or quality score.
Micro-frontend contribution model that moved more product work through the system.
Ryan's role: Ryan owned the product model and the cross-team operating change.
Caveat: The percentage describes cross-team pull-request flow in that platform context, not company-wide engineering throughput.
Operating System
I map edge cases early, make risk visible, and keep pressure from turning into vague language.
I build for the moment the workflow hits real users, real pressure, and the first messy exception.
Trust is what happens when engineering, legal, security, and leadership mean the same thing by ready.
Benchmarks are useful. Live signals are better. I prefer proof that survives production contact.
More Context
Field Notes, Now, About, and How I Work carry the longer version: written thinking, current work, background, and operating style.
Peer Signal
Not adjectives. Observations from people who worked beside me when the work got difficult and the tradeoffs were real.
He doesn't just execute — he digs deep into the details, challenges assumptions, and ensures that what gets built truly serves the customer. He's equally comfortable rolling up his sleeves with engineers as he is presenting a vision to senior leadership. Ryan never lets silos or red tape stand in the way of doing what's right, and he's the kind of teammate who makes everyone around him better.
Ryan showed that he could balance security risk, business progress and technical constraints very well. Ryan can clearly articulate what decisions are being made. Even when he made decisions that did not prioritise security I always felt understood by Ryan, and he made sure we understood his priorities.
Ryan's ability to form solid relationships with people across the organization is legendary, as is his willingness to go above and beyond to help others. He takes ownership quickly, willingly, and isn't afraid to seek out solutions on his own.
Ryan consistently demonstrated a remarkable level of dependability and proactivity in his role. His ability to identify critical issues and pursue them to completion was invaluable to our team and significantly contributed to our success.
He did a phenomenal job of clearing roadblocks, communicating product needs, prioritizing our work, and ensuring we kept our customers top-of-mind. He is a stellar communicator, a strong team player, and a spectacularly positive guy.