Solutions Architect

• Oct 2022 - Present

Solutions Architect

• Aug 2021 - Nov 2022

Application Architect

• 2021 - Aug 2021

National Records of Scotland (NRS) is responsible for Civil Registration (e.g. births, marriages, deaths), the Census, Family History, and the National Archives in Scotland.My key remit as an Applications/Solutions Architect is to investigate, record, and articulate the existing estate and working practices (methodologies, automation, version control, technology stacks, delivery mechanisms, collaboration), and propose improvements.The contract is a mix of architectural, design, development, and coaching activities, including:- Analysing, diagnosing, recording, visualising, and presenting a complex legacy estate.- Convincing key technical and business stakeholders on legacy system position, proposed target state, and appropriate transitions.- Promoting a target architecture.- Coaching modern development, testing, architectural, Agile, and collaborative techniques – including pairing, TDD, BDD, Kanban, microservices, serverless, and API-first best practices.- Leading technical feasibility (proof-of-concepts) and team upskilling activities.- Leading sense-making (Cynefin) and decision-making discussions on current systems.- Sequencing activities for a complex migration to the new system / architecture.

Software Architect / Consultant / Contractor

• Nov 2018 - Nov 2020

Registers of Scotland (RoS) is a public sector organisation responsible for compiling and maintaining records relating to property and other legal documents. RoS is undertaking a major Digital Transformation programme to modernise its business and practices to become more customer-centric.My role as a Technical/Solutions Architect entails a mixture of technical and solutions architectural activities; however, in the main, I work closely with teams to: - Identify solutions that increase business value, reduce costs and improve operational efficiency.- Coach Design, Development, Architectural, Data Modelling, and Delivery Best Practices.- Achieve strategic alignment; particularly across teams, and between Business and Technology.- Coordinate in-flight legacy systems migration, whilst mitigating risk.- Prepare systems and teams for the future.- Score and prioritise work items.- Present, propose, influence, and negotiate improvements that balance long-term aspirations and short-term results with practical, impartial advice on appropriate score-based technical solutions.- Help nurture and embed cultural change, increase trust and ownership by promoting an inclusive, progressive, and proactive working environment.- Document existing transitional and aspirational system/process states.

Software Architect

• Sep 2012 - Nov 2018

Paywizard is a leading provider of outsourced support services specialising in the digital broadcast and new media markets. They deliver a SaaS-based subscriber management, payments, CRM, and Analytics solutions, deployed onto AWS and Azure platforms. Software is delivered using Agile/DevOps methodologies/movements and is typically built using REST/Java Spring Boot & Cloud/Docker/Kubernetes/Cloud technologies.I would describe my role as a combination of a Technical, Solutions, and Enterprise Architect. Additionally, at times, being hands-on; i.e. I sometimes provided development support to critical functional features to enable efficient delivery.I succeeded in this role through a solid mix of technical, personal, and leadership qualities that have enabled me to: build strong relationships across the business; drive change; define realistic visions, goals, and strategies; collaborate, recommend, negotiate, and compromise with stakeholders to solve problems in an efficient, cost-effective manner, using guiding constraints (e.g. MVP).

Platform Developer

• Jul 2011 - Sep 2012

Iplay distributed games to their/third-parties’ customers through a web retail store, built mainly with HTML/JSP/JS, Java Enterprise (JEE), Oracle ATG, and Oracle database technologies. Iplay used an agile methodology; projects were of a relatively short duration with regular client interaction. Iplay’s software solutions were constructed using continuous integration techniques. Iplay distributed games to their/third-parties’ customers through a web retail store, built mainly with HTML/JSP/JS, Java Enterprise (JEE), Oracle ATG, and Oracle database technologies. Iplay used an agile methodology; projects were of a relatively short duration with regular client interaction. Iplay’s software solutions were constructed using continuous integration techniques.

Senior Software Engineer

• Mar 2004 - Jun 2011

Typically, I worked as a Technical Lead on medium sized projects (2-12 months in duration) making architectural, design, and development decisions utilising my comprehensive knowledge of industry best practices. Typically, I worked as a Technical Lead on medium sized projects (2-12 months in duration) making architectural, design, and development decisions utilising my comprehensive knowledge of industry best practices.

Software Programmer

• Aug 2000 - Jul 2002

Key Responsibilities• Designing, implementing and testing software applications and fixing bugs using C++, MFC, Delphi and Oracle technologies on the Windows NT and UNIX platforms.• Creating detailed designs in UML and developing Unit Test Plans.• Responsible for changes to development tools used by over 200 developers. Key Responsibilities• Designing, implementing and testing software applications and fixing bugs using C++, MFC, Delphi and Oracle technologies on the Windows NT and UNIX platforms.• Creating detailed designs in UML and developing Unit Test Plans.• Responsible for changes to development tools used by over 200 developers.