Experience

Vitalograph

• Ireland
• Medical Equipment Manufacturing
• 100 - 200 Employee

• QA Audio Analyst

  • Apr 2018 - Present

  I currently work as a QA Audio Analyst. This involves: Monitoring the performance of Audio Analysts to ensure the sessions they complete are tagged consistently and accurately. Documenting the results of any monitoring that has been carried out. Assisting analysts with any difficulties they encounter.

• Audio Analyst

  • Feb 2016 - Mar 2018

  I worked as an Audio Analyst at Vitalograph. I listened to audio and marked coughs from the subject. I then documented the number of coughs the subject had over the course of the session and uploaded the results to a web application. If the subject had a cough that was difficult to identify then I consulted with the QA team to determine what should and should not be marked.

• Software Test Engineer

  • Feb 2014 - Jan 2016

  I was working in the Software QA department in Vitalograph. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS required one or more test… Show more I was working in the Software QA department in Vitalograph. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS required one or more test cases and each test case contained a series of inputs and expected outputs to verify that the function was working as specified in the SRS. When it was not possible to test every valid value for a parameter I used equivalence partitioning to determine the inputs for a test case. When creating documents I also had to ensure that the correct document template was used and that everything was traceable. I checked for things such as the numbering for test cases matching the relevant numbers in the SRS, the input numbering in the results matching the numbering in the test case and so on.



QPTech Ltd

• Ireland
• Information Technology & Services
• 1 - 100 Employee

• Software QA Engineer

  • Dec 2012 - Oct 2013

  I was working in the Software QA department in Vitalograph as a contractor for QPTech. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS… Show more I was working in the Software QA department in Vitalograph as a contractor for QPTech. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS required one or more test cases and each test case contained a series of inputs and expected outputs to verify that the function was working as specified in the SRS. When it was not possible to test every valid value for a parameter I used equivalence partitioning to determine the inputs for a test case. When creating documents I also had to ensure that the correct document template was used and that everything was traceable. I checked for things such as the numbering for test cases matching the relevant numbers in the SRS, the input numbering in the results matching the numbering in the test case and so on. Show less I was working in the Software QA department in Vitalograph as a contractor for QPTech. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS… Show more I was working in the Software QA department in Vitalograph as a contractor for QPTech. My main role was to execute test cases, document the results and report any issues to the developers. I used Microsoft team foundation server to log any issues. When an issue was resolved I marked the bug as closed if I could not reproduce it. I also wrote test cases. I went through the software requirements specification (SRS) and determined how the software should be tested. Each function in the SRS required one or more test cases and each test case contained a series of inputs and expected outputs to verify that the function was working as specified in the SRS. When it was not possible to test every valid value for a parameter I used equivalence partitioning to determine the inputs for a test case. When creating documents I also had to ensure that the correct document template was used and that everything was traceable. I checked for things such as the numbering for test cases matching the relevant numbers in the SRS, the input numbering in the results matching the numbering in the test case and so on. Show less



WIT

• Ireland
• Education Management
• 300 - 400 Employee

• Admin Internship

  • Aug 2011 - Aug 2012

  I was an intern at the W.I.T. Careers Centre. My main role was to update the website with new job opportunities using the Content Management System (T4 initally and Expression Engine). I assisted the team with other tasks including creating the monthly newsletter, sending out SMS messages, sending out surveys using Survey Monkey keeping track of various statistics and writing reports. I also created a table of contents application using HTML5, CSS3 and Javascript which allowed students to… Show more I was an intern at the W.I.T. Careers Centre. My main role was to update the website with new job opportunities using the Content Management System (T4 initally and Expression Engine). I assisted the team with other tasks including creating the monthly newsletter, sending out SMS messages, sending out surveys using Survey Monkey keeping track of various statistics and writing reports. I also created a table of contents application using HTML5, CSS3 and Javascript which allowed students to browse the contents of a USB memory stick Show less I was an intern at the W.I.T. Careers Centre. My main role was to update the website with new job opportunities using the Content Management System (T4 initally and Expression Engine). I assisted the team with other tasks including creating the monthly newsletter, sending out SMS messages, sending out surveys using Survey Monkey keeping track of various statistics and writing reports. I also created a table of contents application using HTML5, CSS3 and Javascript which allowed students to… Show more I was an intern at the W.I.T. Careers Centre. My main role was to update the website with new job opportunities using the Content Management System (T4 initally and Expression Engine). I assisted the team with other tasks including creating the monthly newsletter, sending out SMS messages, sending out surveys using Survey Monkey keeping track of various statistics and writing reports. I also created a table of contents application using HTML5, CSS3 and Javascript which allowed students to browse the contents of a USB memory stick Show less



Brandt Translations

• Software Tester

  • Sep 2009 - Jan 2010

  I carried out various roles at Brandt. These included setting up servers, documenting procedures for tools that were being used and testing software. Testing software became my main role. I wrote test documentation for the application and tested it by using every function in the application. When I found a bug I would log it in bugzilla so the developer could fix it. A bug report would contain a set of steps to reproduce the problem, a picture to help the developer find it and an importance… Show more I carried out various roles at Brandt. These included setting up servers, documenting procedures for tools that were being used and testing software. Testing software became my main role. I wrote test documentation for the application and tested it by using every function in the application. When I found a bug I would log it in bugzilla so the developer could fix it. A bug report would contain a set of steps to reproduce the problem, a picture to help the developer find it and an importance level. When a bug was reported to be fixed I would then try to reproduce the problem. If I could then I would let the developer know. Otherwise I would mark the bug as closed. I also communicated with the team abroad to ensure that the work that needed to be done was clear. Show less I carried out various roles at Brandt. These included setting up servers, documenting procedures for tools that were being used and testing software. Testing software became my main role. I wrote test documentation for the application and tested it by using every function in the application. When I found a bug I would log it in bugzilla so the developer could fix it. A bug report would contain a set of steps to reproduce the problem, a picture to help the developer find it and an importance… Show more I carried out various roles at Brandt. These included setting up servers, documenting procedures for tools that were being used and testing software. Testing software became my main role. I wrote test documentation for the application and tested it by using every function in the application. When I found a bug I would log it in bugzilla so the developer could fix it. A bug report would contain a set of steps to reproduce the problem, a picture to help the developer find it and an importance level. When a bug was reported to be fixed I would then try to reproduce the problem. If I could then I would let the developer know. Otherwise I would mark the bug as closed. I also communicated with the team abroad to ensure that the work that needed to be done was clear. Show less



AOL

• United States
• Software Development
• 700 & Above Employee

• Technical Support Agent

  • Jun 2003 - Aug 2003

  During my time at AOL I recieved calls from AOL UK cutomers who were experiencing difficulty with their broadband. I would take customers through a set of steps to try and rectify the problem. I also escalated the problem to British Telecom where necessary. During my time at AOL I recieved calls from AOL UK cutomers who were experiencing difficulty with their broadband. I would take customers through a set of steps to try and rectify the problem. I also escalated the problem to British Telecom where necessary.