Senior Software Qa Engineer - Qa Technical Lead
CurrentComing to TheLotter, i had but the slightest idea of what was in store for me. I knew from the start that it wasn't as simple as it originally appeared, but I also knew that there was a lot for me to learn, when it comes to different approaches for the problems encountered, or simply the number and usefulness of the software I would have to use daily.At first my responsibilities were limited to understanding, writing and running acceptance tests, but once i proved myself, the QA team got upgraded to QA Technical team - basically, apart from breaking down PBIs, preplanning and planning meetings, writing E2E tests and mastering the system, configuring and deploying microservices and the client+server builds to the required environments, testing and releasing hotfixes, I was also coordinating and mentoring the developers with regard to the features, guiding them through the complicated flows required to reach the desired functions/statuses. I was also holding kick-off meetings to the developers, aiding them to write their own SpecFlow and ATs, reviewing the ATs, and even running some alongside them. I also often had to prepare training material, hold trainings, and create wikis for certain flows, procedures etc.Some of the tools used (pretty much daily) during my time here are, in no particular order: - TFS (both WebTFS and inside Microsoft Visual Studio)- Microsoft SQL Server Management Studio- Redis Desktop Manager- RabbitMQ- DataDog- Loggly- Fiddler- various others, which weren't used very often, or are not relevant to "skills" (such as mRemote, or Slack, with its threads, on which we set up alerts when certain monitors triggered them).It was a very interesting and useful opportunity, and i had the pleasure of working with people from all backgrounds, from all around the world, and got to use both the latest and greatest tools, as well as some pretty antiquated ones. All in all, i'm a much more accomplished me for having worked here.