Daniel Peedah

I Worked as part of a specific product oriented delivery team; required to analyze, create and maintain automated tests; covering scenarios for specific releases into our Global web product that integrated with multiple microservices and apps

Much like my previous role - responsibilities varied from directly producing these tests, and also analyzing scenarios,raising defects when bugs were found, and conversations with teams further in the test pipeline than ourselves. With added responsibilities as I prepare for more seniorship roles.

• Leading specific month spanning deliveries, by discussing and raising potential issues and risks in early discussions with Business analysts, and delivery teams and pod owners.
• Assigning scenarios or enhancement tasks to those within the team that are assigned for my delivery.
• Discussing and providing updates for our roadmaps and any potential blockers - to help provide more accurate time estimates for product owners.
• Conducted exploratory tests for tests that cannot be automated after analysis.
• Optimizing test coverage by analyzing current scenario coverage and updated flows within the program - and collaborating with my team to prioritize test cases.
• Managed defect tracking systems effectively.
• Reducing testing time by creating efficient, reusable test scripts for various applications, this is a skill of mine that has greatly improved over time.
• Maintaining detailed documentation on test results via confluence / Jira tracking or Github tagging, providing valuable insights for future projects when needed.
• Provided solutions to various technical problems of varying scope and complexity

An example was an intermittent defect that had effected multiple delivery teams and their tests for 1-2 years.

As it began effecting a larger percentage of tests, it became a high priority to fix.

I later found the root cause during analysis - although it would not occur in real-world setting, it was due to our version of selenium and browserstack limitations and the varying speed of individual test pods, thus its intermittency.

I was tasked with fixing this issue throughout multiple weeks as the fix could not break any regression tests and focus had to be made to ensure it didn't slow down tests too drastically so progress was slow. I was able to resolve this issue to the point we haven't seen it reoccur in 1+ years. It is one of my prouder works as it was completed early on in my time within the team.

This role was contracted under a global government project, and mainly required writing Java for End-to-End behavioral automated test scripts, for newly planned functionality, or functionality currently in production, for the web-based project.

• Analyzing intermittent defects to increase test quality and reliability by creating tickets for teams to work on or directly working on these changes myself.
• Managed defect tracking systems effectively, providing timely updates on issue resolution status for project stakeholders.
• Supported cross-functional teams during release cycles, ensuring seamless integration of tested components into final products without compromising quality or functionality.
• Optimized test coverage by analyzing requirements documents and collaborating with business analysts to prioritize test cases.
• Collaborated with business analysts in understanding requirements specifications clearly and early in the dev cycle for any release, enabling accurate translation into functional test cases.
• Identified critical bugs early in the development cycle

Netbuilder is a leading provider of creative, software, consulting, and managed services to financial, government and commercial markets. A full IT and digital service agency, with employees spread across our UK, France and US offices.

As a graduate software engineer, worked with multiple clients, in my case I mainly worked for both AstraZeneca and NHS, working on projects that involved:

• Utilizing Docker and workstation pro to set up an environment to store and transfer firewall logs to Splunk from multiple local machines owned by our contracted companies.
• Using Splunk for ITSI projects, with focus on correctly deploying files and other prerequisites on a client's pre-production and production environments around the world, to track and analyze data
• Defining error codes or patterns within the logs gained via SPLUNK - for known critical system failures, to detect and notify relevant parties of these companies in real time.
• Creating python / PowerShell 2.0/3.0 and .bat scripts to be deployed into client machines from around the world, depending on the requirements provided by the client(s), utilizing Splunk.
• Creating ITSI Glass tables and Dashboards to visualize KPI's and Metrics to customers.
• Being involved in end-to-end client meetings to review the current state of a project and creating new requirements.
• GitHub / Confluence to manage work sprints and goals
• Following a standard for pushing / pulling changes between POV, Preprod and Prod environments.
• Managing files and data securely through citrix, and mobaxterm
• Creating training documents for clients, as well as documenting projects for in-house developers.
• Creating requirements with a team based on a client's non-functional breakdowns.

Civico was a challenge, as my first professional job in my chosen career path, I worked for them during my placement year. I was part of their back-end C++ team and helped create new functionality and uses for their live streaming and conferencing system.

Much of my production work was in adding support for new cameras or microphones from different companies.

A typical day might include me adding a "rotate" functionality for a new camera, this would mean reusing code already available and to be inherited by the new camera, using the API provided by the provider. An API call for a camera may come in HEX, Lexical syntax, or degree and number values, it was my job to allow the new camera or microphone to carry out as many functions agreeable with our application.

Other learning points:

• Learning C++ as I created new functionality for the software
• Reading and using API documents provided by external companies to provide new functionality
• Enhanced software performance by optimizing code and troubleshooting issues.
• Implemented thorough testing procedures to identify bugs and ensure the seamless functionality of software applications.