🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Role & responsibilities Develop a design for the automation framework based on object-oriented design patterns. Redesign the existing automation framework for future scalability and sustainability. Develop an automation framework for unit-level, system-level, and end-to-end testing. Enhance and update the existing framework for new product development and testing. Bug fixes and maintenance. Enhancing the existing automation framework, including bug fixes, new feature additions, and maintenance. Experience working in cross-functional product development environments. Strong experience in Unit Integration Testing, Grey Box Testing, White Box Testing, or Software Verification. 8+ years of experience in software verification, integration testing, or embedded software development. The primary responsibility of this role is bringing the Object-Oriented Design approach to the current automation framework by adopting standard design principles and practices. Design Thinking, Problem-solving, Teamwork, Cross-collaborating with multiple functional, Object-Oriented Design experience, Python, C/C++, LabVIEW, Embedded system knowledge, Hardware schematic reading capabilities, Having worked on Automation development for embedded systems, mobile apps and web application will be added benefit. Influence design and implementation decisions from a testability and quality perspective. Serve as the subject matter expert (SME) for white-box and grey-box testing methodologies. Define testing approaches based on software architecture, design, interfaces, and code implementation. Own the Unit Integration Testing (UIT) and Grey Box Testing strategy for assigned projects and product lines. Perform impact analysis for software changes and enhancements. The Technical Leader UIT/GBT is a senior technical individual contributor responsible for defining, driving, and executing Unit Integration Testing and Grey Box Testing strategies for embedded software systems. The role requires deep understanding of software architecture, source code, internal interfaces, and integration behaviors to identify defects early in the development lifecycle. Analyze execution traces, logs, and internal variables to investigate failures and unexpected behaviors. Validate interactions between software units and subsystems. Leverage source code knowledge to derive effective test scenarios. Review implementation details and internal software behavior to improve defect detection capability. Expert knowledge of the field's concepts, practices, and procedures. Relies on extensive experience and judgment to plan and accomplish goals. Performs a variety of tasks. May lead and direct the work of others. A wide degree of creativity and latitude is expected. Typically reports to a supervisor or manager. Preferred candidate profile Bacholor Degree in ECE / IT Should expereince in Embedded Background .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.