Vetted Windows Professionals

“QA automation engineer in a banking domain who owned an end-to-end automation suite for critical money movement flows (onboarding, funding, transfers). Demonstrated impact through edge-case coverage (min balance, boundary amounts, repeated actions, timeouts), CI/CD gating with smoke vs regression suites, and catching a high-impact timing defect where UI success masked incorrect balance updates.”

“QA automation engineer who owned an end-to-end, device-integrated mobile regression suite for Tandem’s insulin-pump-connected mobile app, covering pairing/connectivity/data sync and catching contract mismatches and firmware-related connectivity regressions. Strong in Cypress/JavaScript automation, CI gating in GitHub Actions, and diagnosing production-impacting sync issues using logs and API traces while influencing requirements early to improve testability and UX.”

“Gameplay-focused Unity developer who prioritizes tight, fair-feeling controls—implemented a custom raycast-based character movement system (avoiding Unity physics) to make platforming more deterministic and difficulty tuning more reliable. Has prototyped multiplayer in both Unity (Photon tic-tac-toe replication prototype) and Unreal Engine (shared workshop/crafting environment), and actively uses AI tools (Copilot + asset generation) to speed prototyping and documentation.”

“Frontend engineer with fintech experience who has owned React Native/React + TypeScript architecture end-to-end, including feature-based modularization, reusable component libraries, offline support, and API optimization. Built a heavy analytics dashboard with real-time WebSocket updates and has shipped security-sensitive third-party payment integrations, including rapid post-release fixes via over-the-air updates.”

“UNIX operations-focused candidate with hands-on AIX/Solaris troubleshooting and Bash automation experience, including resolving a production connectivity outage caused by a host table IP misconfiguration. Has supported a re-platform migration of a home-grown application by working directly with developers and running parallel testing prior to cutover; no direct IBM Power (VIOS/HMC/LPAR) or NIM/PowerHA experience.”