Interview Experiences

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

Share yours, earn XP

4 stories

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

BrillioSoftware Engineer
Reported Jul 2026

Brillio Software Engineer interview: machine coding with immediate feedback

My first round was a machine-coding interview with a panel. The interviewers were polite and gave feedback immediately while I worked through the problems. They also asked a few theoretical questions alongside the coding. I explained fundamentals such as event-loop behavior and closures. The panel guided me through the discussion instead of simply throwing questions at me. It felt like an interac…

OfferTechnical Screen0
BrillioSoftware Engineer
Reported Jul 2026

Software Engineer interview at Brillio: HR then technical fit

The process had two stages. First, I had a telephone discussion with HR about my background, experience, and expectations for the role. The next interview assessed problem solving, technical knowledge, past projects, and overall fit. It was a standard, straightforward sequence of context-setting followed by technical evaluation. Location: India. Overall feedback: positive. Offer status: no offer.

0
BrillioSoftware Engineer
Reported Jul 2026

Brillio Software Engineer interview with three technical rounds and no follow-up

A recruiter contacted me through Brillio Guadalajara. I missed the first call, so they followed up by message to confirm my interest and share the position details. There was no separate HR screening after that. The interviews were simply scheduled. The process became three technical interviews in sequence: one with Brillio, then one with the client, followed by a final technical interview with t…

No response0
BrillioFull Stack Engineer
Reported Jun 2026

Brillio Full Stack Engineer interview: a one-hour NodeJS group coding exercise

The group interview format felt intense from the start. I was placed with about 20 other people and given a sheet containing a complex NodeJS coding problem. We had one hour to solve it on our own, with no talking allowed. When the hour was up, each person had to present a solution privately to the interviewer. That put a lot of pressure on me. I could not compare approaches with anyone while sol…

Technical Screen0

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