WeRide

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·Data Scientist·Technical Phone Screen

Jul 2026

WeRide data scientist round with two pandas problems back to back. Both were heavier than I expected for a DS role, felt more like a data engineering screen honestly.

Write a pandas function that adds a centered sliding-window average column to a DataFrame. For each row, average the k rows before it, the row itself, and the k rows after it. Rows without a full window on either side should get -1.
Given a DataFrame of time intervals per vehicle (and sometimes per event type), write pandas code to merge overlapping or touching intervals within each group, returning one row per merged interval.

“The edge case handling is where I fumbled.”

View Post

WeRide·Data Scientist·Technical Phone Screen

Jul 2026

WeRide data scientist interview, technical phone screen that went deep fast. Two big questions, both stat-heavy, and I felt underprepared on the sampling side.

You have two datasets from different sources (e.g. two system versions, cities, or time periods). How do you test whether they come from the same underlying distribution? Walk through continuous vs categorical variables, parametric vs nonparametric tests and their assumptions, visual diagnostics, effect sizes, statistical vs practical significance, multiple testing, and what changes when sample sizes are very unequal.
What sampling methods do you know and when would you use each? Cover simple random, stratified, cluster, systematic, and weighted or importance sampling at minimum, and say which you'd prefer for product evaluation.

“This one took a while to unpack.”

View Post

WeRide·Data Scientist·Technical Phone Screen

Jul 2026

WeRide data scientist interview focused entirely on autonomous vehicle metrics design, which I wasn't fully expecting to be so deep on the product analytics side. Four-part case question that kept branching, felt like I was being stress-tested the whole time.

Design a multi-dimensional metric framework for ride quality in an autonomous vehicle context, covering efficiency, comfort, safety proxies, and reliability/trust.
What would you pick as the primary north-star metric for autonomous ride quality, and what guardrails would you put around it to avoid optimizing for the wrong thing?
You notice the ratio of actual ride time to planned ETA is much higher than expected. Walk through how you'd figure out if this is a real product problem or an artifact of how the metric is defined or measured.
What additional data would you ask for to fully diagnose the elevated ride-time-to-ETA ratio?

“This took me a while to get organized.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

Third round at Weride with someone based in China. Split pretty evenly between talking through my resume and doing coding problems, which I wasn't fully expecting going in.

Implement a function that generates a random integer between 1 and 10 using only a given function that generates a random integer between 1 and 7.
Given a stream of points added to a 2D plane, implement a data structure that can efficiently count the number of axis-aligned squares that can be formed using a queried point as one of the corners.

“Classic rejection sampling problem.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

Weride software engineer interview with a classic stack problem. Nothing too wild but the constraint to hit O(n) time and space made it feel more deliberate than a throwaway warmup.

Given a string containing only bracket characters, write a function to determine if the brackets are valid (properly matched and correctly ordered). Solve it using a stack in O(n) time and O(n) space.

“Pretty standard stack question but I fumbled the edge cases a bit.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

WeRide software engineer interview focused entirely on math-heavy algorithm problems: matrix multiplication, fast exponentiation, and Fibonacci via matrix exponentiation. Pretty niche stuff, felt more like a competitive programming screen than a typical SWE interview.

Implement matrix multiplication for an n×m matrix A and an m×p matrix B, returning the resulting n×p matrix C. Handle modular arithmetic if a MOD value is provided.
Implement fast exponentiation: given x, k, and an optional MOD, compute x^k (mod MOD) in O(log k) time. Handle edge cases like k=0 and x=0.
Compute the nth Fibonacci number (n >= 0) using matrix exponentiation to achieve O(log n) time complexity. Apply modular arithmetic where required.

“Pretty straightforward once you get the dimensions right, but I fumbled the index order on my first pass and had to back up.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

Weride SWE interview, split into two halves: 30 minutes of resume walkthrough then straight into a coding problem. Pretty standard format, nothing too wild.

Reorder a linked list such that nodes are rearranged in a specific interleaved pattern (e.g. LeetCode 143 style).

“Linked list manipulation always feels deceptively simple until you're actually doing it under pressure.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

Weride coding interview, one algorithmic question on fast exponentiation. Pretty standard stuff for a systems-adjacent role but the negative exponent edge case is where people slip up.

Implement fast power: given a base x and integer exponent n, compute x^n in O(log n) time. Make sure to handle negative exponents correctly.

“The squaring part came naturally enough, split even/odd exponents, recurse down, done.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

Jun 2026

Weride frontend interview had me implementing a debounce utility from scratch, which sounds straightforward until they ask you to layer in leading/trailing edge options and walk through test cases live. Pretty focused session, no behavioral fluff.

Implement a debounce(fn, wait, options) function in JavaScript, where options controls whether fn fires on the leading edge, trailing edge, or both.

“Started with the basic version fine, delay the call, cancel if another comes in before wait ms.”

View Post

WeRide·Software Engineer·Technical Phone Screen

Jun 2026

Second round at Weride for a software engineer role, conducted with someone on the US team. Split pretty evenly between walking through my resume and a coding problem.

Solve the 'Swim in Rising Water' graph traversal problem (LeetCode 778).

“This one is tricky if you haven't seen it before.”

View Post

WeRide interview FAQ

What rounds are in the WeRide interview?

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

What does the WeRide technical phone screen cover?

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