Principal Software Engineer
CurrentCurrent Active Roles on the ARCHITECT PROJECT:-- Principal Software Engineer-- Technical Review Board Chairperson-- Risk Management Team Member-- Risk Management ChairpersonPAST INVOLVEMENTS:Agile software development with scrum.CAPA representative for software team.Software integration testing, including the review of Functional Descriptions, Feature Description Documents, troubleshooting, and root cause analysis; the development of test design documents and informal protocols; the executing of informal protocols in order to assess build readiness; the review of user needs, product requirements, and use cases.Software design verification, including the review of software requirements and hazards; the creation of test design documents; the writing of formal protocols; the executing of formal protocols; the analysis of test case coverage; and the creation of test summaries for software increments that include metrics on coverage, traceability, and defects.Software Systems Engineer, including the creation of Feature Description documents and the writing of software requirements.Fault/issue determination, troubleshooting, and root cause analysis during informal and formal testing activities.Mentor software test engineers as needed and direct junior software testers in completing their work in order to reduce risk to the overall program.Confirmation of the configuration of the software work products.Advanced operation and maintenance/repairs of instruments, including the creation of instrument maintenance logs and the troubleshooting of issues found during testing.Informatics & Software Systems SW Development Process Definition, March 2010 to March 2012Maintenance of process documents as per FDA regulations, including the updating of documents, the collating of edits from document stakeholders, the submission of revisions to an approved storage location, and the confirmation that all users are trained.