SDET (Software Development Engineer in Test) | AstraLink Connect

SDET (Software Development Engineer in Test) | AstraLink Connect
📍 Bengaluru | 4 to 6 years | Full-time | On-site / Hybrid
Do you find the bug everyone else missed?
AstraLink Connect is a network security platform. It brings together networking appliances, cloud services, web, desktop and mobile apps, VPN connectivity, firewall management, IDS/IPS, VLANs, access control and device management.
You'll be our first dedicated SDET. This isn't a role where you get a list of test cases, run them and report what passed. You'll learn how a feature works, work out where it can break, design the test strategy, automate it, and dig into every failure.
How we think about testing
Say we ship a feature that pushes a configuration change from our cloud to a customer's router. Checking that the config reaches the router is only the start. We'd expect you to ask:
What if the router goes offline halfway through?
What if the request reaches the backend twice?
What if the dashboard accepts the config but the appliance rejects it?
What if the user loses permission while the operation is running?
What if the cloud thinks it applied, but the router disagrees?
Can the system recover without leaving the customer in a broken state?
Then you'd decide which of those should become automated tests. That's the mindset we're hiring for.
What you'll do
Own test strategy and quality for features, from development to production release
Build automated end-to-end, integration, API and regression tests in TypeScript with Playwright
Test workflows across our apps, backend APIs, cloud infrastructure and networking appliances
Cover happy paths, negative cases, boundaries, permissions, concurrency and failure conditions
Validate networking behavior: VPNs, firewalls, VLANs, routing, DNS, DHCP and access policies
Test real-world failures: flaky connectivity, appliance restarts, API errors, partial operations
Add tests to CI/CD and set up release quality gates the team relies on
Investigate failures using app logs, browser traces, API responses and device logs
Write bug reports precise enough that engineers can find the real problem fast
What we're looking for
4 to 6 years in SDET, QA automation, or software engineering with real testing ownership
Strong TypeScript / JavaScript (Python is a plus)
Experience building and maintaining production-grade test suites with Playwright, Cypress or similar
You test APIs in code, not only in Postman
A solid grasp of REST, HTTP/HTTPS and client-server architecture
Comfortable reading an unfamiliar codebase (we use Go and TypeScript) and debugging with developers
Experience with Git and CI/CD
Good understanding of test isolation, test data, mocking and negative testing
Networking knowledge matters
Connect isn't another CRUD SaaS. You don't need to be a network engineer, but you should be comfortable with TCP/IP, DNS, DHCP, routing, NAT, ports, firewalls, VPNs and VLANs. You should be able to open a terminal, read logs, make API calls, and figure out why two systems aren't talking.
Bonus if you have worked with:
Linux and shell tooling
WireGuard or other VPN technologies
Network/security products
Docker and containerised environments
AWS
MQTT or event-driven systems
Mobile application testing
Performance/load testing
Security testing
Hardware or networking appliances
Observability and distributed-system debugging
How you work
Methodical: you reproduce a problem before you report it
Clear: you can push back on a release, with evidence
You take ownership without waiting to be told what to test
What success looks like
Within your first few months, we'd expect you to:
Understand the critical user journeys and failure points across Connect.
Establish reliable automated coverage for our highest-risk workflows.
Reduce repetitive manual regression testing.
Catch regressions before they reach production.
Make failures easier for engineers to reproduce and diagnose.
Help establish clear release criteria and quality gates.
Build a test suite the engineering team actually trusts.
Over time the goal is simple: when the pipeline is green, the team is confident to ship.
Why join
You'll shape how quality works here from day one, as our first SDET
A bug here isn't just a broken button. It can be a firewall rule that didn't propagate or a VPN that fails under one network condition. Your work prevents that.
A small team, with the freedom to improve our test architecture and tooling as we grow

Work arrangement
No