As part of the Ecosystem Tribe I was able to rotate through several squads within the Company. Starting out with the Accounts Squad, where I familiarized myself with different crypto wallet technologies along with the execution of test cases; other responsibilities in this squad included the migration of the test suite to TestRail and the onboarding of the resident QA that was due to take the position permanently. Following this I joined the Workspace Squad, in charge of the process followed by creators within the Sandbox metaverse to create, publish and monetize their NFTs through the Marketplace, in which I gained experience about Blockchain technologies and integration. I am currently a part of the Experiences Squad, which is in charge of revamping the way creators generate their content and publish it in the metaverse while also reaching out to players and fans with a web page associated with their experience, showcasing its features, gameplay and rewards for playing. It is also used as a platform to offer exclusive content in the form of NFTs so other creators can incorporate them in their own experiences as well. This position is much more challenging than the previous ones, since the Experiences Squad acts as intermediary between the Marketplace where NFTs are published and locations for the experiences are purchased, the Game Maker app which is used to create the environment for the experiences, and the Game Client app, which is the platform in which the experiences are accessed by users, while also adding features of its own, e.g. access restrictions depending on age, country of residence or even NFTs that the user needs to have in their wallet in order to gain access to the experience. Integrating all these separate systems makes it a very challenging and key role in the Company.My latest challenge in the squad has been learning Cypress to begin working on the automation of the smoke test suite that has gained complexity over time.

I was a part of the Checkout team, at first testing the web application for Travelocity.com with existing test plans, modifying them accordingly due to recent changes to the web interface, and reporting bugs using the Bugzilla defect tracking tool. All test cases were created in HP Quality Center and later migrated to HP Application Lifecycle Management (ALM).Shortly after I was included in the Air Booking Service project, which maintained and updated the web services that provided the backend for the booking section (which included pricing, booking, special services and payment) of the web application. ABS was a small project in comparison, with only two developers and I in the role of QA, but it was a key piece in the correct working of the web application. The whole regression suite was automated using Parasoft SOATest, which I maintained and updated whenever new functionality was added to the application. I was also responsible for migrating from the quite outdated version 5 of SOATest, to the latest version (9.0).I also participated in a very fast-paced project for bug cleanup, which consisted in reviewing almost 1200 bugs that were open (some of which went as far back as 2008) and were never followed up on; this was an all-hands-on-deck project, involving several analysts, 15 developers and 6 QAs from the Dallas, Bangalore and Buenos Aires offices, with daily task assignments and biweekly implementations in production that required a very fast and accurate testing effort.

After almost two years working for Verizon Business, I returned to the Company working on different projects as a Senior Tester, including KiGoo, an add-in to integrate a user’s Google Account into MS Outlook, Kayxo iForms for Outlook, iPhone and iPad, and several other iPhone applications and games. I’ve participated in the iForms project from day one, creating test plans from scratch on all platforms. I used environment virtualization through vSphere to emulate different Windows configurations for testing. I was appointed Administrator for this application, which allowed me to create, configure and maintain the virtual environments used by the whole Testing Team. We managed our time and tasks using the SCRUM Agile methodology, with ScrumWorks as our main planning and metrics tool. I also provided support for the Sales Team to demo our products to potential customers on a regular basis.One of the applications developed at Kayxo was Kolonists, a game for iPhone and iPod Touch platforms, which combined strategy, construction and politics, featuring single and multiplayer (Wi-Fi based) game modes.

I worked on a single project (Event Monitor) as main point of contact in Argentina, and I was also involved in two other applications (ETS/CBE and LTS) to act as back up tester. Analysis and design team members were located in US and developers in India, with constant phone and written communication between all team members, all of it done in English. Intensive use of testing applications such as Mercury Quality Center, and internal applications for project tracking and issue management. The main working environment was UNIX, involving console, shell scripting and data file management through Hummingbird Connectivity Suite. I was an active participant on the analysis and creation of software requirement documentation (based on both high and low level de-sign documents), test cases and test case automation via shell scripting. As part of my tasks within the Test Team, I was in charge of environment creation and maintenance, defect report and issue tracking. Took mandatory training on UNIX (system introduction and shell scripting), database design, problem solving and decision making, and building better work relationships.

I worked during the whole period for a single client (Kayxo, formerly known as Quantum System), at first as a Testing Engineer and since December 2006 as a member of the Product Management Team, in the role of Acceptance Tester. I had direct interaction with three separate development teams, one for each component of the developed application. Initially executing manual and automated test cases (using the TestComplete application from AutomatedQA), and later as a member of Product Management I had a more functional role, creating product requirements after meeting with prospective customers and VPs from other branches of the Company, writing acceptance criteria documentation, user guides and creating acceptance test cases as well.