PROFESSIONAL EXPERIENCE:

Confidential, California

Senior SDET (Software Development Engineer in Test)

Responsibilities:

• Agile SDLC, creating test plans & test cases, automating test cases.
• Lead the technical design and implementation of the automated testing of LinkedIn's Confidential stack using Visual Studio, .NET, C#, Ranorex Studio, Jenkins and Git.
• Created, enhanced and supported a UI automation test framework, designed like .NET, giving other SDETs the ability to efficiently test the quality of Confidential integrated with LinkedIn.
• Support for language neutral automation
• Display port size testing of responsive design for mobile
• Handling pop - up windows in parallel
• Enforcement of web page class design
• Support for validation of CSS properties
• Framework reliability monitoring with Microsoft Unit Test Framework unit and integration tests
• Strengthened team's ability to ensure quality of the Confidential code base by integrating code coverage as part of NUnit tests, UI automation and manual testing.
• Improved quality of the Confidential code base by driving effort to fix hundreds of compiler warnings, Visual Studio build warnings, MSBuild warnings and static code analysis violations.
• Code reviewed hundreds of test automation code changes and enhanced source control to automatically and clearly track and report code changes using a REST API, ensuring high standards.
• Augmented and supported test automation infrastructure, development life cycle and deployment using Jenkins and Git, increasing the stability and efficiency of this backend system that automated tests rely upon.
• Created ASP.NET web pages to wrap SQL queries using the UI to simplify and allow easy execution of database queries, boosting productivity of manual testing.
• Mentored engineers in Test Driven Development, code review, failure analysis and debugging, increasing competence and making tests more thorough, stable and easier to maintain.

Confidential, California

Senior QA Engineer

Responsibilities:

• Agile SDLC, creating test plans & test cases, automating tests: VS 2013, Ranorex Studio, .NET, C#.
• Created UI automation test framework (using .NET, C# & wrapping the Ranorex API) allowing easy test creation for lynda pages on supported OSs & browsers, to allow quality testing of the lynda experience from the user's perspective.
• Designed like .NET: installable, simple to use & productive, layered architecture to wrap low-level Ranorex API with convenience APIs, self-documenting object model making it intuitive with IntelliSense with strong types & a low barrier to entry (organized namespaces & basic scenarios covered with instantiation of a single type).
• Scenario-driven design; worked cross-team ensuring support of top scenarios of Confidential testing. Designed to evolve as support requirements change.
• Extended Ranorex API types with productivity methods.
• Supported localization resources, taking advantage of the .NET resource fallback process, allowing easy implementation of language neutral automation to cover Confidential on multiple cultures.
• Created unit tests (VS 2013) to monitor the health of the framework as its dependencies changed; e.g. Ranorex API, supported browsers & lynda pages.
• Allowed automation engineers to be highly productive as tests were implemented in a short amount of time.
• Created Ranorex C# .NET tests solution to organize tests & run via command-line so Jenkins jobs could specify environment & browser.
• Moved code from GIT to SVN, increasing engineers' productivity (Ranorex was integrated with SVN).
• Feedback to Ranorex to improve their API quality.
• Drove addition of stable attributes in elements on Confidential to decrease test code maintenance.
• Created coding guidelines & supported on/off-shore automation engineers; code reviewing with high-quality standards to ensure maintainability & stability.
• Mentoring automation engineers: C# .NET, OOP, algorithms, data structures and approaching interviews.
• Phone screened/interviewed candidates.

Confidential, Redmond, Washington

Software Development Engineer in Test II

Responsibilities:

• Microsoft Pinpoint Web site. Agile, Scrum SDLC. Sprints, Planning Poker. Creating test plans & test cases, automating tests.
• Automation using Visual Studio 2010 Coded UI C# .NET and creating XML data-driven unit tests.
• Understanding customer scenarios creating automated and manual User Acceptance Tests (UATs) in Team Foundation Server (TFS) during Sprints by working with Program Managers and developers, resulting in thorough test coverage.
• Testing new feature code during Sprints as part of the Agile process, opening many bugs early for easy tracking by developers.
• Contributed to shared test code infrastructure, updating assemblies with code enhancements and bug fixes.
• Achieved a goal of even code coverage by creating and maintaining automated BVT tests across all areas of the product.
• Managed offshore team to automate non-BVT test cases.
• Created test to test localization of Pinpoint’s web pages by retrieving all strings and then identifying the language of the strings using the Bing translator API.
• Met test team quality standards by quickly analyzing BVT failures, updating BVTs as product changed, filing new BVT product bugs and updating lab scripts to set browser configuration for nightly BVT automation test runs.
• Impacted and influenced cross-group improving the Localization, Globalization and Localizability test process, by implementing Sprint UATs as part of an offshore team’s International test cases, starting regular bug triage and documenting the workflow to ensure clarity across multiple teams.

Confidential, Redmond, Washington

Software Development Engineer in Test II

Responsibilities:

• Agile, Scrum SDLC.
• Testing the Microsoft Pinpoint Web site by ad-hoc testing, running manual and automated test cases and analyzing failures.
• Writing automation with Visual Studio 2008 and 2010 C# .NET, creating and maintaining tests.

Confidential, Redmond, Washington

Software Development Engineer in Test

Responsibilities:

• Waterfall SDLC. Creating test plans and test cases, automating tests.
• Testing Internet Explorer (IE) features on supported IE language versions on supported Operating Systems.
• Automating (JavaScript, C# .NET) manual test cases to improve efficiency and quality of test coverage.
• Invented ways to improve the Internet Explorer International localization and localizability test process and infrastructure:
• Invented and coded a C# .NET “Crawler” tool which discovered all UIs within any Windows application on any language.
• Crawler created a tree of the UI hierarchy structure, writing the structure to a Windows International Team (WIT) database while capturing all UI discovered and storing them for review by testers.
• Testers would use a WIT tool to review the captured UIs that were found and created by Crawler.
• Drove WIT to enhance their tool so that it would file bugs with the captured UIs to IE’s Product Studio bug database directly.
• Prior to all of the above, all UIs within IE had to be manually mapped out and manual tests had to be created to capture them. The Crawler process saved months of manual work per application.
• Applied international knowledge towards creating efficient test plans to cover all international IE QFE & Security releases and IE milestones across 30+ localized/MUI and 50+ LIP languages on all supported OSs, resulting in thorough coverage of these releases even with a limited international test team size and test window.
• Reviewed test plans for globalization test coverage, providing feedback on coverage holes which resulted in more thorough globalization coverage.
• Acting Test Lead when required.
• Interviewed full-time and contract candidates, recommending those who would contribute to Microsoft’s success.

Confidential, Redmond, Washington

Software Test Engineer

Responsibilities:

• Created new test procedures and test cases, which improved the efficiency of quality support when:
• Verifying milestone Internet Explorer (IE) public releases prior to and after live Web and CD deployment, including live Web pages.
• Triaging bugs from TechBeta IE users and internal IE users.

Confidential, Redmond, Washington

Software Test Engineer

Responsibilities:

• Ad hoc testing, test case writing and execution on daily builds, TechBeta bug triage, testing Internet Explorer (IE) Web and beta releases, security fix release verification, investigation of urgent IE issues, debugger support for the IE team, internal support for the IE & other teams.

Confidential

Technical Support and Novell Netware Administration

Responsibilities:

• Helping individual students with questions regarding Windows 95, MS Office and Internet Explorer.
• Assisted with Novell Netware 3.x administration and technical support on a LAN of five file servers and 400+ PC workstations used by 5000+ staff and student accounts.

Confidential

Telephone Support Technician

Responsibilities:

• Part of a large technical support team; hardware support of Dell machines sold to customers and support of software on these machines (Windows 95, MS DOS, Microsoft Office); averaged answering 40 customer calls a day.

Confidential

C Programmer, Novell Administration and Technical Support

Responsibilities:

• Designed and wrote various C programs (Visual C, Borland C), used in-house to process database marketing data, which reduced manual processing work by employees; e.g. correcting postcodes, merging duplicate records, converting file formats.
• Novell Netware 3.x administration and technical support on a LAN with PC workstations running MS DOS; hardware upgrades, database management, connecting external employees to the LAN, tape backups.