← Back to Directory

WeRide interview notes, page 1 of 4

Mid-sized

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

31 interview notes · updated Jul 2026

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
Weride SWE interview hit me with the classic kth largest element problem. They wanted more than just 'sort and index', so be ready to actually code quickselect and defend your pivot choices.
  • Given an integer array and an integer k, find the k-th largest element in the array. Walk through multiple approaches and their trade-offs, then implement a partition-based selection algorithm from scratch.

“I started with sorting because it's the easiest to reason about, but they pushed back pretty fast asking if I could do better.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
Weride software engineer interview with a multithreading question that required both identifying a race condition and writing a fix. Pretty focused, one meaty coding problem.
  • Write a program showing how i++ causes a race condition in a multithreaded context, then write a thread-safe version of the same program.

“The concept itself isn't hard to explain verbally but actually writing it out cleanly under pressure is a different thing.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
First round at Weride for a software engineer role, split between talking through my resume and a coding problem. Pretty standard setup, nothing too wild.
  • Implement an LRU Cache from scratch.

“Classic question but I still fumbled the eviction logic for a second.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

Apr 2026
A short technical screen at Weride for a frontend role, basically just a 5-minute conversation about how you use AI tools in your actual work. Pretty low-pressure but they wanted specifics, not vague hand-waving.
  • 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 also talk about where you think they fall short or where you deliberately avoid relying on them.

“This is the kind of question that sounds easy until you're actually on the spot and realize your examples are kind of shallow.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
WeRide software engineer interview with a pretty gnarly string/expression parsing problem. The main challenge was the O(1) space constraint on the base version, which is brutal, and then a follow-up that relaxed it to O(n) but added way more complexity to the input format.
  • Given an expression with lowercase letters, '+', '*', and parentheses where '+' never appears outside any parentheses, return an equivalent expression using only '+' by fully expanding all products (e.g., (a+b)*(c+d) becomes ac+ad+bc+bd). The catch: achieve this with O(1) extra space.
  • Follow-up: now '+' can appear outside parentheses too, like in 'a+b*c*(d+e+f)+k+m*(g+h)+i'. Output the fully expanded form. You can use O(n) extra space, such as a stack.

“The expansion logic itself isn't too bad once you think of it as distributing terms across parenthesized groups.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a software engineering role at Weride and got a coding question that was a Sudoku variant. Not a lot of detail to share but it was a puzzle-style algorithmic problem.
  • Solve a variation of the Sudoku problem (a Sudoku-like constraint satisfaction puzzle).

“Backtracking is the obvious move here and I went with it, but the variant part is what trips you up.”

View Post

WeRide·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral deep-dive at Weride for a software engineer role, but the interviewer was openly skeptical the whole time, pushing back on impact claims and questioning whether my decisions were actually mine to make. Felt less like a conversation and more like a deposition.
  • Walk me through a major project you led: what was the problem, what did you specifically do, and what was the outcome?
  • Why did you make that specific technical decision and not a different approach? What alternatives did you actually consider?
  • How do you know your contribution actually moved the needle? Could the team have gotten the same result without you?
  • Looking back, what would you do differently on that project, and does that change how you evaluate the outcome?

“I had a solid answer prepared but the interviewer kept interrupting with 'why not just do X instead' before I could finish a thought.”

View Post

WeRide·Data Scientist·Technical Phone Screen

Apr 2026
WeRide Data Scientist interview that went deep into statistical testing territory. The whole thing centered on distribution comparison, which sounds narrow but sprawls fast once you get into multivariate settings and sampling design. Technically dense and not something you can wing.
  • You have two datasets from different systems or populations. How would you test whether they come from the same distribution, for a single variable?
  • How would you compare two high-dimensional samples where you're not just looking at one feature but many at once?
  • Once you get a statistically significant result, how do you decide if it actually matters? Walk me through how you'd handle effect sizes, multiple testing, and clustered data.
  • What sampling methods would you use when collecting evaluation data, and when would you prefer one over another?
  • What if one dataset was collected only during rush hour and the other covers the full day? How does that affect your comparison?
  • How would you specifically test rare safety-critical tail events rather than average behavior?

“I started with KS test because that's the reflex answer, but they pushed back pretty quickly asking when I'd use Anderson-Darling instead or why I might care about Wasserstein distance.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Apr 2026
WeRide software engineer interview with a pretty gnarly string parsing problem split into two parts. The algorithmic depth they expected was no joke, and the O(1) space constraint on part one really threw me.
  • Given a string expression with lowercase variables, '+', '*', '(', and ')', fully distribute all multiplications over additions and return the equivalent expression using only '+'. In part one, assume '+' only appears inside parentheses, and implement an O(n) time solution using O(1) extra space beyond the output without using a stack.
  • Extend the solution to handle the general case where '+' can appear outside parentheses as well, including nested parentheses. Use a stack to track current multiplication segments, targeting O(n) time and O(n) space, and analyze the complexity and key edge cases.

“The O(1) space constraint is where I got stuck.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Five phone screen rounds for a software engineer role at Weride, each split between resume walkthrough and a coding problem. Interviews were scheduled around China time, so evening slots were on the table. The coding portion focused on Tries.
  • Implement or work through a problem involving a Trie data structure.

“Five rounds and they kept the coding portion pretty focused.”

View Post