Developer in Engineering Security team. We analyse the technical aspects of all-things Security. The policies and bureaucracy are managed by other teams. Source code analysis for vulnerabilities. Static and dynamic analysis of threats. Tooling. Exploiting. Teaching how to develop secure code.

The official description: Work transversally with all QAs, providing guidelines that will help the quality assurance get to the next level of sophistication, and tackling the increasingly complex technical challenges the platform faces as it continues to evolve. What I did was to get involved in the technical aspects of the several automation frameworks we had (we have a system with several different satellite services in several different languages). The goal was to share knowledge among teams, make the different frameworks go in the same direction, solve the different harnessing problems and be a technical referent for any automation difficulties that might arise. Somehow accidentally I became the manager of a small team called QA Special Projects. This team handled any "strange" project that didn't match any of our current teams. It included stuff like accessibility, or testing new libraries or platforms. And most commonly Load and Performance testing with Jmeter and similar tools. One particularly interesting project was to cross the coverage information from the test automation system with the usage information from our productive servers in order to identify the "holes" in coverage that were used frequently in production. I kept the two roles in parallel.