SUMMARY:

I am an Information Technology professional with over 23 years of experience. I have held many different titles in my career and each one contributed to me being well versed in all stages of the software development life cycle. I have worked on projects directly affecting external clients, as well as ones for internal departments. Due to this experience, I have the ability to foster great relationships across the board, internal/external, technical/non - technical, operations/C-level. In the end, the benefits are directly felt by my clients. Each position that I have held has added to my worth as a successful team player at any stage within software development. I would like to continue to be involved in this field, but would like to take on the primary role of a Quality Assurance Analyst.

TECHNICAL SKILLS:

• SQL Server (TSQL, SSRS, SSIS)
• MS Office
• HTML
• JavaScript
• Visio
• VBScript
• CSS
• Paint Shop Pro
• GIT
• Selenium

EXPERTISE AREA:

• Ability to Work Both Independently and in a Team Based Environment
• Critical and Analytical Thinking
• Pay Great Attention to Detail
• Problem-Solver
• Perfectionist
• Flexible
• Initiative Taker
• Proactive versus Reactive
• Self-Motivated
• Strong Written and Verbal Communication
• Unique and Creative ‘Outside the Box’ Thinker
• Work Efficiently in a Fast Paced Environment
• Ability to Communicate with both Technical and Non-Technical Resources
• Empowerment
• Some Experience with Agile Development Process
• Experience with Testing Mainframe and Web Based Applications
• Facilitation and Elicitation Skills
• Thorough Understanding of Each Phase of the Software Development Life Cycle
• Willingness to Learn New Technologies
• Solid Understanding of QA Testing Environments
• Client Centric

PROFESSIONAL EXPERIENCE:

Business Analyst/Business Intelligence Engineer

Confidential, Omaha, NE

Responsibilities:

• Gathered requirements for client’s reports
• Created stored procedures for use in creating business reports
• Created all database objects (tables, views, stored procedures, synonyms, indexes, etc) for use in the reports
• Used Logi Analytics as the tool to create the reports
• Additional languages used in report creation: HTML, CSS, XML and JavaScript
• Created automated test scripts using Selenium to test our web applications
• Set up version control using GIT for my report files
• Worked on some C# projects as time allowed

Application Architect/Business Analyst

Confidential, Omaha, NE

Responsibilities:

• Identified processes across the company that we could automate or departments heard about our team and asked us to create an application for them
• Many manual processes utilized Excel spreadsheets or Access databases that were getting out of hand for their creators
• Gathered requirements with the individual departments and employees to understand their needs and how we could make their jobs easier, adding enhancements to further simplify processes
• Integrated classic ASP with some of the ProTERM mainframe applications we built to in corporate a GUI front end
• Personally wrote over 1 million lines of ASP Classic code in a text editor to create the web applications
• Created SQL Server databases, tables, stored procedures, etc to house the data
• Created DTS packages / SSIS packages to populate the database with data imported from a variety of sources, such as flat files, spreadsheets, CSV files, other databases, etc
• Responsible for developing and testing all of my applications prior to turning the code over for the users to test
• Wrote documentation for each of the 15 or so applications that I created and was responsible for
• Maintained and updated the code when users asked for enhancements or data repositories changed
• Understand how develop applications using best practices and taking a business user point of view
• After a re-organiziation, I gained further responsibilities as an implementation coordinator for a client-facing GUI tool called Evolve
• Assisted the Testing Center of Excellence in identifying test scenarios and creating appropriate test plans to test Evolve
• Coded some projects for Evolve, which was written in C++
• Used FDR Query

Software Developer / Senior Software Developer

Confidential, Omaha, NE

Responsibilities:

• Utilized ProTERM programming language, which incorporated a terminal emulator and was similar to C-like scripting, to create the tool named FirstTest
• Created training tutorials and user documentation and lead courses on how to utilize the tool, which was for internal users
• Created test scripts for regression testing, they were used by the testing teams
• Outside of the box thinking took the technology for automated testing within the test mainframe environment and spearheaded the concept of using the tool to automate manual transactions that various departments enter into production on a daily basis
• Tasked with learning HTML and creating web pages for each of the testing teams on our intranet

Project Manager

Confidential, Omaha, NE

Responsibilities:

• Performed duties under limited supervision, applying a broad knowledge of principles, practices and procedures…my two previous positions within the company prepared me to excel in this position
• Identified and implemented process improvements and best practices
• Accountable for delivering all of my projects on time, within budget, and within scope.
• Facilitated and coordinated cross-functional, cross-departmental, cross-company teams that are responsible for all aspects of a project, from initiation to closure
• Utilized the in 6 Sigma methodology
• Insured that the project delivery processes and implementation management processes were followed
• Provided clear and concise project communication; both written and verbal to all key players involved with the projects, including integration testers and documentation writers
• Wrote requirements based upon client requests, identifying all systems affected by the requested change
• Wrote test scripts for use in unit, system, and client acceptance testing for the larger projects
• Responsible for signing projects off after successful unit and system testing
• Responsible for collaborating with the user documentation writers and trainers to create a new user manual for Cardholder Correspondence and corresponding training materials
• Since I knew how to test from my previous position, I was in charge of creating test scripts for Y2K testing
• Trained other project managers how to test their products for Y2K
• Present during Y2K testing and helped open Incident Reports for testers, available to answer questions or give suggestions to the project managers and product owners

Quality Assurance Coordinator/Senior Analyst

Confidential, Omaha, NE

Responsibilities:

• Participated in requirements gathering and project design meetings, provided input when necessary
• Created test plans and scripts for manual testing of small to extra large projects based on business requirements and technical design documents
• At the time I worked in this department, there were no automated tools used to test the mainframe and its use of Bigfoot mapping so all of the testing was performed manually
• Identified, isolated and tracked bugs throughout the testing process
• Worked both independently testing my projects and as part of the group that performed regression testing
• Previous experience writing user documentation for the same systems I tested was instrumental in making me a senior analyst in good time
• Ability to communicate effectively with developers, documenting identified problems as incident reports and explained how to replicate them
• Used SQL to query mainframe RD2 databases to identify accounts matching criteria for use in test cases - if none existed, then had to manually create the scenarios needed to test new functionality
• Developed standards and procedures to determine product quality and release readiness
• Worked closely with development and product teams
• Ensured that the functionality developed matched the expectations that the clients have based upon business requirement specifications
• Used Microsoft Excel to track testing statuses for all projects and issues
• Provided reports for upper management detailing what projects were tested and the outcomes of those tests
• Trained new employees on testing procedures, processes, and best practices, as well as on how the various systems within the mainframe environment worked
• Manually tested cardholder statements and correspondence as part of both regression testing and individual project testing

Documentation Writer/Analyst

Confidential, Omaha, NE

Responsibilities:

• Wrote clear, concise, and precise user documentation manuals for all of FDR’s systems
• My expertise was documenting the Product Control File (PCF), Cardholder Non-Monetary Transactions, and Cardholder Account Maintenance
• Interacted with SMEs daily to understand the processes and procedures enough to write documentation for a non-technical audience
• Utilized imaging software to provide the proper visuals needed to enhance the written word
• Minimal rework, if any, was required when feedback was provided by editors