SUMMARY:

• Possesses a Master s Degree in Software Engineering, and extensive experience in Agile, Scrum, DevOps, software configuration management, software testing, build automation scripting, continuous integration, and build releases.
• Detail - oriented; skilled at defining, documenting, and enhancing build procedures.
• Ensures timely completion of high-level projects, resulting in improved product delivery time, accessibility, and profitability.
• Technical skills are balanced by strong communication and interpersonal skills; easily builds rapport with diverse stakeholders. Quickly masters new technologies and methodologies.
• Streamlined production, reduced costs and development time, enabled faster releases of product software, introduction of more new products in a wider range of new markets, and increased revenue by writing and updating build automation scripts to automate integration team tasks.
• Collaborated with Developers, SQAs, and other stakeholders in multiple Confidential and Confidential centers worldwide to elevate the quality of products developed for delivery globally.
• Improved build cycle time and quality by writing a complete set of build and test procedure documents (which had never before been properly documented), and were later utilized as a model for similar documents by other Confidential and Confidential teams. This process definition, documentation, and improvement helped the Confidential and Confidential integration teams complete builds for a far larger set of build lines and markets in less time overall
• Reduced cycle time, enabled product lines to achieve on-time delivery of mission-critical deadlines, and boosted profits by working with integration and development teams at Confidential and Confidential centers worldwide to debug and solve serious problems, which enabled builds to be published in a timely manner.

EXPERTISE AEEA:

• Agile Scrum DevOps Change Management C and C++ Programming Software Engineering Continuous Integration
• Windows Kanban Kaizen Research & Development Quality Control Debugging Lean Cloud Computing Visio
• Microsoft Office Python Process Documentation Process Improvement Training & Mentoring Docker Azure AWS

PROFESSIONAL EXPERIENCE:

Confidential, Lincolnshire, IL

Software/DevOps Engineer

Responsibilities:

• Interacted well with Development and SQA test teams, using my past experience as a developer and SQA tester. Did self-instruction in DevOps procedures, and used DevOps procedures in my frequent interactions with Development and SQA Test teams.
• Had onsite training in Agile and Scum procedures along with self-instruction. Used Agile and Scrum procedures while on the Confidential Software Integration Team. Helped manage bi-weekly Scrum “sprints” using the Version One Scrum automation software tool.
• Set up, utilized, maintained, inspected, and tested the Jenkins continuous integration tool, which launched a series of builds overnight, each with preset inputs at specified days and times.
• Utilized Perl, Groovy, and Windows Batch Scripts for build automation scripting; Jenkins for Continuous Integration; and a GUI build tool called Visual Build Pro which called Perl scripts and issued commands to call version control, compile the builds, and check in build packages to version control.
• Used 3 Master Windows Servers and 6 Slave Windows Servers, for performing builds and for testing changes in build automation scripts. Created Windows Batch Scripts, containing Windows commands, which were called by Jenkins jobs to perform the more difficult steps. Jenkins also called Groovy scripts. The Jenkins system consisted of a set of Jenkins "jobs" which were called in sequence, to carry out the builds.
• Served for six months as Scrum master for the integration team, and created a training document to define Scrum terminology and procedures. Used and performed updates in VersionOne software to track Scrum team projects and hours worked.
• Trained and mentored new integration team members.
• Used Mercurial for version control in my first year at Confidential . Later served on a committee which investigated other version control systems, and then recommended StarTeam as a better alternative to Mercurial.
• Mastered and earned designation as a power user of the StarTeam version control system to produce views, folders, and files used to track the versions of Confidential software files. Created StarTeam commands in automated build scripts.

Confidential, Lincolnshire, IL

Software Engineer

Responsibilities:

• Conducted SCM builds for software used in Confidential electronic diagnostic devices to enable technicians to communicate with onboard computers in cars/trucks, diagnose problems, and perform repairs.
• Installed and tested software on Confidential diagnostic devices. Wrote test reports and change requests for developers.
• Led a team in debugging failed diagnostics tool builds, including those caused by compile errors, build script errors, incorrect file versions, or broken dependencies.
• Aided in improving the readability of Excel spreadsheets used to record the build properties of each Confidential product/market combination to be built in each six-month release cycle.
• Represented the Confidential integration team at the Confidential Tools Rapid Continuous Improvement Event; proposed numerous rapid continuous improvements to enhance Confidential software processes, productivity, and profitability.

Confidential, Libertyville, IL

Senior Software Engineer

Responsibilities:

• Performed, debugged, tested, documented, and released CDMA SCM builds for cell phone and bootloader lines, with an extremely high level of reliability.
• Trained and mentored new team members in build procedures.
• Interacted well with Development and SQA test teams, using my past experience as a developer and SQA tester.
• Acted as senior problem solver for SCM builds performed by the CDMA SCM team at the Libertyville and remote centers.
• Utilized the Klocwork static code analysis tool to identify logic errors, memory leaks, and similar issues in cell phone code.
• Automated the cell phone build process by using Perl, Makefiles, and UNIX to create build scripts.
• Mastered the ClearCase version control system used to create views, folders, and files for tracking versions of software. Created ClearCase commands used in automated build scripts to check in, check out, and copy files.
• Continued to write cell phone code for the Feature Database application while still a member of the integration team.
• Maintained development schedules, expedited cell phone lines’ time to market, and increased profitability by completing large-scale Perl projects, including a 7,000-line Perl script that automated a key phase in the cell phone build process.
• Authored a 75-page CDMA build procedure manual, after quickly learning how to perform CDMA cell phone builds.

Software Engineer

Confidential

Responsibilities:

• Wrote C and C++ cell phone application code as a member of the Voice Recognition and Personalize software development teams. Debugged compile errors. Used cell phone simulators to test cell phone code quality and reliability.
• Updated input files for the Data Resource Manager cell phone application weekly.

Confidential, Lisle, IL

Software Engineer/SQA

Responsibilities:

• Created scripts, websites, and cron jobs to monitor and display information on hardware and software CRs (Change Requests), which aided developers and managers in monitoring bug fixes.
• Developed internal Confidential websites that displayed current information on Confidential CRs and continuously updated graphs providing statistical information on progress towards closure of CRs.
• Created scripts, and used Microsoft Access, to automate data collection and display.
• Created documents and checklists to define and improve SQA processes.