Note: The job is a remote job and is open to candidates in USA. de Anda Capital is hiring a QA Engineer for an unnamed portfolio company in the fintech space. The role owns automated quality coverage for a multi-tenant time-and-attendance platform, extending tests across the hours workflow from punch through delivered export. The engineer will build and maintain automated tests, verify tenant isolation and payroll-related calculations, and keep CI and release verification reliable.
Responsibilities
- Convert PRD acceptance criteria into executable test cases before the feature merges; pair with the engineer on the same Technical Document
- Write pytest against services and the GraphQL schema: frozen time at period boundaries, tenant-mismatch cases, concurrency (two workers, one queue item), Celery tasks run synchronously
- Write Jest / Testing Library for role-gated UI: who sees which card, which button is locked, what happens on GraphQL error
- Build and own the Playwright project in-repo: login per role, punch in/out, missing-OUT exception, approvals, schedule publish, time-off, period-close readiness, support-portal 2FA, kiosk PIN. Wire it into the deploy workflow
- Design data-driven calculation tests: OT thresholds, meal violations, split shifts, DST days, retro edits after calculation, late punches after close
- Verify exports: CSV and PDF totals equal timecard totals; scheduled delivery arrives with the right attachment and audit row
- Run tenant-isolation and RBAC matrices every release; anything that crosses a tenant is P0
- Review agent-generated tests for false confidence: tests that pass without asserting the acceptance criterion do not count
- Keep CI healthy: flaky xdist tests, coverage thresholds, slow Jest suites
- Report defects precisely: tenant, role, pay period, timezone, exact GraphQL operation and variables, expected vs actual hours
- Hours-engine regression pack — scenario index covering pairing, exceptions, OT, meals, geofence flags, waivers, stale calculation after new input
- Playwright E2E suite committed in the monorepo, wired into deploy, with per-role fixtures
- RBAC and tenant-isolation matrix as automated tests, including support-portal boundaries
- Period-close and delivery verification — blocking vs warning exceptions, delivered totals vs timecards
- Locked-vs-live admin audit — guard that admin screens not yet backed by GraphQL stay locked until it lands
- CI health — stabilize xdist and add coverage thresholds that fail builds
- Performance baselines — schedule grid, dashboard aggregation, large-tenant timecard lists
Skills
- 3–5 years in software quality with code-level automation as the primary output, on both the Python and TypeScript sides
- Python test authoring (pytest, fixtures, factories, mocking) and TypeScript/React component testing (Jest, Testing Library)
- Has built a browser E2E suite from scratch (Playwright preferred; Cypress acceptable) and kept it non-flaky in CI
- Reads GraphQL operations and responses; can isolate a frontend bug from an API bug from a data bug
- SQL against PostgreSQL to verify what the UI claims
- Test design for stateful systems: roles, periods, timezones, retries, eventual consistency
- Git, PR review, Docker Compose, GitHub Actions
- Precise written bug reports and test plans
- Time and attendance, payroll, or scheduling domain
- Testing Celery or other queue-based systems; concurrency and idempotency cases
- Multi-tenant SaaS isolation testing; auth flows (JWT, TOTP, OTP, rate limits)
- Contract/schema testing for GraphQL; Apollo cache behavior
- Accessibility (axe), visual regression via Storybook
- Load testing (k6 / Locust); reading CloudWatch and Sentry
- Experience using coding agents to generate tests, and judging when their output is wrong
Company Overview