Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

3 stories

Likes earn the author +10 XP for the first 3 likes each day

ValeoSoftware Engineer
Reported Aug 2026

Valeo Software Engineer Interview Experience: C code tracing and embedded protocols

I started with an online assessment on HackerRank, which immediately set the tone. It leaned heavily on data structures and algorithms in C, with many code-tracing prompts where I had to predict how snippets would behave and whether they would compile. There were also multiple-choice questions on embedded systems and communication protocols, especially UART, SPI, and I2C. After the assessment, I…

HR Screen0
ValeoSoftware Engineer
Reported Jul 2026

Valeo Software Engineer Interview Experience: Academic projects, C fundamentals, and ECE questions

My first round was a written test that felt easier. Then we discussed projects I had completed during my academics, with a strong focus on C basics. The interviewers cared most about my project, so I had to explain every block and why I chose each component. They followed up with "why" and "what if" questions. They also tested C fundamentals directly: pointers, arrays, strings, functions, structu…

Online Assessment0
ValeoSoftware Engineer
Reported Jul 2026

Valeo Software Engineer Interview Experience: HackerRank, an online-store task, and a project walkthrough

The process began after I sent my CV. I completed a HackerRank assessment covering backend, frontend, HTTP, and cloud-related knowledge. Then they sent a task to build a simple online store or marketplace. The next step was an interview where I walked through the task and my experience, including what I did and how I approached it. The process felt structured and work-like because the conversatio…

Online Assessment0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP