About
Connor Easterbrook
I build software across the connections between applications, data and the people using them.
My background
I started in web administration, maintaining websites with attention to accessibility and operational security. I moved into full-stack .NET development, working on educational web applications, authentication, asynchronous processing and automated delivery.
I now work in defence software engineering, across networked applications, API integration, platforms and developer tooling. That progression has given me experience of both the behaviour a user sees and the application and delivery decisions behind it.
The work I bring together
My experience includes transport and message-processing changes, external API integrations, live data and the tooling needed to develop and verify applications. I enjoy following a problem across those boundaries: an interface issue can lead back to an API contract, while an unreliable workflow can reveal unclear ownership of state.
Alongside application development, I have built workspace tooling and reusable delivery foundations. Documentation, configuration and verification are part of that work, because someone else needs to be able to understand and maintain the result.
How I work
I try to make assumptions visible early. What happens when a connection drops? Who owns this decision? What does a successful response actually promise?
I prefer clear boundaries and useful tests, with enough documentation to explain the reasoning. I am happy to simplify a design when its extra machinery creates more work than it saves.
What you will find here
The case studies describe my contributions and the decisions behind them. The engineering notes give individual problems more room, using generalised examples where useful.
For a fuller account of my experience, or to discuss an engineering opportunity, get in touch and request my CV.