QA Full Stack Engineer

< class="jkflp5" data-pm-slice="1 1 []">Job Title : QA Full Stack Engineer
Location: Berwyn, PA (4 days onsite per week)
Duration: 6-month contract to hire.
Interview: 2 virtual rounds.

This discussion provided critical clarification on the QA Full Stack Engineer roles supporting the Archer organization within client. Diana outlined that these are no longer traditional QA positions. Client is actively transforming QA into a more technical, full stack engineering function that combines testing, automation, application knowledge, code analysis, Agile participation, AI utilization, and strong business domain expertise.
Key Requirements

Technical Skills
* Strong understanding of QA methodologies and automated testing.
* Working knowledge of:
o Java
o SQL
o JavaScript
o Angular
o HTML/CSS
o Tomcat
* Ability to read, analyze, and troubleshoot code, though not necessarily operate as a full-time software developer.
* Experience creating and maintaining automated test scripts.
* Understanding of database concepts, joins, keys, and query development.

QA Evolution
* Historically, QA resources focused only on testing and automation.
* Client now expects QA engineers to function as Full Stack Engineers in Test (SDET-style profiles).
* Candidates should be comfortable navigating code, investigating defects, and collaborating closely with development teams.
Manager repeatedly emphasized the importance of financial services experience.< class="jkflp5" data-pm-slice="1 1 []">Preferred exposure includes:
* Settlement processing
* T+1 settlement concepts
* Custody and asset servicing
* FIX messaging
* Capital markets and transaction processing terminology

Candidates without financial services experience may struggle to understand the application and business workflows.
Agile & Communication Expectation
A major differentiator is communication ability.

Candidates must:
* Actively participate in Agile ceremonies.
* Review and challenge poorly written acceptance criteria.
* Speak up during refinement and planning sessions.
* Push back when requirements are unclear.
* Demonstrate confidence and influence within a pod structure.
Diana specifically stated she cannot have "quiet QA engineers" and needs individuals who will advocate for quality and challenge assumptions.

AI adoption is becoming a significant expectation.

Candidates should:
* Be comfortable using tools such as Copilot and AI-assisted coding platforms.
* Leverage AI to:
o Analyze code
o Troubleshoot defects
o Understand applications
o Summarize technical findings
o Improve productivity