Pros: speaking with co-works and getting their fee- back
Cons: that it was a contract
My typical day
• Created and executed automated software test plans, cases and scripts to uncover, identify and document software problems and their causes.
• Contributed to the QA process improvement and documentation for support in Department Audits.
• Take an active role in backlog grooming to ensure all requirements given are testable and well understood.
• Lead QA status meetings at the daily scrum.
• Ad Hoc Status Reporting on QA status
• Support the project team in all aspects of the project life cycle
• Tested all Web Services between the .net in house application to external systems such as External Bank’s, Appian workflow, Navision accounting services as well as the online claims processing applications
• Applications tested in .Net, ASP.Net, Appian, HTML%, Crystal Reports with the back end of SQL and MySQL. Run simple SQL scripts to validate data within the application directly from the database.
• Pinpointed previously undiscovered flaw in new software release, resulting in formal commendation letter from the department head
• Identified the root cause of intermittent interoperability glitch in the software, leading to a better release
• Conducted formal and informal product design reviews throughout the software development lifecycle to provide input on functional requirements, product designs, schedules and potential issues. Leveraged my communication to communicate effectively with software design team, quickly gaining their respect and becoming a valued, “go-to” team member on challenging test cases
I learn everything that you see above.
Management was great, – more... they were flexible in hours
co-works were amazing, cause we worked as team and not as individuals
The hardest part of the jobs is that there was not enough hours in a day.
The most enjoyable part of the jobs is seeing the end result of a successful project. – less