SUMMARY

• Team Lead of a successful Software Testing team at Microsoft.
• Excellent writing and documentation skills.
• Strong noledge of Windows networking.
• Intermediate to advanced debugging skills. Very experienced at resolving symbols and triaging both kernel mode and user mode breaks. Familiar wif most debugger commands.
• Intermediate noledge of teh C# programming language and of teh .NET framework. Capable of reading, interpreting, understanding and documenting C# code. Capable of writing lightweight C# applications.
• 1 year experience Java programming as a student at teh University of Newcastle upon Tyne.
• Experience wif web design (XHTML, PHP, ASP, JavaScript and C#). me is strong wif XHTML and have PHP and ASP development experience.
• Strong experience wif UML diagramming.
• Extremely familiar wif XML and XML automation.
• Strong noledge of database systems, me.e. relational database structure. Very comfortable wif writing SQL database queries.
• Strong noledge of database systems, me.e. relational database structure. Very comfortable wif writing SQL database queries.
• Very proficient and experienced wif HP Quality Center.

PROFESSIONAL EXPERIENCE

Software Systems Test Engineer

Confidential

Responsibilities:

• Investigated issues reported by users of teh Justice Detainee Information System (JDIS).
• Diagnosed and root caused issues and documented issues via IBM ClearQuest.
• Wrote test scripts to reproduce problem behavior.
• Tested fixes.
• Created test plans for new modules based on System Design Documents and Functional Requirements Documents.
• Modified test plans according to changes made during requirements verification meetings.
• Created test cases for new functionality.
• Created automation scripts using IBM Rational Functional Tester to test new functionality.
• Diagnosed, root caused and documented issues found during testing of new functionality.

Software Systems Test Engineer

Confidential

Responsibilities:

• Meet wif teh customer and peers and use system documentation to determine and document procedures for validating application requirements.
• Using HP Quality Center - Write test plans based upon system requirements. Create test cases and test sets, and perform manual Systems Acceptance Tests in accordance wif approved test plans.
• Develop test scenarios and provide support for User Acceptance Testing.
• Coordinate wif various stakeholders to resolve pre-requisites for testing and issues found during tests.
• Write test summaries and test problem reports. Use PVCS Tracker to record test problems.
• Regularly participate in test readiness and release readiness meetings.
• Apply approved technical approaches to testing to ensure dat applications are evaluated in an analytical and systematic manner.
• May assist test automation developers in creating and maintaining automated test scripts.
• Develop test options wif varying degrees of scope, risk, and duration and present to customer for approval.

Software Test Engineer Lead

Confidential

Responsibilities:

• Lead of a team of 6 Software Test Engineers for teh Windows Server Serviceability Engineering (WinSE Server) group.
• Responsible for teh management of integration testing test passes via teh TERRA automated system.
• Responsibilities include documenting processes and training and assisting team members on STE process and triage issues.
• Coordinating teh specifications of teh test pass guidance wif teh WinSE Server test leads and editing .xml schedule files to satisfy test pass guidance.
• Initiating, monitoring and triaging a Windows SE test pass and providing test pass specific leadership to team members which includes prioritization and appropriation of triage related tasks, answering process and triage related questions and providing ad hoc training as needed.
• Diagnosing and root causing issues wif teh TERRA automated system and reporting teh issues to teh appropriate follow-ups, filing bugs for each issue or adding to existing bugs.
• Diagnosing and root causing issues wif TERRA reported to me by members of my team, distilling teh information reported to me, and reporting those issues to teh appropriate follow-ups, filing bugs for each issue or adding to existing bugs.
• Creating thorough, comprehensive, detailed reports for each test pass complete wif charts and statistics.
• Engage Microsoft manager in “Post-Mortem” discussion after each test pass to identify areas of strength and areas which require improvement. Collaborate wif manager and members of our team to streamline existing process and develop new processes/tools to increase efficiency/productivity for teh next test pass.

Software Test Engineer Lead

Confidential

Responsibilities:

• Initiating, monitoring and triaging integration testing test passes for teh Windows Core Operating Systems Development (Windows COSD) group via teh TERRA automated system.
• Diagnosing and root causing issues wif teh TERRA automated system and reporting teh issues to teh appropriate follow-ups, filing bugs for each issue or adding to existing bugs.
• Creating thorough, comprehensive, detailed reports for each test pass complete wif charts and statistics.

Software Test Engineer

Confidential

Responsibilities:

• Verified daily builds of Longhorn Server via a test pass of both automated and manual jobs in which teh automated jobs were scheduled through WTT (Windows Testing Technologies). Verified daily builds of Longhorn Client Service Pack 1 (installed via slipstream) via a separate automated test pass.
• Ran upgrade/downgrade tests on daily builds of Longhorn Client

Software Test Engineer

Confidential

Responsibilities:

• Managed and ran graphics testing through a Windows Testing Technology Server (WTT Server) on an array of PC’s running Microsoft Windows Vista to test LDDM (Longhorn Display Driver Model) drivers for Nvidia and S3 graphics. Software testing included both manual and automated testing. Triaged both kernel mode and user mode breaks caught by teh debugger and used debugger commands to determine what module or process (me.e. block of code) caused teh break; determined which development team to send teh break to for further investigation and resolution. Discovered and filed approximately 100 new bugs mostly regarding Nvidia and S3 LDDM drivers as well as some bugs in teh Windows Vista Operating System which me discovered while testing Nvidia and S3 graphics drivers.
• Created detailed reports summarizing teh results and highlighting teh points of interest for each automated test pass. Investigated each and every failed job for each test pass, researching teh job logs in WTT to determine teh nature of teh failure and working wif developers to either resolve teh failed job to an existing bug, or file a new bug.
• Set up and configured machines for Broadcom’s Scalable Networking Pack (SNP) component testing. SNP is a hardware-based offloading technology which relieves teh Operating System and theirby teh system's CPU, of certain networking related tasks in order to improve system performance. SNP is composed of three technologies: NetDMA (alias Black Diamond), Receive Side Scaling (RSS), and TCP Chimney (alias Blue Laser). Ran tests under varying scenarios for different components of RSS and TCP Chimney.
• Components tested included HTTP, Firewall, Winsock QoS, Winsock Direct, NetBT, NetSH and NetStat.
• Also set up and configured machines, including hardware, for Winsock Direct component testing for SAN Infiniband adapters.
• Continually managed GDR Stress testing on 25 PC's running Windows 2003 Server.
• Received highest possible score on performance evaluation.

Network Support Engineer

Confidential

Responsibilities:

• Remote Client Access Support technician from October 2000-March 2003, responsibilities included troubleshooting and resolving remote connectivity and Radius authentication issues and issues wif teh PIX firewall. Promoted to teh Compaq merger team in March of 2003. Resolved issues submitted to teh merger team by teh help desk through Remedy’s BLT ticket tracking software. Responsible for resolving or escalating merger related issues, especially, but not limited to, issues regarding pre-merger Compaq employees connecting to teh HP extranet and accessing network shares.
• Possessed Windows 2000 Domain Administrator privileges for teh Compaq Americas domain after teh Compaq merger.
• Manipulated domain user accounts and global groups so as to acquire proper rights and permissions for domain users to access needed network resources.
• Assisted in diagnosing and troubleshooting other merger related connectivity and performance issues TEMPeffecting end users and provided thorough and detailed documentation when escalating to appropriate tier 3 team.