Quality Assurance & Technical Documentation Analyst

IEM•,

2d•$36 - $38•Remote

About The Position

IEM is looking for a Full Time - Quality Assurance & Technical Documentation Analyst to serve as the quality assurance resource for an agile application development team delivering business applications for a federal client. As the team’s primary QA resource, this role develops and executes the test plans for each release, analyzes requirements and acceptance criteria to build test conditions, tracks defects to resolution, recommends release readiness, and produces the end-user documentation and training for the program. The ideal candidate combines hands-on software testing with clear, user-facing writing and communicates effectively with both technical and non-technical stakeholders. This position may require occasional travel to client’s office at DC to complete work assignments or attend meetings.

Requirements

Bachelor’s degree in Information Systems, Computer Science, Communications, Business, or a related field.
4+ years of experience in software quality assurance, user acceptance testing, or technical writing for software applications.
Demonstrated experience analyzing requirements and acceptance criteria, designing test plans and test cases, and executing functional and regression testing.
Demonstrated experience producing user-facing documentation such as user guides, release notes, or training materials.
Experience working with a defect-tracking or work-management tool (e.g., Jira, Azure DevOps, or equivalent).
Excellent written communication skills, with the ability to explain technical functionality to non-technical audiences.
U.S. citizenship and the ability to obtain and maintain a federal Public Trust suitability determination.
Meticulous attention to detail and a methodical approach to testing.
Clear, concise writing with strong editing skills.
Ability to see the application from the end user’s perspective.
Strong organizational skills and ability to manage multiple releases and deliverables.
Collaborative and proactive in a remote, distributed team environment.

Nice To Haves

Experience testing applications built on low-code/no-code platforms (e.g., Microsoft Power Platform, Appian, ServiceNow, Salesforce).
Familiarity with agile/scrum delivery and sprint-based release cycles.
Experience supporting federal or public sector clients, including familiarity with Section 508 accessibility testing.
Experience with SharePoint or similar collaboration platforms for publishing documentation.
QA or technical writing certifications (e.g., ISTQB, CPTC).

Responsibilities

Develop the test approach and test plans for each application release, consistent with client quality and release standards.
Analyze user stories, requirements, and acceptance criteria in consultation with business analysts, developers, and end users to develop test conditions and validate that delivered functionality meets the specifications.
Execute functional, integration, and regression testing for each release; plan, coordinate, and facilitate user acceptance testing (UAT) with end users, including test scripts, test accounts, and consolidation of results.
Log, classify, and track defects by severity and business impact; perform root-cause analysis with developers to determine whether issues originate in requirements, design, configuration, or data, and refine test conditions accordingly.
Report test results and outstanding defects to the technical lead and client prior to each release, with a recommendation on release readiness.
Author end-user documentation for the program, including user guides, quick-reference materials, and system documentation, consistent with client documentation standards.
Author release notes and technical notifications describing new features, fixes, and known issues in plain language for the client user community.
Develop and deliver end-user training for new and updated functionality, including materials and live sessions.
Participate in application design and development activities and agile ceremonies, providing input on testability, accessibility, and usability as features are designed and built.