{"id":1597673,"url":"https://alion.io/job/svitla-systems-qa-automation-engineer","title":"QA Automation Engineer","company":{"id":2216,"name":"Svitla Systems","domain":"svitla.com","url":"https://alion.io/company/svitla-systems","size_band":null,"is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Career site","truth_index":{"grade":"A","score":93,"open_postings":7,"ghost_share":0,"stale_share":0.286,"repost_share":0,"time_to_fill_p50_days":55,"computed_at":"2026-10-05T05:45:15Z"}},"role":"QA","role_family":"QA","seniority":"middle","employment_type":null,"work_mode":"remote","remote_scope":"stated_countries","remote_scope_basis":"inferred_payroll_markers","remote_working_hours":null,"hiring_geo_confidence":"inferred","locations":[],"countries":[],"hiring_countries":["AR"],"hiring_countries_total":1,"salary":null,"salary_estimate":null,"experience_years_min":4,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":".NET","optional":false},{"name":"C#","optional":false},{"name":"CI/CD","optional":false},{"name":"JavaScript","optional":false},{"name":"Pact","optional":false},{"name":"Playwright","optional":false},{"name":"Rest API","optional":false},{"name":"TypeScript","optional":false},{"name":"AI Agents","optional":true},{"name":"AWS","optional":true},{"name":"Claude","optional":true},{"name":"Claude Code","optional":true},{"name":"Docker","optional":true},{"name":"Gatling","optional":true},{"name":"GitHub Actions","optional":true},{"name":"JMeter","optional":true},{"name":"k6","optional":true},{"name":"Self-Healing","optional":true},{"name":"SQL","optional":true},{"name":"Stripe","optional":true},{"name":"TeamCity","optional":true}],"status":"live","first_seen_at":"2026-07-17T10:17:01Z","employer_posted_date":"2026-07-17","last_verified_at":"2026-10-06T01:42:20Z","board_verified":true,"closed_at":null,"days_open":80,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":80},"description":"We’re hiring a QA Automation Engineer to drive quality across our product suite, with our payment and billing flows as the highest-stakes surface. This isn’t a pure automation role. We want a well-rounded quality engineer, grounded in QA fundamentals and comfortable designing a test plan or exploring a feature by hand when that’s the right tool, who uses automation and AI as force multipliers, not a substitute for judgment.\nYou’ll design and build automation frameworks, wire quality gates into CI/CD, and use AI tools to generate, maintain, and heal tests, so your time goes where human judgment matters most. Where a payment flow can fail in production, you’ll have caught it first.\nYou’ll be embedded in a product pod, working alongside full-stack engineers, with a dotted line into the broader quality engineering community across our five pods.\nRequirements\n 4+ years as a QA engineer, SDET, or automation engineer. You write production-grade automation code, not record-and-playback scripts, and you got there on a foundation of real testing skill.\n Solid QA fundamentals. Test design techniques (boundary analysis, equivalence partitioning, state transitions), test planning, and defect lifecycle management.\nStrong TypeScript/JavaScript. C# is a strong plus given our .NET back-end.\nDeep, hands-on Playwright experience. Selectors strategy, network interception, parallelization, CI integration, and flake management.\nSolid API testing experience. REST, auth flows, webhooks, error contract correctness (a 500 where a 400 belongs is a bug you catch), and contract testing (Pact or similar is a plus).\nComfort testing third-party embedded UI. Stripe components, iframes, postMessage flows, and the cross-frame defects they produce.\nWorking SQL skills. You can verify data state in SQL Server, not just assert on the UI.\nCI/CD fluency. You’ve built or owned pipelines, not just consumed them.\nAI-driven testing\nYou already use AI coding assistants daily for test work and can demonstrate it live.\nGenuine curiosity about agentic and AI-native testing. You’ve experimented with these approaches, or you’re visibly eager to.\nJudgment about where AI output needs human review. Especially where money moves.\nDomain and quality mindset\n Experience testing payment, billing, fintech, or other correctness-critical systems is strongly preferred.\nYou understand idempotency, race conditions, and async workflows well enough to design tests that catch their failure modes.\n Risk-based thinking. You know what to automate, what to explore manually, and what to skip.\n Strong communication. Your bug reports, test plans, and failure analyses are clear enough that engineers act on them without a meeting.\nNice to have\n Performance and load testing (k6, Gatling, JMeter).\nVisual regression tooling and accessibility testing (axe, WCAG).\n Docker, AWS, and testing against containerized environments.\nPrior work in a pod or squad model embedded with developers.\nResponsibilities\n Design, build, and own test automation frameworks for web UI (Playwright preferred) and APIs (REST, contract tests at service boundaries).\nBuild integration and e2e coverage for payment-critical flows. Hosted and iframe-embedded payment pages, merchant onboarding, webhooks, recurring billing, refunds, and reconciliation. These tests are the safety net for money movement.\nCover multiple payment rails and regions. Cards with 3DS, ACH and eCheck in the US, PAD / ACSS debit in Canada, and surcharging rules that differ by card type.\nOwn test data management. Seeding, isolation, teardown, and realistic finance scenarios (partial refunds, declined cards, ACH returns, disputed charges, trust vs operating account routing).\nTest feature-flag and entitlement matrices. The same flow can behave differently by region, brand, processor routing, and package tier, and your coverage has to prove all of them.\nWire quality gates into CI/CD (TeamCity, GitHub Actions). Fast, reliable, deterministic suites that engineers trust and don’t bypass. Track and drive down flake; a flaky suite is a broken suite.\nMake AI the multiplier\nUse Claude, Claude Code, and similar tools daily to generate test cases, scaffold suites, refactor brittle tests, and analyze failures.\nBuild AI-assisted workflows for test generation from acceptance criteria. A well-written ticket should produce a draft test suite, not a blank file.\nEvaluate and adopt AI-native testing approaches. Self-healing locators, agentic exploratory testing, AI-driven failure triage, and visual regression analysis.\nMeasure the gains. Coverage growth, authoring speed, escape rate, and time-to-triage, and report them.\nShare what works with QA and QE engineers across all pods. You raise the AI-fluency bar for the whole quality org.\nEngineer quality into the SDLC\nShift quality left. Review acceptance criteria for testability before development startas and flag ambiguity and missing edge cases early.\nDefine test strategy with the pod. What gets unit, integration, contract, e2e, and what risk-based exploratory testing on top.\nRun hands-on exploratory testing on new features and high-risk changes. Automation proves what you expected; exploration finds what you didn’t.\nTest manually where it’s the right tool. New UI before automation exists, complex edge cases, and usability checks.\nOwn the regression, E2E, and UAT cycles that gate payment releases. GA doesn’t ship until your suites say it can, and rollback plans are tested, not theoretical.\nBuild observability into the test layer. When a suite fails, the failure should explain itself.\nContribute performance and load baselines for payment endpoints and watch for regressions.","description_format":"text","description_chars":5665,"description_truncated":false,"requirements":{"experience_years_min":4,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[{"name":"Argentina","iso":"AR","kind":"country"}],"hiring_excludes":[],"relocation_offered":false,"industries":["DevOps & Platform Engineering","IT Outsourcing & Dedicated Teams","Custom Software Development"],"lifecycle":[{"event":"open","at":"2026-10-01T18:15:47Z"}],"visa":[{"country":"US","licensed_sponsor":true,"evidence":"Filed H-1B visas in the last two years","filings_12m":0,"filings_prev_12m":1,"green_card_filings_12m":0,"median_offered_wage_usd":null,"route":null,"cap_exempt":false,"checked_at":"2026-10-03T21:08:04+00:00","sources":["US Department of Labor: LCA disclosure data (H-1B, H-1B1, E-3)"],"filings_for_role_12m":0}],"liveness":{"score":30,"band":"fade","label":"Fading","p_open":1,"p_active":0.686,"p_room":0.44,"age_days":79,"expected_fill_days":55,"reasons":["conf:1","velocity","win:tail","crowd:brand"],"computed_at":"2026-10-05T05:45:15Z"},"pay":null,"html_url":"https://alion.io/job/svitla-systems-qa-automation-engineer","json_url":"https://alion.io/job/svitla-systems-qa-automation-engineer.json","meta":{"generated_at":"2026-10-06T03:01:47Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":4548,"day_limit":5000,"remaining_today":452,"minute_limit":60,"resets_at":"2026-10-07T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":2216},"rest":"https://alion.io/mcp/rest/get_company?id=2216"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Fsvitla-systems-qa-automation-engineer"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Fsvitla-systems-qa-automation-engineer"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Fsvitla-systems-qa-automation-engineer"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/svitla-systems-qa-automation-engineer\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Fsvitla-systems-qa-automation-engineer"}]}