← Back to Directory

WeRide

Mid-sized

Most of these WeRide write-ups come from Software Engineers (17), then Frontend Engineers (4). The most reported rounds are the technical phone screen (20) and the behavioral / leadership round (1).

21 interview notes · updated Jun 2026

WeRide·Software Engineer·Technical Phone Screen

Jun 2026
Weride coding interview, one algorithmic question on Fibonacci with a twist toward the efficient solution. Short and focused, felt more like a technical screen than a full onsite.
  • Compute the n-th Fibonacci number in O(log n) time.

“The naive recursive approach is what everyone reaches for first, and I did too for about 30 seconds before catching myself.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

Jun 2026
A short technical screen at Weride for a frontend role that included a five-minute segment on how you actually use AI tools day-to-day, not just whether you know what they are.
  • How do you understand AI tools like LLMs, ML models, and agents, and how do you actually use them in your day-to-day engineering work? Give concrete examples across things like coding assistance, code review, design exploration, and debugging, and talk about where you choose not to rely on them.

“This one tripped me up a little because I expected a surface-level 'do you use Copilot' type question, but they pushed for specifics fast.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026
Weride put me through a pretty deep Java concurrency session, the kind where you realize halfway through that you've been fuzzy on some of this stuff for years and just never had to confront it.
  • What are the different ways to create threads in Java, and how do you decide which approach to use?
  • Explain the difference between synchronized, Lock, and ReentrantLock. When would you reach for one over another?
  • How does the Java memory model work, and what does volatile actually guarantee?
  • When would you use atomic classes like AtomicInteger versus a lock-based approach?
  • What concurrent collections does Java provide and what are the trade-offs between them?
  • Walk me through how a deadlock can occur in a multithreaded Java program and how you'd prevent or detect it.
  • How do race conditions differ from visibility issues, and how do you address each?

“Ran through Thread subclassing, Runnable, and ExecutorService.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at Weride for a software engineer role, one question the whole time. Pretty focused session, nothing too wild.
  • Implement a message queue from scratch.

“Spent the first few minutes thinking about the interface before touching any logic, which I think was the right call.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

Jun 2026
Weride frontend interview had me implement a custom React hook from scratch, which sounds manageable until you're live on a call and someone's watching you think through rAF cleanup and tab visibility edge cases simultaneously.
  • Build a custom React hook called useFps() that tracks and returns the current frames-per-second of the page using requestAnimationFrame, updates on a rolling time window, and cleans up properly on unmount. Also discuss how it behaves when the tab is backgrounded and how you'd prevent unnecessary re-renders.

“I got the basic loop working pretty fast, timestamps in a ref, count frames over a second, setState with the result.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Weride software engineer interview with a classic stack problem. Nothing fancy, but they wanted you to be precise about the O(n) complexity and not just hand-wave it.
  • Given a string containing only bracket characters, write a function to determine whether the brackets are all properly matched and closed in the correct order. Expected solution is O(n) time and O(n) space using a stack.

“Pretty standard bracket matching problem.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Weride and got hit with the classic kth largest element problem. They wanted more than just a working solution though, so be ready to actually talk through tradeoffs and write quickselect from scratch.
  • Given an integer array and an integer k, find the k-th largest element. Walk through multiple approaches and their tradeoffs, and implement a partition-based selection algorithm from scratch.

“I started with sorting because it's the easiest to explain, then moved to the min-heap approach.”

View Post

WeRide·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral deep-dive at Weride for a software engineering role, but the interviewer was openly skeptical the whole time, pushing back on impact claims and questioning every decision. Less of a conversation, more of a stress test.
  • Walk me through a major project you owned: what was the problem, what did you specifically do, and what was the outcome?
  • Why did you make that technical decision instead of the more obvious alternative?
  • How do you know your work actually had the impact you're claiming?
  • Looking back, what would you do differently on that project?

“This is where the tone got set fast.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Second round at Weride for a software engineering role, done remotely with someone on the US team. Split between talking through my resume and a coding problem, nothing too wild but the algo portion had some bite to it.
  • Given a grid where water rises over time, find the minimum time at which you can swim from the top-left to the bottom-right corner.

“This is LeetCode 778.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Weride and got a coding problem that was a variant of Sudoku. Not a lot of context to share but it was a technical screen focused purely on the problem.
  • Solve a Sudoku-style variant problem (a modified version of the classic Sudoku constraint satisfaction puzzle).

“The twist on the standard Sudoku format is what slowed me down.”

View Post

WeRide interview FAQ

What rounds are in the WeRide interview?

Candidates most often report a technical phone screen (20 write-ups) and a behavioral / leadership round (1).

What does the WeRide technical phone screen cover?

Across 20 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (30 questions), Algorithms & Data Structures (17) and System Design (15).

WeRide interview guides by role

17 notes

WeRide Software Engineer interview questions