I worked on a project for client Vaillant Group Business Services GmbH. The project involved taking over a custom Keycloak-based IDM implemented by a previous team as well as developing re-usable components for other dev teams including a fileupload service and cookie consent manager integration as part of the Digital Solutions Platform team. The following tasks we encountered mainly:

• Assume responsibility for the deployment, maintenance and development of the custom Keycloak-based IDM solution using mainly Jakarta EE, JavaScript, Terraform and Kubernetes/Kustomize deployment manifests
• Work with internal and external consumers of the IDM solution to assist them getting onboarded to it
• Keep custom Keycloak configuration files up to date and respond to customer queries
• Develop new fileupload component using Azure Functions and k8s that allowed consumers to seamlessly upload files to the CRM backend (Salesforce) after scanning them for malicious content
• Help advertise new fileupload solution and get consumers onboarded
• Design and develop Integration Layer for 3rd party cookie consent manager solution
• Improve current Monitoring/Alerting system implemented using ElasticCloud (using ELK stack)

I have been working on a project for a client called PPRO a large Payment Provider. The goal of the project was to develop and deliver a CRM system that would allow a new strategic client to display transactions and refunds. The main tasks were:

• Conceptualise a ?Merchant Portal? to display financial transactions created via a newly written and not yet released payments API
• Design Architecture for new Merchant Portal. The result was a fully serverless application written in Typescript and Javascript mainly utilizing the following AWS products: Cloudfront, API Gateway, Cognito, Lambda, Kinesis and DynamoDB
• Helping business stakeholders to define, refine and formalise customer requirements into a SCRUM backlog
• Lead efforts to define all Cloud infrastructure as infrastructure-as-code
• Define and execute a testing strategy that would ensure that any code written is up to Quality standards as well as allowing for short feedback cycles
• Design deployment pipelines for all environments in gitlab Enterprise that would allow stakeholders to promote code all the way into production
• Liaise with SecOps and Infrastructure teams to define a new deployment strategy for serverless applications using aws-cdk (most previous software project were deployed using Kubernetes)
• Integrate with the existing payment processing solution which runs on a mix of Kubernetes and FreeBSD to ingest and display payments and refunds
• Assist the team with troubleshooting the newly developed API that allows their strategic client to create payments and refunds

I worked on a project Bunzl Europe, one of Europe?s largest Logistics enterprises. Goal of the project was to deliver a RESTful API to ingest documents into a Datalake store to kick of Bunzl?s new Datalake Analytics framework. The solution was implemented on Azure Cloud utilizing API Management, Azure Functions, Azure Storage Accounts and CosmosDB. The following tasks had to be performed as part of the project:

• Liaising with business stakeholders from different departments for information gathering and formalising of business requirements
• Breaking down of requirements into Epics, User Stories and Tasks
• Planning and implementation of CI/CD pipelines in Azure DevOps utilising PowerShell Scripts
• Writing of highly modular Terraform templates for Infrastructure as Code
• Implementing of Test Strategy consisting of Unit Tests, Integration Tests and Acceptance Tests
• Documentation and handover of solution to client

I was working on a project for Edeka, Germany?s largest Supermarket Chain. I was assisting their ?Lighthouse? team in pursuing a cloud-first approach and acting as a de-facto blueprint for future teams and project and defining a sustainable model for supporting modern in-house software products.

The Lighthouse team was working as a cross-functional team following SCRUM methodology to deliver an in-house CRM tool to assist other parts of the business to carry out their day-to-day activities. The team was also tasked with BaU support and continuous improvement of existing solutions.

My main responsibilities at Edeka were the following:

• Liaise with technical and business stakeholder to define, refine and formalise business requirements, technical requirements as well as non-functional requirements
• Refine, size and prioritise above requirements in the backlog and sprint in collaboration with other team members
• Assist the team in all Cloud Infrastructure as well as Continuous Deployment queries
• Make sure, best practices of Agile Software development are being followed by improving existing testing solutions and Azure Devops Continuous Integration Pipelines
• Migrate the deployment pipelines of the BackOfficeApps2.0 application from AWS Cloud using Bash to Azure DevOps using Powershell scripts
• Improve monitoring solution implemented using DataDog
• Author a module for the provisioning of self-hosted. Azure Cloud Agents using Hashicorp Packer and Terraform to improve the stability and reliability of build pipelines
• Continuous improvement of the existing codebase written mostly in Typescript and augmented with Kotlin

I have been working on a project for London based tech startup Twyn Limited. During the duration of the project a mix of SCRUM and Kanban was used to keep delivering at a high pace while maintaining continuous improvement of the delivered solution.

My roles on this project were threefold: I acted as Solution Architect and Senior DevOps Engineer as well as filling in for the Team Lead position while the client was still trying to define their team structure. As part of these roles my responsibilities including the following but not limited to:

• Work with business stakeholders (CTO, COO, PO) as well as Delivery Lead and developers to discover, define, refine and record product requirements into User Stories in Azure DevOps boards
• Design a prototype mobile app/backend solution that would deliver the requirements. Quickly iterate the solution to make it more robust/functional and allows for experimentation. Technologies used include: SwiftUI, Python, C#
• Design a starter architecture in Azure Cloud that would be able to support the above technical solution. A non-exhaustive list of utilized technologies: API Management, Azure Functions, Azure Media Services, Cognitive Services, Storage Accounts, ?
• Set up Azure DevOps pipelines heavily utilising PowerShell scripts to work towards a CI/CD model and enable quick iteration of the solution
• Work on the continual improvement and evolution of the solution and architecture. As part of that most of the Azure Functions were replaced by a Kubernetes cluster to host most of the backend services
• Making sure that required infrastructure is being provisioned via terraform templates and a deployment pipeline

I joined Equal Expert?s network as an Associate. I was brought into a project with a large German financial services provider. The work was mainly focused on the below:

• Liaise with client?s infrastructure provisioning team
• Implement CI/CD pipeline to
• Work with Tech- and Development Leads to establish best practices, evaluate solutions to specific problems and ensure a smooth Path to Production
• Establish best practices in the DevOps team in the following areas: infrastructure provisioning, testing strategy, packaging and deployment of build artifacts, monitoring and alerting

The following technologies were mainly utilized during this project: Kubernetes, Docker, Gitlab, Cypress, Rancher

The main outputs of the project were a web application with a frontend written in React/Typescript and a backend written in Java/SpringBoot. Various external components had to be integrated with, including but not limited to:

• PostreSQL as DB backend
• Keycloak for OAuth authentication
• Microsoft Exchange for sending and receiving emails
• WebDAV for sharing and collaborating on Microsoft Word and Excel documents

I started my contract with Asos.com Ltd in November 2017. I was mainly working with the Data Science team. My responsibilities at Asos generally fell into two different areas:

• Onboard Data Ingestion Services developed by a 3rd party supplier in C#. As part of this project I was mainly exposed to the following technologies:
  • Microsoft Azure Cloud, Team City, Octopus Deploy, ARM Templates, Powershell Scripting, Azure ServiceFabric, Git
• Working alongside Data Engineers and Database Developers to help them release projects through various environments into production. The following technologies and tools were used to accomplish this:
  • ?Team ?City, Octopus Deploy, Azure Data Factories, Azure Functions, TFS and VSTS for Version Control

I have started working at Sainsbury Plc in October 2016 on an initial 6-month contract which has been extended twice. After working alongside the Windows DevOps Engineering team on 2 projects I have been put in the newly formed platform team in June 2017 and decided not to renew the contract with Sainsbury?s in October 2017. I have worked on the following projects:

Implemented CI/CD pipeline for a Microservices based C# Application using the following technologies and vendors: AWS, Terraform, Chef, Appveyor

• Refactoring of terraform Infrastructure Code for Microservices based ASP.NET Web Application to mitigate risks to the business discovered by penetration tests. To achieve this, several layers of separation and segregation were implemented as well as fine tuning and hardening of the existing setup.
• Working on the several tasks related to involvement in the Platform Team

I helped Wonga to migrate from on-premises VMware estate to AWS cloud using the following technologies:

• Octopus Deploy in combination with PowerShell scripting
• Hashicorp Packer and Hashicorp Terraform
  • ?Also? helped establish an ?Automation first? mindset.

• Founding member of the DevOps Automation team. 
• Successfully launched DevOps as a service for customers mainly focusing on Windows estate. 
• This offering was built mainly on PowerShell Desired State Configuration (DSC), augmented with Chef recipes where necessary.