WeRide Software Engineer interview questions

21 Software Engineers have shared notes from their WeRide interviews, with the questions they were asked in each round. That is 68% of the 31 WeRide interview notes on Screna AI.

21 Software Engineer interview notes

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·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·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at WeRide and got hit with a pretty deep question about bridging PhD research into industry work. More of a conversation than a grilling, but it required me to have concrete answers ready, not just vague claims about being 'research-oriented'.
  • Walk me through your PhD research and explain how the skills and experience from it translate to a software engineering role. Be specific about tools, programming languages, systems design, data pipelines, or experimentation. Give a concrete example of taking a research idea and turning it into maintainable production-quality code, and tell us what motivated you to make this transition.

“This was basically four questions stitched into one and I did not realize that until I was already two minutes into answering just the first part.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Weride put me through a pretty intense resume deep dive for a software engineering role. They weren't just skimming the bullet points, they wanted to get into the weeds on every project I listed.
  • Walk me through a major project on your resume. What was the problem you were solving, what did you personally contribute, and what was the measurable outcome?
  • What design decisions did you make during that project, and what trade-offs were involved?
  • Looking back at that project, what would you do differently?

“This sounds straightforward until they start peeling back layers.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Interviewed at Weride for a software engineering role and got hit with a classic algorithms question dressed up with a twist I wasn't fully ready for.
  • Compute the n-th Fibonacci number in O(log n) time.

“I knew the recursive and iterative solutions cold, but O(log n) is a different beast.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026
Weride SWE interview that goes deep on past projects. The whole thing felt like an interrogation of your resume, not a conversation, and they kept pushing until you gave specifics.
  • Walk me through a past project you consider most representative of your work.
  • What specifically was your contribution to that project, as opposed to the team's contribution?
  • What trade-offs did you make during that project, and why did you choose this approach over the alternatives?
  • Looking back, what would you do differently on that project?

“This sounds easy until you're actually in it and second-guessing every project you've ever touched.”

View Post