Developer

Developer - legacy technology - Hybrid OpenVMS Plus 1 of the following: Cobol, c#, HP Basic, Fortran, Pascal, DEC Will also work on migration to SQL This role is about making a difference and is unique in its opportunity to support significantly important legacy systems as well as learning how to (and implementing) new digital micro-services strategies around the same system. bull; The role enables the older legacy system (MSL) to be supported by competent, analytical individuals but at the same time offer up new ways of integrating and extending functionality in modern ways. bull; It is accepted that the individuals that are lsquo;right for this role rsquo; are technically not a 100% fit in that legacy skills and modern skills are not always within the same individual ndash; but this role is available to those willing to learn technical, domain and future skills or someone who has a strong foot in one and would like to make a difference in the others. bull; There is a potential for the right individual with the right personal attributes and approach to be trained into this position. bull; Working fromTBC, adjoined to the UK Team, the MSL Analyst/Developer will be a key member in MSL Development Team. bull; Reporting to the UK Development Team Leaders for support, guidance and technical direction the MSL Analyst/Developer role has been created to maintain and enhance our share registration applications MSL). bull; The MSL system is a legacy system written in Dec Basic on an OpenVMS platform. Whilst the stability and performance it is imperative this role provides two key services: o Maintain existing MSL services, code and connected systems: #xF0A7; To consider, supported by System Analysts, simple domain requirements in technical terms articulating the business need into technical considerations and specifications. #xF0A7; To provide 3rd line support on the share registration systems. #xF0A7; Design of system changes. #xF0A7; Deliver new/enhanced code to the MLS platform to support business needs either from specifications provided or self-determined based on own domain knowledge built up. o Marginalise MSL by introducing modern integration framework (DSF): #xF0A7; It is also key that the MSL system doesn rsquo;t continue to grow a larger footprint so newer integration technologies (such as the Group Digital Services Framework) are introduced; #xF0A7; Micro-services architectures are required to be introduced to create data and functional services that lsquo;hollow out rsquo; the MSL system over time; bull; MSL will be available for a number of years so the system needs to be supported whilst it is also marginalised towards the micro-service strategy. bull; This makes for a unique legacy/future architectural responsibility working within this area. bull; Production of documentation (e.g. design, specifications) in both the existing MSL and the newer DFS services is vital. bull; Creating abstract integration services to the legacy system allowing newer, digitally enabled solutions utilise the data within the database and enabling future transformation possibilities. bull; Ensuring that the MSL system integrity, incidents and problems are resolved quickly ndash; getting to know MSL lsquo;inside out rsquo; will; be key to transforming it through newer micro-services technologies. Responsibilities Responsible: bull; Working with the UK Team Lead - Design, Build and Test of Dec Basic code for the maintenance of business objectives as needed. bull; With this, whilst the dominant responsibility is code, the role needs to be take into consideration an element of removing ambiguity from change requests by providing some of the details around business requirements. Project demand would be led by Systems Analysts and not Analyst/Programmers. bull; Resolution of issues, incidents and problems within the MSL system due to code or data issues. bull; Understanding, documenting and supporting the existing MSL code modules so they can continue to provide integral systems service to the business and can be integrated/supported by DSF components; bull; Ensuring that, working with DevOps, the Development Team has the right environments to maximise the development Teams rsquo; efficacy and obstacles are removed and automation introduced where appropriate; bull; Working with the UK DSF Architects to learn the framework and to determine what integration opportunities exist and bringing those opportunities to an implemented reality. bull; Work with ALM/SDLC Architects to ensure that code is properly managed and stored correctly with code repository tools. bull; Ensuring code is of good quality without significant rework required and without introducing performance or security issues into live services. bull; Production environments are protected by governance, good practice/process, design and lsquo;fit for purpose rsquo; environments, to the left of Pre-Prod, supporting all project and change activity; bull; Ensuring project and change release(s) are packaged to the right quality, repeatable between environments without change or modification and deployed to the target environments - ultimately to Production without detriment or issue in agreed timescales; bull; Software and processes are correctly documented to ensure single points of knowledge do not become a problem and skills are distributed across the team and department; bull; Ensuring that software Deliverables/Artefacts, as part of any Change/Project, are progressed providing appropriate status reporting and updates as requested by the Line/Project/Change Manager; Qualifications and skills There is potential for the right individual with the right personal attributes and approach to be trained into this position as it is recognised as a uniquely position role where the successful candidate will be required to learn domain knowledge, legacy coding skills and alongside ndash; new modern day micro-services strategies. Desirable (Not Essential) bull; DEC/Compaq/HP Basic bull; RMS bull; OpenVMS bull; Experience of the full software development lifecycle. bull; Experience working with legacy systems and platforms bull; ISAM files bull; C# bull; Working with micro-service patterns Key Performance Indicators bull; % rework of code provided to fulfil business objectives. bull; Quality of code in reviews meeting architectural and quality/coding standards; bull; % of Releases/Deployments to Production and non-production without issue; bull; Post deployment Incident levels achieving set targets; bull; % of formal processes documented. bull; Number of DSF compatible services approved by the DSF Architects. Competencies Required bull; Fast learner looking to make a difference; bull; Understands the challenges of legacy v modern and willing to address the former; bull; Innovation, change and continuous improvement bull; Communication bull; Results focused bull; Technical awareness bull; Commercial awareness Desirable bull; Leadership and performance bull; Customer service bull; Team working bull; Risk and conduct management