Michał L.

Duties

1. Line management as per the corporate policies (including use of Trakstar for regulated performance tracking and reviews including peer ratings).
2. Serving as the testing Amigo, driving the shift-left in the pod.
3. Creating and refactoring testing processes, frameworks and scripts (Pact.js, WDIO, Cucumber, Jest, Playwright).
4. Spikes and research, sharing the results and propositions with the pod and the Quality Guild.

Why did you quit that fast? "The Canadian corporation"?!!

It turned out my (and others') leadership was of unacceptably ephemeral nature: the ways-of-working standards, painstakingly worked out between the 3 Amigos and the rest of the pod got abruptly overturned by a mid-level manager without asking pre-intervention questions or providing any explanations until demanded.

I did not take it lightly and made sure to explain my position on the exit interview, so now I'd rather explain myself before the corporation gets asked for my references.

For Coforge itself, I created a training delivery app with code exercises sandbox strongly inspired by W3Schools, as well as the first learning module delivered by it ("API testing in .NET/C#").

Initially I was placed via Coforge with Schroders Wealth Management to deliver a learning project with associated materials and processes. Serving as a standalone hub between multiple wildly different counter-parties with not a lot of previously built rapport proved to be too much for my fledgling consultancy skills though.