Projects
These case studies show how I work and some of the projects I've worked on.
From April 2016 to April 2017, I worked as a Senior C# Developer with Landmark, participating in a major modernisation programme that helped reshape part of the organisation’s core processing infrastructure.
Landmark is widely recognised as the UK’s leading provider of land and property risk data, digital mapping, environmental information and related workflow solutions. It combines vast proprietary datasets with analytic and software tools used across the property and conveyancing ecosystem — from estate agents and surveyors to lenders and legal professionals — to support confident, compliant decisions throughout the transaction lifecycle.
At the time of my engagement, a significant portion of the UK’s mortgage application processing ecosystem relied on Landmark’s backend services and data platforms, which fed information to lenders, brokers and major banks across the country. That meant the platforms I was helping to modernise sat behind an enormous volume of real-world activity, where reliability, throughput and maintainability were essential.
The core of the engagement was a .NET modernisation programme: moving legacy pipelines into a more modular, service-oriented architecture backed by C#.NET, RESTful microservices, and SOLID-aligned design principles. This wasn’t an academic exercise. It was about replacing brittle, hard-to-change systems with services that could evolve safely and predictably, reducing risk in a domain where any regression can ripple into downstream mortgage workflows.
We organised the work around small, deliverable API surfaces that could be versioned, tested and deployed independently. Our REST-first approach (a microservices approach) made it easier to shield consumers from implementation changes and facilitated parallel development across teams. The focus on modularity and clear interfaces also meant discussions about behaviour and responsibility could happen in code — rather than being deferred to architecture documents that no one read.
Alongside the technical conversion, we invested heavily in ensuring that design decisions were defendable and understood by the team. That involved careful application of Domain-Driven Design concepts, a practical interpretation of SOLID principles, and a strong emphasis on patterns that made the system comprehensible over time — not just on the day it was written.
Part of the role was explicitly about people as much as technology. I acted as a hands-on technical lead for an agile team of eight, facilitating communication between developers, product owners and stakeholders, and helping move conversations from ambiguity into clarity.
I also mentored a developers, some of whom went on to lead their own team. That mentoring was grounded in practical habit change — establishing good design and testing practices, explaining trade-offs between abstraction and simplicity, and helping build an internal capability that didn’t depend on any single person.
Training, pair programming and consistent feedback loops were as important as the code we wrote. They helped align the team around shared practices, spread understanding of the emerging architecture, and create an environment where progress didn’t depend on guesswork or personal intuition alone.
Landmark’s products are deeply embedded in the UK property market. The company sits at the heart of due diligence, risk assessment, conveyancing and regulatory workflows — turning complex land, environmental and planning data into actionable information for professionals across the transaction chain.
The modernisation work I contributed to played a part in strengthening the backbone of these services, making them easier to maintain, evolve and integrate with other systems across the industry. Replacing monolithic processing pipelines with a RESTful microservices architecture gave the broader technical organisation more flexibility and confidence to respond to future requirements without fear of unintended disruption.
That experience reinforced a lesson that has shaped much of my subsequent work: in long-lived systems dependent on reliable data and predictable behaviour, successful engineering is as much about making the work understandable as it is about making it correct.
C#.NET, REST microservices, Domain-Driven Design, SOLID principles, Agile development, API design
Feedback from people I worked with within this organisation
I worked with Nathan during my time at Landmark. Nathan was a contract developer brought in to help provide much needed development and creativity on some of the areas in the new transformation project and hit the ground running – He did not disappoint and completed in very little time some work which had been outstanding for a while.
Nathan has a breadth of knowledge in development, coding and also coaching and mentoring. He seemed to work really well with other developers and was always on hand to coach them in new ways of approaching situations and completing work.
Nathan provided me support in agreeing to pair programme with some of my team members who I lined managed and this resulted in a noticeable difference in their quality and approach to work.
I would highly recommend Nathan to any organisation who are not just looking for a developer but someone who can help engage your teams and coach on Agile and best practice.
I worked with Nathan on a large enterprise web application project as another contractor. He knows his stuff and my impression is that he is one of those devs who makes others around him better by mentoring colleagues and passing on information. I would hire him if I were building a team.
Nathan is a very technically experienced developer and from a project management perspective, a joy to work with as he provided reliable and pragmatic estimates which he worked to and delivered on schedule. He was a safe pair of hands and provide guidance and mentorship to less technically able developers. Nathan specialises in UI development however he still is able to work at the middle tier and backend areas. I really enjoyed working with Nathan who has a calm and friendly disposition. Although he was a contractor he still was passionate about doing a good job for the company.
Nathan joined our dev team building scalable micro services for core enterprise applications as part of our ongoing modernisation program.We achieved a great deal together and we took away a lot of new insights and ideas from the collaboration.
From the many projects we worked on, I also managed to learn Angular 2 from a developer who prides himself on delivering clean code and architectures, it was a real pleasure to work with him, with his genuine commitment to delivering clean solid software.
I would highly recommend Nathan.
