Looking to grow your career in Software Development Engineer in Test (SDET) roles? Blitz is hiring for two quality engineering positions at its Bangalore HQ: SDET-1 for professionals with 1–2 years of experience and SDET-2 for candidates with 3–5 years of experience. These opportunities are suited to QA automation professionals who enjoy coding, building reusable automation frameworks and testing web, mobile and API-based applications. The roles also involve regression testing, CI/CD pipelines, debugging and close collaboration with developers in a fast-paced environment.
🏢 About the Company – Blitz
Blitz enables same-day delivery for eCommerce brands, helping businesses improve delivery speed, reliability and cost efficiency. According to the supplied company description, Blitz works with enterprise brands across fashion, beauty and personal care, and healthcare. Fast delivery depends on more than moving a package quickly. Digital systems must coordinate orders, delivery operations, status updates and customer-facing experiences reliably. Software quality is therefore important to ensuring that orders are processed correctly and delivery workflows continue to work as expected. For SDETs, this environment can provide exposure to end-to-end workflows, API integrations, web and mobile automation, regression testing and scalable quality engineering practices. The company description also highlights improved conversion and retention outcomes for its brand partners; these figures are company-provided claims rather than independently verified results.
📌 Job Overview
- Company: Blitz
- Job Titles: SDET-1 and SDET-2
- Location: Bangalore HQ
- Employment Type: Full-time
- Work Mode: Bangalore HQ is specified; exact office attendance expectations are not stated
- SDET-1 Experience: 1–2 years
- SDET-2 Experience: 3–5 years
- Primary Languages: Java or Python
- Automation Tools: Selenium, Playwright or Appium
- API Testing: Postman and REST APIs
- CI/CD and Version Control: Jenkins and Git
- Additional Skills: SQL, database validation, performance testing, Allure/Extent reporting and cloud/test infrastructure
💼 Why Are These Roles Good for Experienced Professionals?
- SDET-1 (1–2 years): Ideal for early-career QA professionals looking to strengthen programming, UI automation, API testing and debugging skills while contributing to existing frameworks.
- SDET-2 (3–5 years): Suitable for professionals ready to take greater ownership of automation design, framework improvements, test reliability and CI/CD integration.
- Cross-platform testing: Work across web, mobile and API layers rather than focusing on only one testing area.
- Engineering collaboration: Partner with developers to reproduce issues, investigate failures and improve software quality throughout the development lifecycle.
- Startup exposure: Build adaptability, ownership and problem-solving skills in a fast-moving product environment.
🛠️ Skills Required for Blitz SDET Roles
- Programming: Java or Python, OOP concepts, collections, exception handling and writing clean, reusable code.
- UI Automation: Selenium or Playwright for browser testing; Appium knowledge for mobile automation.
- API Testing: REST methods, status codes, request/response validation, authentication and negative test scenarios using Postman or automation libraries.
- Framework Development: Reusable components, test data management, assertions, reporting, configuration and maintainable test suites.
- Testing Fundamentals: Functional, regression, integration, smoke and end-to-end testing, along with defect lifecycle and SDLC/STLC.
- CI/CD and Git: Version control, branching, pull requests and automated test execution through Jenkins or comparable pipelines.
- Database and Reporting: SQL validation, database checks and reporting tools such as Allure or Extent Reports.
🎯 Preparation Tips
1. Practise a complete order workflow. Design tests for order creation, payment confirmation, dispatch, delivery-status updates and cancellation. Consider duplicate requests, delayed updates and failed API calls. These are practice scenarios based on the logistics context, not confirmed interview questions. 2. Prepare a framework walkthrough. Explain your framework structure, test runner, reusable methods, configuration, test data, logging and reporting. For SDET-2, prepare examples of improvements you personally implemented. 3. Connect UI, API and database testing. Explain how you would create an order through an API, verify it in the UI and validate the stored data with SQL. 4. Practise debugging automation failures. Understand flaky tests, timeouts, locator failures, environment issues, logs and screenshots.
🧑💻 Expected Interview Rounds
- Round 1 – Recruiter Screening: Experience, role preference, location and availability.
- Round 2 – Coding and Testing Fundamentals: Java/Python, OOP, test design and problem-solving.
- Round 3 – Automation and API Testing: Selenium/Playwright/Appium, REST APIs and framework concepts.
- Round 4 – Practical or Framework Discussion: Debugging, test scenarios, SQL and CI/CD. SDET-2 candidates may face deeper framework-design questions.
- Round 5 – Hiring Manager Discussion: Project ownership, collaboration, quality strategy and working in a startup environment. These are possible preparation areas, not verified Blitz-specific rounds.
💰 Expected Salary Range
- SDET-1 (1–2 years): Approximately ₹6–12 LPA
- SDET-2 (3–5 years): Approximately ₹12–22 LPA These are indicative estimates, not confirmed Blitz salary bands. Actual offers depend on coding ability, automation expertise, interview performance and compensation structure.
📄 Resume Tips for Blitz
- For SDET-1: Highlight coding fundamentals, automated test scripts, API testing and contributions to regression suites.
- For SDET-2: Emphasise framework improvements, CI/CD integration, debugging ownership and measurable quality outcomes.
- Show your technical stack clearly: Separate programming languages, UI automation, API testing, databases and DevOps tools.
- Quantify genuine achievements: Mention test coverage, execution time saved or flaky-test reduction where you have evidence.
- Include end-to-end examples: Demonstrate how your testing validated complete workflows rather than isolated screens.
