QE Engagement Lead

**Job Openings** **1. QE Engagement Lead** *Location: Charlotte, NC (3 days onsite)* *Open for non-locals who can relocate* **Role Overview** Single point of accountability for a QE engagement validating the modernization of legacy applications onto.NET, Angular, and AWS, including migration from SQL Server to PostgreSQL. This is a hands-on lead role, not a coordination role. The person owns the client relationship, sets the technical direction, reviews what the offshore pod produces before it reaches the client, and is the one in the room when results are challenged. The client has an existing automation framework, governance model, and CI/CD pipeline already in place — this role must work inside them and improve them, not replace them. **Key Responsibilities** - Act as the single point of contact; own weekly reporting and the escalation path. - Report status against evidence — execution logs, failure artifacts, coverage traceability — rather than self-reported completion percentages. - Manage scope and estimate conversations, including re-confirming indicative timelines once the application estate has been inspected. - Review the client's existing automation framework, test organization, governance, and result-tracking model, and produce an agreed hybrid approach that combines it with existing practices. - Extend the client's existing Azure DevOps pipeline rather than standing up a parallel one. - Lead reverse engineering of application workflows, code, database objects, and configuration into a structured knowledge base where documentation is missing or outdated. - Establish coverage truth — assess the existing test estate against real business processes, identify duplicate, stale, orphaned, and non-executable cases, and quarantine flaky tests. - Build and maintain traceability, and drive a risk-ranked gap list to closure. - Own the pre-migration baseline — full execution on the legacy platform, with results, configuration, and data snapshots frozen. - Lead post-cutover parity validation — field-by-field comparison against the frozen baseline, deviation triage, and functional parity certification. - Own source-to-target data validation: record counts, schema and type mapping, transformation rules, referential integrity, null handling, stored procedure logic, and incremental loads. - Design and execute functional, integration, API, and end-to-end test scenarios across Angular front ends,.NET services, and downstream integrations. - Direct an offshore pod and review all output before it reaches the client. - Set automation standards and unblock the team technically — writing and debugging code where that is the fastest route. - Apply AI-assisted QE with human-in-the-loop discipline; AI-generated artifacts are validated before use, never shipped unreviewed. **Must Have** - 12+ years in Software Testing / Quality Engineering, including 3+ years leading a client-facing QE engagement onsite. - Demonstrable experience validating a platform or database migration — establishing baselines and proving parity between legacy and modernized systems. - Strong SQL, hands-on with both SQL Server and PostgreSQL, including practical knowledge of dialect differences (T-SQL vs PostgreSQL — TOP/LIMIT, GETDATE, ISNULL, casing, identity handling). - Hands-on ETL / source-to-target data reconciliation and the ability to write complex validation SQL independently. - Test automation depth in Playwright, Selenium, or Cypress, plus API automation (REST Assured, Karate, Postman, or equivalent). - Experience testing.NET /.NET Core back ends and Angular front ends, and testing REST APIs and integration flows. - Hands-on with CI/CD pipelines, specifically Azure DevOps, including integrating and troubleshooting automated suites in a pipeline. - Proven ability to adopt and work within a client's existing framework and governance model rather than imposing a new one. - Strong written communication — able to produce a status report a VP will read and act on, and to say plainly when something is not on track. - Willingness and eligibility to work onsite in the US. **Good to Have** - Experience testing applications hosted on AWS, and familiarity with RDS, Lambda, S3, ECS/EKS, API Gateway, and CloudWatch. - Exposure to AI-assisted development and testing tools — Kiro, GitHub Copilot, Claude Code, or similar — and to GenAI/agentic approaches applied to test generation, change-impact analysis, and defect triage. - Prior work in legacy application modernization programs. - Familiarity with Tosca or other legacy commercial test tools, particularly in a migration-off context. - Observability tooling — Datadog, Splunk, CloudWatch. - Working knowledge of performance, security, accessibility, and resilience testing. - Domain exposure to food service, procurement, supply chain, or retail. - Experience running a distributed onsite/offshore delivery model. --- **2. Lead Product Experience Strategist** *Location: Charlotte, NC (3 days onsite)* *Open for non-locals who can relocate* **Role Overview** We're looking for someone who thrives in ambiguity, enjoys understanding how work really happens, and can turn operational complexity into confident product decisions. Success is measured by the quality of decisions influenced before engineering begins—not by research reports or design deliverables. Establish and scale Product Discovery as a core capability. Working alongside Product, Engineering, and Operations, determine what evidence is, how to obtain it efficiently, and when the organization has enough confidence to invest. Influence product strategy, shape AI-enabled experiences, and help create a repeatable discovery operating model. **Key Responsibilities** - Regular travel to customer sites for operational discovery. - Cross-functional partnership with Product, Engineering, and Operations. - Daily use of AI to accelerate planning, synthesis, and communication. **What You'll Do** - Design evidence strategy: Translate ambiguous business questions into structured discovery plans, identify what is known