TECHNICAL SKILLS:

System Admin /QA Lab Management: Mac OS X server, Win 95/98 NT/2000 Server/, Unix (Solaris, HPUX and AIX)Linux (Red Hat Server, Fedora and Centos). Setup for Kerberos and ipchains and backups.

Automated Testing Languages: Perl, Python, TCL/Tk, C, C++, Shell Script, TSL and LabView. UML

Web Protocols: HTML 4.0, XSL, XML

Web testing tools: Selenium/Python, Webdriver (Selenium 2 for Python), Perl and Wire Shark

Network Protocols: SSL, PKI, TCP/IP, NFS, FTP, TFTP, UDP, SMTP, LDAP IEEE 1588

Web Server: Apache

Bug reporting tools: Jira, Clear Quest, DDTS, Remedy and Bugzilla, Radar Espresso

MS - Suite: MS-Word, MS Excel, MS-Project, MS Visio, MS Outlook

Data Bases: Oracle 8i/9i/10g/12g, MySQL with MySQL Workbench

Data Base Tools: TORA/TOAD for Oracle database

Testing Tools: Perl, Python, Selenium, TCL/Tk, Expect

Configuration & Deployment Tools: Jenkins, Git, Maven, Ansible, Yum, CVS, and Clear Case

Framework: Robotframework, Behave, Pytest, TeamCity and a Python Intel developed Framework

PROFESSIONAL EXPERIENCE:

Confidential

SDET/Contractor

Responsibilities:

• Wrote Python automation Function Level Test Cases for the REST API Server portion of the Hortonworks/ Confidential system.
• Wrote Python automation test framework (pytest TDD) Hadoop as a Service (HAAS) integration test cases.
• Wrote manual Excel driven verification and validation test suites.
• Wrote Python scripts to configure and deploy Horton works Big Data operations (Hadoop) and its special deployments.

Environment: Linux and Mac OSX Protocols used: SSL, REST, LDAP and XML Automation Python and XML Used Radar for bugs Git for versioning

Confidential

Principle System Architect

Responsibilities:

• Performed Architectural for the AI Project
• Acted as Project Manager as well as QA Manager for the Deep Sea Project.
• Interfaces with Confidential management and Agents.
• Wrote AUV AI documentation for the Deep Sea Project.
• Wrote deployment plans, schedules and biding documents to support the Deep Sea Project.
• Wrote software/hardware specifications to allow AUV communication to remote systems.
• Wrote design documents for a new machine leaning algorithms and AI integration plans.
• Re-wrote Production Python code to adapt the Cassandra product into the existing AI project.
• Performed DevOps, Program Management ( Confidential ) and QA Manager tasks for the Deep Sea Project.
• Perform Project Management (Agile Scrum) for the robotics and AI for the Deep Sea Project.
• Performed QA Manager tasks from 2009 to 2016 for the Deep Sea project.

Environment: Linux and Mac OSX Protocols used: SSL, REST, LDAP and XML Automation Python and XML GitHub for versioning.

Confidential, Milpitas, CA

Software Engineer in Test

Responsibilities:

• Wrote Python automation Function Level test cases, test plan and integrated the test cases into a BDD Test Framework.
• Wrote documentation for the Test Framework.
• Performed manual ad hoc testing when required.

Environment: Linux Mac OSX Protocols used: SSH, LDAP and XML Automation Python and XML Used JIRA for reporting Git for versioning

Confidential, Hillsboro, OR

Automation QA Engineer/Contractor

Responsibilities:

• Wrote Python automation Function Level Test Cases for the REST API Server portion of the Intel Analytics system.
• Wrote SCALA automation to replace some of the manual test cases.
• Participated in Agile Sprint sessions.
• Wrote Python automation that replaced the SCALA test cases.
• Wrote Python scripts to verify Big Data operations (Cassandra/Hadoop), Machine Learning algorithms (LBP, LDA, ALS and Page Rank)

Environment: Linux Protocols used: REST, HTTP, HTTPS, Json and XML Automation Python and Json

Confidential, Culver City, CA

Sr. Automation QA Engineer

Responsibilities:

• Test Plan for evaluating the ISP e-commerce backend APIs and database
• Created the evaluation ecommerce APIs and database using QTP 10.
• Web testing using Selenium using Perl, Python and shell scripting.
• Technical lead for three (3) junior QA engineers
• Participated in Agile Sprint sessions
• Web evaluation using VMware for OS and browser evaluations
• A/B testing for the various Confidential commercial offerings. A/B testing (also known as split testing) is a method of comparing two or more versions of a webpage against each other to determine which one performs better.
• Entered and validated defects using the web based bug tracking tool E-Track

Environment: Solaris, Windows, Linux & Mac OS X Protocols used: HTTP, HTTPS and XML Automation QTP/QC, Perl and Python

Confidential, San Jose, CA

SQA Automation Engineer

Responsibilities:

• Created the evaluation TMS Client using Perl automation (API testing).
• Cleared Bugs posted using a “home grown” bug-reporting tool called CMVS.
• Evaluated the UI and CLI interfaces to the TMS Client.

Environment: Mac OS X, Windows, Linux Protocols used: NFS, AFP, XML and SSH Automation Perl

Confidential, Livermore, CA

SQA Automation Engineer

Responsibilities:

• Created the in house CAD tools evaluation automation for QA use (API testing).
• Cleared Bugs posted using a “home grown” bug-reporting tool called Mantis.

Environment: Windows and Linux Test tools: Perl, Python and Selenium

Confidential, Cupertino, CA

SQA Engineer

Responsibilities:

• Created the evaluation automation for Operating System evaluation using various network protocols
• Created automation to validate the Confidential Xsan (SAN)
• Cleared Bugs posted on the Confidential bug-reporting tool “Radar”.
• Used SSH and rlogin to connect to the test lab systems.
• Tested Secure Sockets (SSL) as part of the Product Evaluation

Environment: Mac OS X, Windows, Linux Protocols used: HTTP, HTTPS, Samba, SSH, XML NFS, AFP and LDAP

Confidential, Sunnyvale, CA

SQA Engineer

Responsibilities:

• Wrote Black Box manual test procedures for multi tiered servers and to validate the Filer software.
• Performed Black Box ad hoc testing

Environment: Windows, UNIX, Linux Protocols used: SSH, NFS, HTTP, HTTPS, XML Test tools: Perl, Python for Windows

Confidential

Technical Automation Engineer

Responsibilities:

• Performed white box testing of the Order fulfillment Oracle 9g backend transaction.
• Established Test accounts: UID, GID, Home Directory path
• Used SSH to connect to the test lab systems.
• Participated in Agile Sprint sessions
• A/B testing for the various Confidential Project web access by Windows, Linux and Mac OS. A/B testing (also known as split testing) is a method of comparing two or more versions of a webpage against each other to determine which one performs better.
• Tested Secure Sockets (SSL) as part of the Project Evaluation

Environment: UNIX Protocols used: XML SSL HTTP, and HTTPS. Test tools: Perl Bug tracking Remedy Source Control: Perforce

Confidential, San Jose, CA

Automation Engineer

Responsibilities:

• Verified the functionality, performance and stability of the Device Under Test using Solaris based c code.
• Top Board mixed signal evaluation code for Lab View and Rack-And-Stack ATE.

Environment: Solaris Protocols used: FTP, Telnet Code Development: Perl, Python and C++.

Confidential, San Jose, CA

SQA Automation Engineer

Responsibilities:

• Responsible for evolving test cases to verify the functionality, performance and stability of the AON TCL test suite from Cisco’s India Based partner
• Perform integration, System, regression, and User Acceptance of the TCL test suite into the Regression testing suite.

Environment: Linux Protocols: SSH, SFTP, Telnet and TCP/IP Bug tracking: DDTS Test tools: TCL

Confidential, Palo Alto, CA

SQA Automation Engineer

Responsibilities:

• Responsible for evolving test cases to verify the functionality, performance and stability of the Linux based embedded clock system.
• Created the evaluation automation and test reporting.
• Used Ethereal to assist in the automation development
• Used SSH to connect to the test lab systems.
• Tested Secure Sockets (SSL) as part of the Product Evaluation
• C++ and LabView.

Environment: Linux Protocols: multicast, XML, SSH, HTTP, FTP, Telnet and TCP/IP Test tools: Perl, Python, C++ and LabView

Confidential, Mountain View, CA

SQA Engineer

Responsibilities:

• Created manual and automation Test Plans and Procedures to evaluate the Newsroom Pipeline (API testing).
• Performed Hands-On white box backend and web based front end automated (Perl) and manual White Box ad hoc testing of the dataflow to and from the DB2 databases.
• Participated in the SCRUM meetings.
• Used OpenSSH to connect to the test lab systems.
• Evaluated Secure Sockets (SSL) on the remote servers.
• Kerberos/ipchains setup and evaluation.

Environment: Linux, Solaris Database: DB2 Web: Apache, RSS, Atom, Soap, Ajax

Confidential, Palo Alto, CA

SQA Engineer (Contractor/Technical Lead)

Responsibilities:

• Created manual and automation Test Plans and Procedures to evaluate the Order Pipeline section of the mySimon.com Web site.
• Lead 3 junior testers and provided Hands-On backend and web based front end automated (Perl) and manual White Box ad hoc testing of the Sybase to MySQL database migration.
• Linux/UNIX System Admin (QA Lab Management).

Environment: Linux, UNIX (Solaris and HPUX) Servers. Web Engine: Apache Database: Sybase 11.9.2 MySQL

Confidential, Reston, VA

Technical Lead QA Engineer (Contractor)

Responsibilities:

• Created manual and automation Test Plans and Procedures
• Performed Hands-On White Box ad hoc testing of the Rules and Sybase database validation both as automation scripts (Perl) and manual testing.
• As a Technical Lead: Provided Technical training and direction to a 6-person test team.
• Provided white box evaluation results of the Confidential Call Center (CRM).
• Used OpenSSH to connect to the test lab systems.

Environment: Linux, UNIX (Solaris and HPUX) Servers. Web Engine: Apache Database: Oracle 9i.

Confidential, Seattle, WA

SQA Automation Engineer

Responsibilities:

• Created manual Test Plans and Procedures to evaluate the Order Pipeline section of the Confidential Web site.
• Perform white box integration, System, regression, and User Acceptance testing for Billing Applications.
• Participated in the CCB and SCRUM meetings.
• A/B testing for the various Amazon commercial offerings. A/B testing (also known as split testing) is a method of comparing two or more versions of a webpage against each other to determine which one performs better.
• Used OpenSSH to connect to the test lab systems.

Environment: Linux and Microsoft Windows 2000 Advanced Server.

Confidential, Inglewood, CA

SQA Engineer

Responsibilities:

• Created ISO 9001 compliant Test Plans and Procedures to evaluate the Product.
• Wrote White Box test programs in VT 6.05 and Perl for multi tiered servers (API testing),
• Performed Black Box ad hoc testing.
• Tested Java implemented Web Pages both manually and with automation.
• Tested and installed LDAP communications for ADS for Containers, Domains, Users, and Groups.
• Used OpenLDAP on Red Hat Linux servers and Solaris 8.
• Verified CA's version of OpenLDAP using HP-UX servers
• Check the database using SQL Queries for the data entries.
• Tested the Exchange 2000 interfaces as they apply to LDAP and Active Directory.
• Used OpenSSH to connect to the test lab systems.

Environment: Unix, Linux and Microsoft Windows 2000 Advanced Server. Web Engine: Microsoft IIS. Databases: ADS native and Ingress.