WeRide Interview Questions — Page 2

WeRide·Software Engineer·Technical Phone Screen

May 2026

Interviewed for a Software Engineer role at WeRide with a heavy focus on Java concurrency. The questions drilled pretty deep into the memory model and thread-safety primitives, so if you're not solid on that stuff going in, you'll feel it.

What are the differences between Thread, Runnable, and Callable in Java? When would you use each?
Can you explain the Java Memory Model and how it governs visibility and ordering between threads?
What are the differences between volatile, synchronized, Lock, and the Atomic classes? When is each appropriate?
Why is i++ not thread-safe, and how does this relate to the lost update problem?
How would you implement a thread-safe counter without using synchronized?
What new features or improvements were introduced in a recent JDK version that you found useful?

“Ran through the basics fine but stumbled a bit when they pushed on Callable vs Runnable beyond just 'Callable returns a value.' Should've talked more concretely about Future and how you actually get the result back.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026

Weride coding interview, got a matrix multiplication problem that felt more like a systems/math warmup than a pure algo question. Pretty straightforward if you know your linear algebra basics, but they pushed on edge cases and complexity in ways I didn't fully anticipate.

Implement matrix multiplication for two matrices A (m x n) and B (n x p), returning the product C (m x p). Include dimension validation and explain the time complexity.

“I started with the triple nested loop and got that right pretty fast.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

May 2026

A 30-minute round at Weride for a frontend engineer role that split time between walking through resume projects and a rapid-fire sweep of frontend fundamentals. Nothing too unusual but the breadth they expected to cover in half an hour was a bit much.

Walk me through a project on your resume with technical depth.
Explain the CSS box model and how layout works in the browser.
How do JavaScript closures work, and can you give an example?
Explain the JavaScript event loop and how it handles asynchronous operations.
How do Promises work in JavaScript, and how do they relate to async/await?
Explain how `this` binding works in JavaScript across different contexts.
Describe the browser rendering pipeline from receiving HTML to painting pixels on screen.
How does React's reconciliation algorithm work, and what role do hooks play?
What are some strategies you'd use to optimize frontend performance?
What are the basics of HTTP and common web security considerations for frontend engineers?

“This is the part I always underestimate.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

May 2026

Resume-based technical screen for a frontend engineer role at Weride, focused almost entirely on data visualization work. If you have OpenGL or WebGL on your resume, be ready to go deep because they will.

Walk me through a data visualization project on your resume that involved OpenGL or WebGL.
How does the rendering pipeline work in your implementation, and what shader programming did you write?
What performance optimizations did you apply, specifically around draw call reduction or batching?
What were the trade-offs you considered between using native OpenGL versus WebGL for this project?
How did you handle user interaction in your visualization, and what were the technical challenges there?
What was your specific contribution to this project versus what the team built?

“This was basically the whole interview.”

View Post

WeRide·Frontend Engineer·Technical Phone Screen

May 2026

Weride frontend interview had me implementing a custom React hook from scratch, which sounds manageable until you're live-coding and second-guessing every cleanup detail. The question had a few layers to it and the follow-up discussion about tab visibility caught me a bit flat-footed.

Build a custom React hook called useFps() that tracks and returns the current frames-per-second of the page, using requestAnimationFrame with a rolling time window to smooth the value, and properly cleans up when the component unmounts. Also discuss how the hook behaves when the tab is backgrounded and how you'd prevent unnecessary re-renders.

“The core rAF loop wasn't hard to sketch out but I kept second-guessing the cleanup.”

View Post

WeRide·Software Engineer·Technical Phone Screen

May 2026

Interviewed for a software engineering role at Weride and got a coding question about building a message queue. Pretty standard systems-adjacent coding problem but it has enough moving parts to trip you up if you haven't thought about it before.

Implement a message queue from scratch.

“I started with a basic array-backed queue and talked through enqueue and dequeue, but they kept pushing on things like what happens with multiple consumers, ordering guarantees, and whether messages get acknowledged before removal.”

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

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

May 2026

WeRide data scientist interview with a meaty domain adaptation question about expanding an autonomous driving eval system from Beijing to Guangzhou. One question, lots of sub-parts, and a follow-up that honestly caught me working harder than expected.

You built an autonomous-driving evaluation system using labeled data from one city. The company now wants to expand to a new city where you can only collect a small amount of data. How would you evaluate whether the system is likely to perform well there? Cover how you'd define the target population and success criteria, assess whether your existing metrics and calibration transfer, detect distribution shift, combine the large source dataset with the small target sample, and make a go/no-go call under limited evidence. Follow-up: if the new city has important scenarios that barely exist in your source data (different road layouts, higher scooter density, different weather, local signage, etc.), how does that change your data collection strategy and edge-case prioritization?

“This one took me a minute to even organize in my head.”

View Post