about

Calm, pragmatic, and useful — in that order.

I'm Ben Kelly. I run consulting.benjamin.ie as an independent practice, helping businesses and engineering teams make confident decisions about their systems — from a single network rack to a multi-year cloud strategy.

background

Where I've come from.

My background spans software engineering, distributed systems, and the messier real-world fabric that holds them up: networks, identity, operational tooling, and the human practices that make all of it run.

I've worked across regulated sectors — legal, health and similar — where the "boring" parts (audit, access, data residency, change control) are the parts that actually decide whether a project ships.

Most recently, I spent several years as a software engineer at Microsoft Azure, working across cloud infrastructure, Kubernetes, AI, and architectural design — from large-scale platform engineering and PoC work through to accessibility initiatives and regulatory compliance programmes across Europe. Before that, I built and shipped across fintech-adjacent, legal, and health-adjacent environments. I also started out as an electrician's apprentice — which is probably why I still end up pulling cable when a fit-out needs it done right.

The work I enjoy most is the kind that gets handed over because there isn't a clear path through it yet. Some of that pattern is just experience; some of it is being dyslexic, which has always pushed me to think laterally and arrive at solutions that more conventional approaches tend to miss.

Outside the work itself: based in Dublin, mostly found tinkering with personal projects, electronics, and anything I can take apart and put back together better.

The full work history lives on my CV: cv.benjamin.ie. Notes and writing: blog.benjamin.ie.

about.txt
name = Ben Kelly
role = Software engineer & architect
company = consulting.benjamin.ie
based = Dublin 2, Ireland
since = 2025-06
availability = remote & on-site
depth = software · networking · AI · security · privacy · M365
style = honest scoping, written outputs
how i work

Principles I keep coming back to.

Decisions over deliverables

The most valuable thing I can leave you with is a clearly-stated decision and the reasoning behind it — not a stack of slides nobody opens twice.

Smallest change that helps

Big rewrites are rarely the answer. I look for the smallest credible change that moves the system in the right direction and unblocks the next one.

Boring on purpose

I bias toward boring, proven technology. Excitement should come from what you build with it — not from operating it at 3am.

Honest scoping

If a piece of work isn't a fit, I'll say so on the first call and point you somewhere better. Wrong-fit engagements are no good to either of us.

Written, not hand-wavy

Recommendations land in writing — short, scannable, with the trade-offs visible. Easier to disagree with, easier to act on.

Respect the team

I work with your team, not around them. The goal is to leave the people who live in the system more capable than I found them.

engagement shapes

A few ways we can work together.

Engagements are typically one of these — or a sensible combination. Pricing is either fixed-fee for a defined deliverable, a day-rate, or a retainer for ongoing advisory.

  1. Short review — 1–2 weeks, fixed scope. A written architecture, network, security, or AI-strategy assessment with prioritised recommendations.
  2. Project lead — multi-week, embedded. Lead a migration, fit-out, or capability build from kick-off to handover.
  3. Advisory retainer — ongoing. A predictable amount of time each month for design reviews, decisions, and mentoring.
  4. Mentoring — 1:1 or small-group, recurring. For engineers and tech leads working on growth, distributed systems, or reliability.