SUMMARY
Software Engineer with experience in the entire development and test life cycles (SDLC and TDLC) – requirements through customer support. Web programming, software quality assurance, change management & source code control, development, maintenance, highly reliable and available systems, user and internal documentation, training, user interfaces, testing, test automation, system build, testbed build, deployment & installation, release coordination, requirements, design, process improvement. Review requirements, specifications, design, test sets and test cases.

SKILLS: Unix (Sun/Solaris, HP–UX, IBM/AIX, Linux), shell, Perl, Python, C, awk, Windows, MS Word, Excel, PowerPoint, Visio, Oracle, sqlplus, Quality Center, ClearQuest, QTP, Apple Mac, problem solving, test automation, quickly learn new technologies, work with people in many locations around the world, able to change projects with no notice, Agile and more structured development and test environments, handle multiple projects at once, rarely miss a deadline.

PROFESSIONAL EXPERIENE

Confidential,Jersey City, N. J. (4/21/2008 – 1/20/2011)
QA Engineer – Advisory
Windows, Sun/Solaris, IBM/AIX, Unix, shell, awk, batch jobs, network, APL, SVN

• Defined, improved and implemented QA and development processes. Helped document the SDLC and TDLC so people could understand them and be less reluctant to follow them. Many problems and defects were eliminated.
• Initiated work on a program to facilitate delivery of code to QA and guarantee that the code that is tested is the code that is deployed. Currently being used by all developers and testers.
• Part of a team in the US and India developing a test automation framework – from requirements through implementation. Looked into ways to automate testing of a pseudo-GUI application running in a terminal window. Found a way to semi-automate testing of this application. Enhanced someone else’s test automation system to simplify determining and recording pass/fail results.
• Designed and implemented a program and process for securing client data by masking and encrypting it. Allowed the company to satisfy client and certification requirements. Documented and trained people to use the masking program. Recorded it so people could train themselves.
• Taught a class in Unix twice. I was asked to do it a third time, but other projects had higher priority.
• Worked with testers and developers to test enhancements to a complex legacy application and the APL interpreter it’s implemented in. Wrote test plans and test cases.
• Worked with the computer department to resolve potential and actual problems I uncovered.

Confidential,N. J. (12/10/2005 – 4/16/2008) Comverse bought our division from CSG.
Lead/Advisory Test Engineer
Windows, Sun/Solaris, IBM/AIX, HP-UX, Oracle, SQL, shell, awk, ClearQuest, batch jobs

• Developed methods for turnkey installation of a multi–machine telecommunications billing system using RPM on Linux and IBM. Streamlined the process. Automated various parts of the process, including parts that had been declared to not be automatable. Found ways to do things that had been declared impossible to do. Improved the efficiency of the process.
• On loan to development group for installation. Worked closely with developers to get the information we needed for installation. My ability to work with other people was one of the reasons I was chosen for this assignment.
• Moved into a group responsible for testing reliability, availability, maintenance, and installation of the entire system. Used IBM’s ClearQuest for recording and tracking defects. Brought a new viewpoint to the group that allowed me to develop tests that improved efficiency and test coverage.
• Continued with the work I was doing in CSG. (See CSG, below.)

Confidential,N. J. (3/1/2002 – 12/9/2005) CSG bought our division from Lucent.
Lead/Advisory Test Engineer
Windows, Sun/Solaris, IBM/AIX, HP-UX, Oracle, SQL, shell, awk, Perl, Python, batch jobs

• System tester and test coordinator for telecommunications order management and prepaid billing systems and a fraud management system. Wrote test plans and testcases. Wrote Python and Perl programs to fully automate all testcases for the part I was responsible for. Tested installation of the system. Tested the user documentation, and suggested changes to make it easier to read and use.
• Designed and wrote a test automation system in Perl. This allowed me to automate 100% of my tests. Sped up testing from months to days. It was used for all Unix test automation, not only my tests.
• Part of a team reviewing system requirements and high level designs before they’re implemented.
• Worked with other people to improve the process for all of System Test. Worked closely with the Software Quality Process Management team.

Confidential,Murray Hill, N. J. (1973 – 2/28/2002)
Member of Technical Staff
1/15/2000 – 2/28/2002 – Windows, Sun/Solaris, Oracle, SQL, shell, awk, make, batch jobs

• System tester for telephone fraud management and prepaid billing systems. Unit and integration testing before the system was complete.
• Reviewed requirements and architecture. Found many problems – ambiguous, inconsistent, incomplete, untestable. Wrote test plans and test cases – with other team members.
• Functional, performance, command–line, and GUI testing. Reported all bugs in bug tracking system. Maintained test case metrics. Automated tests so they could easily be run on new deliveries.
• Wrote shell/awk scripts for other testers and myself – reduced errors in repetitive tasks (e.g., environment setup, start/stop the system); wrote a common test script template so all testers could run all tests; analyzed test results.
• Proposed enhancements to the call generation simulator to aid in testing and interpreting the results. Most were implemented.
• Proposed and implemented improvements to the installation process – I became the owner of it.

6/1/1998 – 1/15/2000 – Windows, Sun/Solaris, shell, awk, batch jobs

• System tester for an internet telephony system (VoIP) for service providers.
• Quickly learned the system – configured and demonstrated it to developers and testers.
• Developed test plans and test cases, and ran the tests. Uncovered many bugs. Worked with developers to diagnose problems and test fixes.
• Designed and set up a test lab to minimize the need for re–installing hard drives and rewiring for different tests – a time consuming, error–prone process in previous testing. Minimized resource conflicts among testers.

7/1/1973 – 6/1/1998 – Unix, Sun/Solaris, HP–UX, C, shell, awk, batch jobs

• Began work on improving/automating a system for generating licenses for a large CAD (Computer Aided Design) system (BLDA). It would have been web-based, but work ended because the CAD Lab was sold.
• Developed a web–based document ordering system using CGS and HTML. The order went directly to the vendor. The vendor acknowledgement was automatically analyzed and recorded. Exceptions were sent to a clerk.
• Release coordinator for a large CAD system (BLDA). Worked closely with project management, testers, and developers to make sure we accepted only program changes that were requested and passed all tests. Worked closely with the sales team to make sure that customers received everything they paid for, and nothing else.
• Designed, built, and maintained the BLDA testbed. Structural integrity was guaranteed by automated incoming inspection – the delivery bed was guaranteed "correct by construction". Worked closely with project management and developers to establish requirements for delivery of software to system test – helped developers adapt to the rules. Sped up a co–worker\'s testbed verification program by 97.5% (10 hrs to 1/4 hr). Wrote most of the infrastructure verification programs, including extensive tests for them.
• Responsible for deployment of the BLDA CAD system. Customers praised the installation system that I wrote in the C language. Designed and implemented a system for secure distribution on CDs.
• Proposed and implemented a process for handling asynchronous release of parts of the CAD system. The process greatly reduced effort and helped insure that various CAD tools worked together.
• Conceived of, designed, developed and implemented a software quality assurance system:
• conceived of and developed an automated program librarian, with incoming inspection
• conceived of and developed a fully automated regression test system that featured a "fuzzy" diff for text files and a "smart" diff for graphics files
• designed and implemented a journal and playback system to facilitate error recovery for users, bug location, and regression testing - this system allowed noninteractive testing of an interactive graphical layout editor

This work significantly increased quality and productivity.

• Provided project management support for a chip/circuit simulator. Worked with developers to rebuild their programs with the latest libraries, and to deliver their programs on time.
• Developed and implemented a system for delivery of software to system test in a distributed development environment - including automated incoming inspection for quality control. This guaranteed that the delivery bed would be structurally correct after the delivery - without risking corruption of the delivery bed by making a bad delivery.
• Published papers on software quality assurance, user interfaces, an automated librarian, and an automated regression test system that I designed and wrote.
• Member of teams developing and maintaining a VLSI layout editor and circuit simulator. Fixed bugs and added many new features. Made programs run much faster. Used SCCS and make to build the programs.
• Developed, maintained, and documented a general utility library.
• Ported CAD programs to Cray, VAX, and SUN workstations.
• Tested VLSI chips and dips. Developed methods and programs for extensive automated characterization of devices. Predicted poor reliability of an IC based on high leakage current. This prediction was rejected by developers, and then proven correct.

Confidential,N. Y. (1969 - 1973)
Staff Engineer
Responsible for initiation, conception, design and carrying out of experiments to determine failure rates, modes, and mechanisms of LSI circuits and display devices. Semiconductor aspects of new technologies: insulation, metallization, glow discharge. Developed theoretical – empirical mathematical-physical models for failure mechanisms.

EDUCATION PhD – EE
MSE – EE
BEE – EE