Virendra Rajpurohit

I have 17 open full time roles for engineers (frontend or backend), eng managers, and product managers. 200k - 650k total comp. US/Canada 100% remote. Links to apply are in the top comment: 1. Group Product Manager: → Total Comp: 636 - 678k → Experience: 10+ yrs → Must Haves: You have managed other product managers for 2+ years. You have a fintech or crypto background and are interested in leading a flagship product with over 70M users. → Locations: US/Canada, 100% remote 2. Senior Product Manager: → Total Comp: 350 - 678k → Experience: 5 - 10 yrs → Must Haves: You have a crypto background, preferably consumer Web 3. Experience with defi, crypto wallets, building on chain for consumer. You are comfortable with a team moving very fast. 0 to 1 builder type role → Locations: US/Canada, 100% remote 3. Product Manager: → Total Comp: 215 - 240k → Experience: 3 - 6 yrs → Must Haves: You likely have a fintech background and are interested in working on a crypto staking product. A crypto background is optional. → Locations: US/Canada, 100% remote 4. Engineering Manager: → Total Comp: 486 - 524k → Experience: 5 - 10 yrs → Must Haves: You have experience with fintech or large scale payment systems where decisions affect millions of users. You are comfortable with Go. → Locations: US/Canada, 100% remote 5. Frontend Engineer: → Total Comp: 220 - 250k (US) → Experience: 2 - 5 yrs → Must Haves: Product minded engineers that are solid with React (TypeScript). React Native is a nice to have. Looking for two types of eng (1) some that move very fast and scrappy and (2) others that have operational maturity and ship really clean, well thought through products. → Locations: US/Canada, 100% remote 6. Senior Software Engineer: → Total Comp: 300 - 400k (US) → Experience: 5+ yrs → Must Haves: You are a degen. You live and breath crypto and want to build a brand new product onchain. You are a 0 to 1 engineer. You can move fast and have a high degree of ownership. You are comfortable with React (TypeScript) or React Native. Go is optional. → Locations: US/Canada, 100% remote 7. Backend Engineer: → Total Comp: 220 - 250k (US) → Experience: 2 - 5 yrs → Must Haves: Ideally have experience large scale payment systems where decisions affect millions of users. You are comfortable with Go. → Locations: US/Canada, 100% remote Find more details/apply through the links in the top comment. It includes a Loom video where I talk you through it! --- **REPOST to get tons of people jobs TODAY 🙏**

250

58 Comments

#Selenium Online Training #New #Batch Register : https://t.ly/kRNPk ☸ Course Contents :- Java, Selenium, TestNG, Maven, Git, Jenkins, BDD Cucumber, Selenium Grid, Page Object Model, HTML, JavaScript, AutoIT, Log4j, Assertion, Project Explanation, Manual Testing, Agile, JIRA, API Testing, etc. 🚩 Dedicated Framework Design Session from Scratch to Advance Level. ✳ Transposed 10000+ People into Automation across the World. ✳ Customized Notes on All Topics. ✳ Concept Retention With Funny Example. ✳ In Depth Interview Preparation, Resume Writing Assistance and Much More. ☑ First 4 sessions are free

95

13 Comments

🚀 Can You Pass This Automation Testing Mock Interview in Just 40 Minutes? | For Experienced SDET 🔍 Are you an experienced SDET or Automation Tester preparing for your next big interview? 🤔 🎥 I’ve just uploaded a Mock Interview that covers real, challenging questions you’ll face in today’s job market! Test your skills, sharpen your responses, and see if you can pass in just 40 minutes. ⏱️ 👉 Watch Now and get valuable insights to ace your next interview! 📌 Video includes: Advanced Automation Testing scenarios Key questions for SDET roles Tips and tricks for nailing the technical interview 🔗 https://lnkd.in/gP2_9MB7 #AutomationTesting #SDET #MockInterview #QAInterview #SoftwareTesting #AutomationEngineer #TechInterview #InterviewPreparation #JobInterviewTips #CareerGrowth

20

4 Comments

Strategies for Optimizing JMeter Test Plans for Large-Scale Performance Testing! 😎 Modularize Test Plans: Break down complex test plans into reusable components for better maintainability and scalability.   Use Distributed Testing: Leverage JMeter’s distributed testing to spread the load across multiple machines, reducing the strain on individual systems.   Limit the Use of Listeners: Minimize or disable listeners during the test run to save system resources; use CLI mode for better performance.   Efficient Data Handling: Use CSV Data Sets and efficient parameterization to manage large data sets without overloading memory.   Optimize Thread Groups: Carefully plan the number of users and ramp-up times to simulate realistic load without overwhelming the server or test machine.   Control Resource Utilization: Use timers, such as the Constant Throughput Timer, to control the pace of requests and prevent server crashes.   Use Assertions Sparingly: Apply assertions selectively to avoid excessive overhead during large-scale tests.   Pre-Test Infrastructure: Ensure that the testing environment (network, hardware, etc.) can handle the expected load before running large-scale tests.   Monitor System Resources: Keep an eye on CPU, memory, and network usage on both the server and client sides during the test.   Regularly Review and Clean Test Scripts: Continuously optimize and remove unnecessary elements to keep the test plan lean and efficient. #PerformanceTesting #JMeter #LoadTesting #SoftwareTesting #TestAutomation #QualityAssurance #Scalability #DevOps #TestingTools #ContinuousTesting #immediatejoiner #lookingfortestingjobs

8

2 Comments

Have you worked on Selenium & PlayWright? One of the crucial interview questions to showcase practical experience Selenium Exceptions vs Playwright Exceptions 🔥 ➡ Selenium Exceptions <> NoSuchElementException: Occurs when an element is not found using a locator strategy <> TimeoutException: Arises when a command does not complete its execution within the defined time <> StaleElementReferenceException: Happens when an element is no longer present in the DOM <> ElementNotInteractableException: Occurs when an element is present but not in a state that can receive input <> ElementNotVisibleException: Happens when an element is not visible on the screen but expected to be interacted with <> ElementClickInterceptedException: Occurs when an element is found but cannot be clicked due to another element obscuring it <> UnexpectedAlertPresentException: Arises when an unexpected alert pops up while executing a command <> InvalidSelectorException: Happens when the provided selector is invalid or incorrect <> SessionNotFoundException: Occurs when the WebDriver session is not found or has ended prematurely <> UnhandledAlertException: Happens when an alert is present, and the command used to handle it is not supported ➡ Playwright Exceptions <> TimeoutError: This occurs when an operation does not complete within the specified timeout <> SelectorError: Arises when a provided selector does not match any elements <> PageError: Represents errors related to actions or interactions with a page <> FrameError: Occurs when dealing with frames or iframes and an operation cannot be executed <> RequestFailedError: Represents failures in network requests or response handling <> RouteHandlerError: Represents errors when handling routes or intercepting network requests <> BrowserContextError: Arises when there are issues related to browser contexts, such as creating or manipulating them <> BindingCallError: Occurs when there are issues with function calls or bindings within the Playwright API <> WorkerError: Represents errors occurring within workers or threads in Playwright's execution environment Do follow for more - Japneet Sachdeva -x-x- Become Master of Test Automation Frameworks, Interviewers expect more then Page Object Model now!!! : https://lnkd.in/gyFKz5yF Become Proficient Automation Tester with CI/CD, Learn Industry standard Docker, GitHub Actions, Jenkins: https://lnkd.in/gWmK9Jud #japneetsachdeva

104

5 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle #QAInterview #QualityAssurance #TechInterview #InterviewQuestions #SoftwareQuality #BugFixing #SoftwareDevelopment #CriticalBugs

2

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

257

8 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Note: All services on TopMate are discounted till 31st May. Use it maximize your learning!! Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Full Stack QA with Test Architect preparation: https://lnkd.in/dWjpT3-3 Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

152

10 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package: https://lnkd.in/gusymgFi Become Master in Test Automation Frameworks & Designs: https://lnkd.in/gyFKz5yF My latest course on Udemy, for sale at Rs 399 only, Take a look here: https://lnkd.in/grvCi-ri #japneetsachdeva

144

2 Comments

What are different types of Testing every SDET should know? At what level these testing types are used? This is a common interview question, if your experience exceeds more then 5 yrs. Pre-Production Testing: Testing executed in lower env. such as Dev, QA, Staging etc. 1) Unit Test 2) Contract Test 3) Regression Test 4) Smoke Test 5) Sanity Test 6) Acceptance Test 7) Benchmark Test 8) Usability Test Post Deployment Tests: Testing executed after deployment into lower or mirror environments. 1) Integration Test 2) E2E Test 3) Load Test 4) Component Test Release Tests: Prod Blue Env. Tests before releasing to masses. 1) Traffic monitoring 2) Error logging review 3) Any other abnormal behaviour detection using tools like Kibana, Grafana, etc. Post Release: Release to Prod Green Env. Tests after releasing to masses. 1) A/B Tests 2) UAT 3) Traffic monitoring 4) Error logging review 5) Using tools like Kibana, Grafana etc. 6) Chaos Testing Final Conclusion: Depending upon the type of requirement and release management these types can be added or removed. Even some other testing types can be added. This is not a full fledged guide but it can serve as a part of realtime understanding and can be used as example in interviews. Different types of environments such as: 1) Dev Env. 2) QA Env. 3) Staging Env. 4) Non Prod Env. 5) CAT/UAT: Customer Acceptance Testing/User Acceptance Testing can be used but in the end the purpose is following: Dev Env. (Developer creates/enhances a feature) -> Released to -> QA Env./Staging Env./Non Prod Env. -> after rigorous Testing -> Release to -> Production Env. -x-x- API Test Automation E-Book for RestAssured & JAVA with Framework Creation from Scratch: https://lnkd.in/g8qgu-Qz Become Proficient Automation Tester with CI/CDCreate Industry Level Framework - using this course: https://lnkd.in/gWmK9Jud #japneetsachdeva

120

11 Comments

As a test automation enthusiast I recently faced a challenge – sharing data between scenarios in my existing Karate framework. Duplicating setup steps across features felt tedious and prone to errors. One of the common pain points in API automation is ensuring consistent data sharing across multiple scenarios within a feature file. Imagine a scenario where you need to authenticate a user, retrieve their profile information, and then perform various actions on that data. Traditionally, you'd have to repeat the authentication process in each scenario, leading to a cumbersome and error-prone workflow. 😓 Karate, a robust and versatile API automation framework, provides a elegant solution to this challenge. By leveraging the Background and CallOnce feature, you can seamlessly share data across your scenarios, streamlining your workflow and improving the overall efficiency of your testing process. 💪 The Background feature in Karate allows you to define a set of steps that will be executed before each scenario in your feature file. This is the perfect place to handle common tasks, such as authentication, that need to be performed across multiple scenarios. 🔑 The CallOnce feature, on the other hand, ensures that a specific set of steps is executed only once, regardless of the number of times it's called. This is particularly useful when you need to set up or retrieve data that should be shared across your scenarios. 📚 Let's dive into a practical example to illustrate how you can leverage Background and CallOnce to share user data across your scenarios. In this example, we first define the Background section, where we: 1. Set the base URL for our API calls. 2. Use the CallOnce feature to read user information from a JSON file and store it in the userInfo variable. 3. Print the user information to the console. 4. Set the Authorization header using the access token from the userInfo object. Now, in our two scenarios, we can directly use the userInfo object without having to repeatedly authenticate or retrieve the data. 🙌 In the "Retrieve User Profile" scenario, we make a GET request to the /users endpoint using the userId from the userInfo object, and then assert that the response matches the userInfo object. In the "Update User Profile" scenario, we make a PUT request to the /users endpoint, updating the user's name and email using the userInfo object, and then verify that the response contains the expected updates. By using Background and CallOnce, we've eliminated the need to repeat common setup steps, ensuring a more DRY (Don't Repeat Yourself) and maintainable automation suite. 🧹 #Karate #APITestAutomation #CodeReuse #Efficiency

38

6 Comments

[Imp SDET Interview Question] How Would You Design a Test Script to Validate a Login Page? Ans: My approach for effective, reliable test coverage: 1. Identify Basic Elements First, I will focus on elements like username, password fields, and login button. It's critical to ensure each element is uniquely identifiable, using stable locators (like IDs or CSS selectors) that won’t change frequently. 2. Valid Inputs Scenario Enter valid credentials and verify that the login is successful. I will check for the landing page, confirming it loads as expected. I will also add assertions for any welcome messages or redirects that are supposed to happen post-login. 3. Negative Test Cases Next, I will introduce scenarios where incorrect credentials are used: Blank fields: Verify that trying to log in with empty fields triggers the right error messages. Invalid Username/Password Combinations: Check for scenarios like invalid usernames, correct username with an incorrect password, and so on. 4. Boundary and Edge Cases Testing with inputs on the boundary is essential. I will include tests for: Max and min length: Ensure username and password fields enforce length limits. Special characters: Ensure inputs with special characters behave as expected. 5. Security Checks Security is always a top priority. I will add scenarios to ensure: SQL Injection Protection: Validate that the app does not accept SQL-like inputs. Brute Force Protection: Test for account lockouts after multiple failed attempts. Session Management: Ensure the user session remains secure and consistent. 6. Usability and Accessibility I will finish by validating usability and accessibility, checking that error messages are clear, fields have descriptive labels, and the UI handles edge cases gracefully. #Testing #SDET #QA #LoginPage #Automation #Python #Selenium

82

8 Comments

QA & QA Automation interview questions with answers Experience level - 4 years or more Q1) Describe a time when you missed a bug? Ans: No one can say they never make mistakes. So it’s a red flag if a candidate tries to insinuate their work is 100% error-free. So obviously providing an example in this situation is really useful. Now for me its related to a web application testing. Scenario - I was working in insurance domain and there are different tiles which appear with respect to a user account. So I missed to test a FSA tile. FSA is Flexible Spending Account which a user can use upto a limit granted by its insurance provider. Although there are different ways in the application to get know the remaining amount, but still missing this to test was an issue. But it didn't cause a major issue because it was medium priority Test Scenario. Q2) Do you think manual testing has any advantages? If so, what are they? Ans: Manual testing can be a better choice in some cases because :- <> The cost of manual testing can be lower than that of automated testing <> Manual testing allows you to see the product from the end user’s perspective <> Performing a manual GUI test is more intuitive, and results are more accurate automated GUI testing is tricky because of the accessibility of visuals and preferences <> A manual test can be easier to run for new teams or people new to quality assurance, meaning that it can be rolled out more quickly A lot more points can be added so as per your experience keep on adding. Q3) How do you ensure a bug in production is fixed? Ans: Validating the bug fix in dev or QA or Staging env, Once validated writing a test case and running a regression test immediately is the best course of action. This way, future software tests will be able to detect this specific bug. These can be done with the help of patch updates or hotfix or as a new release. Q4) How are a build and a release number different? Ans: A build number is assigned by the development team to a piece of installed software that goes to the testing team. The release number is assigned by the developer or tester to a piece of installed software before releasing it to the customer. Q5) What is defect triage? Ans: Bug triage is a process in which QA engineers: <> Make sure bug reports are complete <> Assign and analyze bugs <> Identify the proper bug owner and assign the bug to them <> Make necessary adjustments to bug severity <> Determine bug priority Do follow for more - Japneet Sachdeva Get more such scenario based and advance SDET interview questions with answers: https://lnkd.in/gSU-m2F7 #japneetsachdeva

232

12 Comments

💼 Understanding the Structure of a Technical Interview for SDETs Preparing for an SDET interview? Here's a simplified breakdown of what the process typically looks like: 1️⃣ Written Test: Most interviews kick off with a HackerRank or similar platform test. It includes a mix of: - Coding challenges to assess problem-solving skills. - MCQs on testing concepts to evaluate foundational knowledge. - Aptitude questions. 2️⃣ Technical Automation Round: This is where things get technical! Expect discussions on: - Coding problems and your approach to solving them. - Automation concepts, tools, and frameworks you’ve worked with. 3️⃣ Testing Round: The spotlight shifts to your manual and automation testing expertise, including: - Testing methodologies and processes followed in your previous projects. - Scenario-based questions like handling complex bugs or edge cases. 4️⃣ Managerial (HM) Round: This round dives into your teamwork and project management skills. Be prepared to discuss: - Real-world challenges and how you handled them. - Collaboration with cross-functional teams. 5️⃣ Director Round: Here’s where the focus broadens to: - Your mindset towards taking on challenges and navigating ambiguity. - Leadership skills, especially if you have substantial experience. 6️⃣ HR Round: A casual yet essential round to align expectations: Learn about the company’s culture and share your career aspirations. 7️⃣ Salary Negotiation: This is the final lap! Discuss compensation, benefits, and any other expectations before wrapping up. 🎯 Pro Tip: Every round is a chance to showcase your skills and enthusiasm. Tailor your responses to highlight your unique value proposition. Not always, but these steps are common across most SDET hiring processes. Final Thoughts An SDET interview is more than just a test of your technical skills—it's an opportunity to showcase how you think, collaborate, and contribute. Each round brings its own challenges and insights, so approach them with confidence and preparation. Have tips or experiences to share? Let’s discuss in the comments below! 👇

25

7 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle -x-x- 950+ Test Automation Interview Prep, Questions with answers and Coding questions exercises (paid): https://lnkd.in/gSU-m2F7 #japneetsachdeva

326

7 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle -x-x- 950+ Test Automation Interview Prep, Questions with answers and Coding questions exercises (paid): https://lnkd.in/gSU-m2F7 #japneetsachdeva

331

9 Comments