The document outlines the duties and responsibilities of a Quality Assurance Engineer at The Nerdery, which include executing various types of testing such as browser compatibility testing, localization testing, and regression testing. Additional responsibilities for an integrated QAE lead include managing a QA team, writing test plans and cases, estimating QA hours, and participating in client meetings. The role also involves maintaining environments and devices for testing across desktop and mobile platforms.

1. My duties, responsibilities and tasks as a Quality Assurance Engineer at The Nerdery:
General Tasks:
 Test plan execution using various desktop browsers, mobile devices, tablet devices and 3rd party
hardware
 Static design and copy comparison testing
 Corner testing
 Audit testing
 Hardware integration testing
 End to End testing
 Localization testing
 Maintenance testing
 Regression testing
 Admin feature testing
 CMS testing - WordPress, Drupal, SharePoint, Sitecore, Sitefinity, Umbraco
 Internal project team meetings
 Writing detailed defect or enhancement tickets using issue tracking software (Jira, Trac).
Providing the summary of the issue/enhancement, expected results, location of
issue/enhancement, environments the issue occurs in, steps to reproduce and providing
annotated screenshots and/or videos
 Creating timesheet entries in Mainframe for time billed to clients and admin time used for work
performed each day
 Updating a capacity report spreadsheet daily for resourcing. With current project work and hours
needed for the week if looking for billable client work
Integrated QAE Lead Duties and Responsibilities:
 Managing/leading a QA team on large project engagements – Communicating project updates
and changes requested from the client and assigning tasks/direction to each QA team member
 Test plan writing - Creating test cases in which all requirements based on the scope of work,
wireframes and designs are met
 QC testing – Testing while writing the TPS (Testing Procedural Spreadsheet), calling out any
blocker issues that could prevent test cases to be performed before the project is ready to begin
the first sweep. As well as calling out any missing requirements or features that have not yet been
implemented into the staging environment
 QA process planning - Integrating agile or waterfall methodologies based on project size and
timeline
 Sprint planning - Working together with the lead developer and SPM to plan which features and
requirements to test together or separate for each sprint and create a sprint timeline breakdown
 Requirement analysis - Reviewing scope of work and ensuring all requirements described are
tested and written properly into the test plan. As well as calling out any potential risks or concerns
from a QA perspective during QAE lead kickoff meetings
 Creating project status reports for internal team and for the client
 Estimating QA hours needed to complete a project before testing begins
 Client facing meetings - Discussing project status, describing current issues/defects and provide
possible enhancements for the project
 Bottlecap presentations for projects from the QA standpoint
 Provide training, leadership and guidance to new QAE employees. As well as create training
documentation used during their first week.


2. Environment/Browser and Device Management (Role I created 2 years ago to benefit the QA
department and company as a whole):
 Provide environment recommendations for various projects based on technology used, project
type, current market share value, client analytics and the client’s budget
 Send out a weekly email to the QA, SE, SPM and Sales departments containing information
regarding browser updates, iOS/Android OS version updates, upcoming Apple or Google events
(overview of event will take place in the following email after event occurs), new devices
purchased and available for scoping to projects, current stable versions of desktop browsers and
current stable versions of iOS/Android OS versions. As well as current market share/usage data
for desktop browsers, mobile/tablet browsers, desktop OS versions, mobile/tablet OS versions,
Apple App store distribution numbers by version and Android Google Play store distribution
numbers.
 Meet with the technology managers each quarter to discuss upcoming device purchases to add
to the device library and upcoming new major desktop OS/Apple OS/Android OS version updates
that could effect upcoming projects
 Review and analyze client analytics – Create a breakdown spreadsheet with current usage
numbers for all desktop OS versions, browsers and their versions and mobile devices/models and
their versions. As well as how each desktop OS, browsers and mobile devices/models/versions
are trending. Then provide a recommended supported environments list for the project based on
the numbers, trends and client’s budget
 Review the supported environments listing in SOW documentation during QA intake. In which I
will approve the supported listing or recommend updates/changes to be made and meet with the
project team and client to discuss
 Manually maintain devices and update device OS versions in the library as needed based on
market share value and project needs. As well as use debug tools as needed if there’s an
issue/problem with a device
 Present at SPM bi-weekly meetings when a major OS version update occurs to ensure everyone
is aware of the new features/changes to the OS that could effect current or upcoming projects
and communicate the information I present to clients so they are aware
Staff Augmentation:
 On site at client office for an extended period of time, until project completion
 Provide consulting advice on NQA process and how it can be implemented or adapted to the
client’s current QA process (if client currently has a QA process)
 Lead the overall requirements testing effort and User Acceptance Testing effort
