Greenhook Systems Sign in
Laravel · PHP · SQL · Linux · 16+ years

Backend engineer for the codebases teams depend on

Senior and lead-level backend engineer with sixteen years in PHP ecosystems — still hands-on in Laravel, SQL, and Linux, and still the escalation point when production is under pressure. I have led engineering teams, recruited and mentored developers, owned roadmaps and releases, and steered delivery through acquisition and restructure while keeping a long-running communications platform stable (most recently in the education sector; the same patterns apply wherever uptime and compliance matter).

I am targeting senior backend, lead engineer, or team-lead roles in any industry — not tied to one vertical. I started in third-line support and moved into development and leadership from there; that history helps me debug under fire, communicate with stakeholders, and leave code and runbooks the next engineer can actually use.

What I deliver

Application engineering

Object-oriented PHP and Laravel, complex data models, Linux operations, and careful modernisation of legacy codebases.

Incidents and reliability

First responder for outages and security events — log-led diagnosis, coordinated recovery, and fixes that prevent repeat failures.

Release discipline

Git-based workflow, peer review, staging environments, and release pipelines that favour quality over ceremony.

Long-lived products

Permissions, audit trails, and uptime expectations — patterns that transfer across sectors once you learn the business rules.

Leadership and mentoring

Built teams, steered delivery through acquisition, and supported handover to successors — now focused on deep technical contribution.

Cloud and .NET

Azure Functions, Bicep, and .NET services alongside the core PHP estate — choosing the tool that fits the problem.

Rigorous work, clear documentation, sensible AI use

Structured problem-solving across application code, databases, and infrastructure. I design agent-assisted workflows for authorised repository review, documentation, and quality checks — with human judgement on what actually ships.

  • → Root-cause analysis and SQL-led data investigation
  • → Technical guidance for teams at mixed experience levels
  • → Plain-language updates for non-technical stakeholders

Recent background

The last decade-plus on a regulated communications product — high availability, careful change control, and code that still reads clearly years after the original author has moved on.

That work sat in education, but the engineering is generic: learn the domain, respect compliance where it applies, and ship backends you would trust on call. I am looking for the next problem, not the same logo.