About Ankit Pandey
Software Test & Automation Engineer building automation that validates software from the interface to the data layer.
I am a Software Development Engineer in Test (SDET) focused on distributed systems, payment flows, and robust automation architectures. My approach treats quality engineering as an architectural discipline rather than a downstream verification chore.
Rather than relying solely on superficial browser clicking, I believe high-leverage testing happens at the boundaries: verifying HTTP status invariants across REST controllers, asserting database state rollbacks in PostgreSQL, testing distributed lock releases in Redis, and observing worker retry mechanisms in asynchronous queues like BullMQ.
The 6-Stage Testing Approach
Every testing architecture follows a structured pipeline where each step strictly informs the next.
Analyze the system architecture, data flows, and business rules before writing a single test.
Map the application layers — frontend, API, backend, database — and their interaction boundaries.
Determine where failures are most likely and most costly. Prioritize coverage accordingly.
Build reliable, maintainable automation that validates each layer independently and together.
Execute tests across the full stack — from UI interactions to database state verification.
Analyze results, refine coverage, and evolve the testing architecture as the system grows.
The Kinds of Problems I Like Testing
Distributed worker failure paths, idempotency key replays, Redis lock timeouts, and dead-letter queue behavior.
Pessimistic row-level locking (SELECT FOR UPDATE) preventing double debits, transaction rollback verification, and decimal precision checks.
Correlating Playwright network traces, database query logs, and container stdout to trace defects to their exact root cause.