QA Engineer Resume San Francisco, CA - Hire IT People

SUMMARY:

Excellent analytical skills and the ability to interpret technical data.
Excellent written and oral communication skills. Team player.
Working knowledge of software engineering and quality assurance processes
Analyze and report on search quality and performance.
Work closely with Product and Engineering Management, customer support, and customers to validate product use cases and requirements.
Collaborate with other developers to resolve issues to ensure a quality product is released on time.

TECHNICAL SKILLS:

Database testing. Mobile tools: DeviceAnyware. Agile/ Scrum and Waterfall environment proficiency.

WebTesting: basics of QTP, Winrunner, Toad DB Tool PC and Mac hardware and software proficiency. XML, SQL, HTML, HTTPS, JavaScript, PhotoShop, Word, Excel, PowerPoint, Access. Flash 8, MX2004, CS3, Action script viewers and editors, Java, Cold Fusion, Ajax, Atlas publishing tools, ZebraWindows XP, ME, 2000, NT, 98/95 administration experience.

Networking: TCP/IP, FTP, LAN, WAN, Internet, Intranet, Tech Savvy.

Bug Tracking: Elementool, Bugzilla, Mantis, RT, TFS, Octane, Tracker.

Virtual Machines: VMWare Server 1.0.4

EXPERIENCE:

Confidential, San Francisco, CA

QA Engineer

Responsibilities:

This position is with a company that provided international seasonal workers and AuPairs and internships abroad.
The application that we built is Java based.
There was also maintenance of old systems which were done in Cold Fusion.
The DB was SQL server.
I worked as the sole QA for both teams of developers (Java and CF).
This was in an Agile/SCRUM environment with 2 week iterations.
The CF side was more waterfall as it was mainly maintenance.
The dev team consisted of 5 Java and 2 CF developers.

Confidential, San Francisco, CA

QA Engineer

Responsibilities:

Utilizing many tools daily such as Zebra, TFS, a QA tool made in house Flash 8, MX2004, CS3, Action Script viewers, Atlas tools and many more.
I was able to verify functionality, look, feel.
Made sure everything was up to spec.
Mentored 4 QA team members as well as many producers, AdOps team members and worked closely with many external agencies to review process.

Confidential, Marina Del Rey, CA

QA Engineer

Responsibilities:

I was brought on in order to document all of these sites as there was no formal documentation present at that time.
I created architectural documentation on all sites.
I also created all the test cases and test plans for all these sites.

Confidential, Philadelphia

QA Analyst

Responsibilities:

QA analyst I was responsible in the testing of Ad Campaigns.
Testing all aspects of these rich media ads was set in a very high paced environment.
From conception to release, all ads took approximately 3 to 5 days.
The qa was done in a matter of hours of release from production and was live at the same time.
In a typical day, there were upwards of 20 ad campaigns that needed testing.
I worked closely with the other 4 analysts.
Testing was done by verifying redirects, click thru, redirect tracking, etc.
There were live ad checks for placements, panel testing for click tracking and activity tracking.
Web testing environment utilizing HTML, Flash and JavaScript as well as some SQL.

Confidential, Cupertino, CA

QA Engineer

Responsibilities:

I was engaged in driver and signal testing, functional testing, and acceptance/release testing.
I was 1 of only 2 QA engineers in the company.
There was a team of approximately 15 developers for both testers.
This was a hardware/software environment.

Confidential, San Ramon

Quality Assurance Engineer

Responsibilities:

I was expected to learn this product in a very short period of time.(1.5 weeks) Tests were done intensively and my participation in this product gave me great exposure to the whole upgrade which was enormous and functioned in many different ways due to many separate yet dependant services and mini processes.
I worked both in a 6 - person team closely with developers as well and autonomously.
This was a Client/Server environment using software

Confidential, San Francisco

Senior QA Engineer

Responsibilities:

I was part of a 9-person team. All were held accountable to different products yet were cross-trained to know the functionality of the other products.
I was accountable for a product called PWS, which was run on SQL, LDAP and Oracle, for the back-end.
Code was written in jsp. Other hardware and software was used as well. Testing was done with both automation and black box.
This was a web test environment utilizing HTML, Flash and JavaScript as well as some SQL.

We provide IT Staff Augmentation Services!

Qa Engineer Resume

San Francisco, CA

We'd love your feedback!

Resume Categories

Client Services

Job Seekers

Visa Sponsorship