Design Verification Engineer, Automotive Robotics

About the role

You own the verification strategy for advanced digital designs in automotive robotics. You build test environments and mentor engineers to ensure designs meet functionality, performance, and quality goals. You work across teams to validate complex systems and influence methods for compute engines in AI and high performance computing.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Comprehensive verification plans are defined and executed for complex digital blocks and systems to ensure design correctness.

Verification methodologies and strategy are driven across projects to establish best practices and standards for the verification team.

Advanced test environments are built using SystemVerilog and UVM, and testbenches, cases, and coverage are executed to validate designs.

Specifications are aligned and verification issues are debugged in collaboration with architecture, design, and software teams.

Junior engineers are guided and mentored to strengthen the capabilities of a high performing verification team.

Requirements

10+ years of industry experience in digital design verification with a strong record of technical leadership.

Deep expertise in SystemVerilog and UVM, along with familiarity with formal verification methods.

Strong understanding of computer architecture, microarchitecture, and SoC integration.

Hands-on experience with tools like Questa, VCS, or similar simulation environments.

Excellent communication skills and the ability to lead cross functional collaboration.

A degree is required for this role.

Practical notes

export-controlled technology access and may be affected by citizenship or license approval. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Digital verification for compute engines in AI and high performance computing relies on SystemVerilog, UVM, and simulation environments such as Questa and VCS. RISC-V based designs and chiplet architectures are central to modern implementations. Collaboration with hardware and software teams drives the verification workflow. The environment emphasizes fast paced innovation and continuous verification methodology development.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.