Rajesh kannan’s Post

Real Talk About SDET Hiring - From Someone Who's Been on Both Sides I had to smile this morning while reviewing some SDET job descriptions that landed in my inbox. They reminded me of my mother's shopping lists - you know, the ones where she writes down everything in the store just in case she needs it. Look, I get it. I've been heading automation teams for years now, and yes, we all want rockstar engineers. But here's what I'm seeing everywhere: "Required Skills:" - Must know every automation framework created since the dawn of testing - Should code fluently in roughly 4-5 programming languages - Must have mastered all CI/CD tools (including the ones still in beta) - Need expert-level knowledge in... well, everything Here's the thing - I've hired and worked with some brilliant SDETs over the years. Want to know what made them exceptional? It wasn't their encyclopedic knowledge of every tool in existence. The real MVPs in my teams have always been engineers who: - Really understand how to design robust test architecture - Have solid coding skills in one or two languages (and can learn others when needed) - Know how to pick the right tool for the job (not just the trending one) - Can explain complex testing concepts to non-technical folks - Actually think about maintainability (bless their souls) Let's be real for a minute. If you're posting job requirements that look like a copy-paste of the entire testing section of Stack Overflow, you might be doing it wrong. What if instead, we tried something radical - like being honest about what the job actually needs? Here's my approach: 1. List the core tech stack they'll use daily (the real one, not the aspirational one) 2. Focus on problem-solving abilities (because that weird edge case won't test itself) 3. Look for architectural thinking (because someone needs to think about the big picture) 4. Value learning aptitude (because today's hot framework is tomorrow's legacy code) After all, I've never met an engineer who simultaneously used Cypress, Playwright, Selenium, and Appium all in one day. And if you have, please check if they're okay. Fellow engineering leaders - what's your take on this? How do you cut through the noise when writing job descriptions? #SoftwareEngineering #TestAutomation #HiringInTech #EngineeringLeadership #RealTalk #SDET #QualityEngineering

🌟 Most Common Questions Asked in Product-Based Company Interview For Lead SDET / Project Lead / Principal SDET 🌟 When preparing for interviews at top product-based companies, it's crucial to focus on key coding problems that often come up. Here are a few that you should be familiar with, along with some examples to help you understand the concepts better: 1. Find Peak Element Given an integer array, a peak element is one that is greater than its neighbors. Your task is to find a peak element and return its index. If the array has multiple peaks, return the index of any peak. Simple Example: Input: nums = [1,2,3,1] Output: 2 Explanation: 3 is a peak element at index 2. Complex Example: Input: nums = [10, 20, 15, 2, 23, 90, 67] Output: 1 or 5 Explanation: Both 20 (at index 1) and 90 (at index 5) are peak elements because they are greater than their neighbors. 2. Equilibrium Index An equilibrium index is a position in an array where the sum of elements on the left is equal to the sum of elements on the right. Simple Example: Input: nums = [-7, 1, 5, 2, -4, 3, 0] Output: 3 Explanation: At index 3, the sum of elements to the left (-7 + 1 + 5) equals the sum of elements to the right (-4 + 3 + 0). Complex Example: Input: nums = [1, 2, 3, 4, 6] Output: 3 Explanation: At index 3, the sum of elements to the left (1 + 2 + 3) equals the sum of elements to the right (6). 3. Dutch National Flag Problem Given an array consisting of only 0s, 1s, and 2s, sort the array in one pass. Simple Example: Input: nums = [2, 0, 2, 1, 1, 0] Output: [0, 0, 1, 1, 2, 2] Explanation: The array is sorted in a single pass using a two-pointer technique. Complex Example: Input: nums = [2, 2, 0, 1, 2, 0, 1, 0, 1, 2] Output: [0, 0, 0, 1, 1, 1, 2, 2, 2, 2] Explanation: The elements are rearranged in linear time to sort the array. 4. Product of Array Except Self Given an array, return an array where each element is the product of all other elements except itself. Simple Example: Input: nums = [1,2,3,4] Output: [24,12,8,6] Explanation: The result array contains the product of all elements except the one at each index ([2*3*4, 1*3*4, 1*2*4, 1*2*3]). Complex Example: Input: nums = [2, 3, 4, 5] Output: [60, 40, 30, 24] Explanation: The result array is [3*4*5, 2*4*5, 2*3*5, 2*3*4]. These problems are crucial for testing your understanding of core algorithms and problem-solving skills. Make sure to practice them thoroughly to be well-prepared for your next interview! #Follow #DSA #ProductBasedCompanies #CodingInterview #SDET #InterviewPreparation #Algorithms

How to Survive an SDET Job? 1. A lot of times, people don't know what they want from you. If they want you to "fix their automation", write up tickets, and ask product professionals to prioritize them. 2. If there is manual testing, the product developers help out. No exceptions. 3. If there is toxicity and an extreme amount of politics, you will never change it. Leave. 4. Code reviews are not optional. 5. Be kind to people. 6. If you have to hire a SDET, be strict about your hiring process. 

🚀 Transitioning from QA to SDET: Your Career Leveling-Up Guide 🎮 Are you ready to evolve your QA career? Here's why becoming an SDET (Software Development Engineer in Test) might be your next power-up: 💰 Higher earning potential 🔧 Expanded technical skillset 🌟 Greater impact on product quality 🔑 Key to unlocking senior tech roles Top 5 skills to master: 1. Programming (Java/Python + JavaScript/TypeScript) 2. Automation frameworks (Playwright, Selenium, Cypress,Katalon) 3. CI/CD pipelines(Jenkins,Azure Devops) 4. API and performance testing(Karate,Postman,Gatling,jmeter, Neoload) 5. Containerization (Docker, Kubernetes) 🔥 Hot Tip: Start contributing to open-source testing projects. It's great for learning and your portfolio #SDET #QualityAssurance #CareerGrowth #TechCareers #SoftwareTesting #AutomationTesting

💼 Attention QA and SDET professionals! Are you looking for a change or preparing for your next big opportunity? One of the most frequently asked interview questions, especially for automation and coding rounds, is sorting algorithms—Bubble Sort is a classic favourite! 🧑💻 Here’s a quick refresher in Python to boost your preparation: def bubble_sort(arr):   n = len(arr)   for i in range(n):     for j in range(0, n-i-1):       if arr[j] > arr[j+1]:         arr[j], arr[j+1] = arr[j+1], arr[j]   return arr # Example usage arr = [64, 34, 25, 12, 22, 11, 90] print("Sorted array:", bubble_sort(arr)) 🔑 Key takeaway: While Bubble Sort isn’t the most efficient, it’s often used in interviews to test your understanding of algorithms and ability to optimize code. If you're ready to explore exciting QA/SDET roles or want to sharpen your interview skills, stay tuned for more tips and opportunities! Let’s connect. 🚀 #QAJobs #SDET #BubbleSort #CodingInterview #TestAutomation #QualityAssurance #JobSearch #CareerChange #Python #InterviewPreparation #AutomationEngineering #TechCareers #Hiring #Testing

From Automation Test Engineer to SDET: Embracing Career Development In the ever-evolving world of technology, the journey from Automation Test Engineer (TAE) to Software Development Engineer in Test (SDET) represents a transformative shift. This change embraces a broader perspective in testing, embedding quality into every phase of the software development lifecycle and reshaping the future of quality assurance. Key Changes:  Skill Expansion  - Evolving from scripting to understanding system architecture and CI/CD pipelines.  - Emphasizing programming as an essential skill, no longer just "nice to have." Beyond Automation  - Building frameworks and tools that empower both developers and testers.  - Focusing on scalability, maintainability, and operational efficiency. Collaborative Team Dynamics  - Acting as a bridge between development and operations teams.  - Participating in design discussions, code reviews, and risk analysis. Why This Evolution Matters:  Improved Software Quality: Identifying and addressing issues earlier.  Career Growth: As a hybrid developer/tester with unique value.  Future-Proof Skills: Aligning with the industry's shift toward DevOps and Agile practices. Ready to Start?  Diversify Your Skills: Dive into development, architecture, and systems thinking.  Explore Modern Tools: Familiarize yourself with Kubernetes, Docker, CI/CD pipelines, and cloud technologies.  Stay Curious: Keep learning, experimenting, and exchanging ideas with peers. This evolution is not just a career move—it’s a mindset shift. Embrace it to thrive in the ever-changing tech landscape! #CareerGrowth #SDET #Automation #QualityAssurance #SoftwareTesting

🔄 The SDET Identity Crisis: Stuck Between Two Worlds? 🐞 After years in the trenches as an SDET and during my journey from SDET to Software Engineer I've noticed a frustrating pattern that many of us face. Let me share a reality that's rarely discussed: 😕 The Development Transition Challenge: When SDETs try to move to pure development roles, we often hear: "But you're a test engineer, where's your product development experience?" This, despite building complex test automation frameworks, designing scalable testing architectures, and writing code that's just as crucial as production features. 📉 The QA "Overqualified" Paradox: Try to pivot to QA leadership? "You're too technical for this role." The same coding skills and architecture experience that make us valuable suddenly become a barrier. It's as if hiring managers can't see past the "test" in our job title. 🎯 The Truth About SDETs: SDETs build and maintain production-grade testing infrastructure. SDETs write code that tests code. SDETs understand both development and quality perspectives. ⚡️ Reality Check: An SDET who has architected entire test automation frameworks from scratch, managed CI/CD pipelines, and written thousands of lines of code isn't "just a tester" or "overqualified for QA." We're engineers who happen to specialize in quality and automation. 💡 What Needs to Change: HR needs to understand that SDET !== "just testing" Hiring managers should value our unique full-stack perspective The industry needs to recognize that building test frameworks IS software engineering #SDET #CareerTransition #SoftwareEngineering #QualityEngineering #TechCareers #JobSearch #Engineering #SoftwareDevelopment #HiringManagers #CareerGrowth

Some of the most important but 'often ignored' test automation concepts that must be mastered for faster growth in quality engineering domain are -: - Learning to implement testability & controllability in the application under test. - Controlling and reducing test flakiness for automation runs. - Ensuring maximum usage of your automation (run atleast once for every PR) - Ensuring maximum acceptance for your automation among tech & product. - Developing the reporting & analytical history of your automation runs. - Ensuring proper logging for most optimised failure cases debugging. - Creating the test cases tagging for running selected/module wise cases. - Developing CI CD mindset & pipelines using your automation. - Developing and maintaining automation environment and infrastructure. - Creating business impact/ROI metrics for your automation framework. - Optimising automation run time using parallel runs and infra scaling. - Developing and maintaining end to end pipelines which have build, deploy, test & monitor steps embedded into the pipeline stages. - Understanding the user behaviour , production issues & engineering productivity problems to prioritise WHAT to automate ? - Cracking WHERE to run the automation suite depending on the type of application , infra availability & feasibility. - Many more practical learnings ......... Remember , these are some of the core practical concepts which make us an expert quality engineer / test architect , but interestingly these are not covered in most of the automation courses. Rather these skills are not easy to be taught, but perfectly grasped when learnt by directly working in such an opportunity. 🚀 P.S - If you wish to work on above points , grow your skills & have related industry experience ,and excited to be part of an amazing journey with Zupee 🏅 ,we are hiring for SDET-1 & Lead QA/SDET roles. 🥁 DM me/ Mamta Pandey for referring 📞 your profile in above job openings. 🤝 #openings #sdet #cicd #jobopportunites #jobs #referrals #skillset #automation #engineering #sdetroadmap #mentorship #testing #pipelines Sangeetha Swamy Akshay Gulati Dilsher Malhi Aman Gupta Saurav Yadav Jyoti Gupta Anshul Mittal Naveen Kadyan Akanksha Dhamija Rajneesh Yadav

#Prophecy [Startup] recent SDET Interview questions 𝐑𝐨𝐮𝐧𝐝 1: Q1. Code to find Next Greater Element (NGE) for every element . -Time complexity -Optimized approach E.g. Input: arr[] = [ 4 , 5 , 2 , 25 ] Output:  4      –>   5                5      –>   25                2      –>   25               25     –>   -1 Explanation: Except 25 every element has an element greater than them present on the right side Q2. Write test Cases of the code. Q3. Let us suppose this function is the API. How will you write code to test it, (API Automation)? Q4. How to do authentication? Q5. What are headers in API testing Q6. Authentication vs Authorization. Q7. Selenium code to test the login page Q8. Test Cases for the login page 𝐑𝐨𝐮𝐧𝐝 2: Q1: Write a code to Implement tail -f command (tail -f command prints last few lines of one or more files) Followup : Write test cases for this  Explanation: Need to write a function that takes filepath and number of lines as a parameter , returning last n lines of the file(e.g. Log file ) Q2: —-Write Test cases and Automation for given app—-------- GoogleDocs with below functionalities - Create a doc file - Share it with any user (email) -> EDIT/READONLY/COMMENTONLY - When anyone edits the document you and others can see the changes Asked to write 2 things: Test areas - Test cases Automation strategy 📢 If you’re looking for daily job openings, especially in QA, SDET, and automation, from 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐁𝐚𝐬𝐞𝐝 companies join my Telegram channel! https://lnkd.in/gXWP2xiM #SDET #AutomationTesting #SoftwareTesting #InterviewExperience #APITesting #TestAutomation #Prophecy #TechInterviews #SoftwareDevelopment #startup