Glia Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Glia.
Glia
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Take home Recruiter call Offer
Interview formats
Coding Technical
The interview process was pretty standard these days. It started with a take-home assessment, and then they were supposed to provide feedback. I completed the take-home assessment, but after a few weeks and sending emails to the People team, they never responded (first red flag). About a month later, I received a rejection email stating they had moved forward with other candidates who were further along in the process (second red flag). My advice is: don't waste candidates' time! Be polite. The way you communicate with candidates reflects how you communicate within the company afterwards.
Confirmed questions1 question
- Could you create a rest api using express?
Glia
IOS Software Developer
Mid Difficult Positive experience No offer 3 rounds
Interview process
Technical screen Onsite Background check
Interview formats
Technical Coding Behavioral
It was a very hands-on process with a technical theoretical plus practical interview, a cultural fit chat, and a talk with the CTO. They really focused on practical aspects and asked about things relevant to daily work, avoiding hypothetical scenarios. The practical part involved building and testing a simple endpoint. Communication throughout was excellent; the interviewers were friendly, and the feedback provided was clear and detailed. Despite it being a great experience, I didn't quite have the technical skills needed for the role.
Confirmed questions2 questions
- Could you build an endpoint for data retrieval and include its tests?
- How would you handle a situation where your lead assigns a task you disagree with?
Glia
Software Engineer
Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding Behavioral
Had an intro call that was pretty chill. Then a technical assignment, which was fine, but it had this optional optimization part. I didn't really have time for it and figured it was optional, so I didn't sweat it. But turns out, they apparently only cared about that optional bit. I did the required stuff right, but they dinged me for not finishing the optional part. Their communication was really unclear about what they actually wanted most in the assignment. On the plus side, they did give good feedback.
Confirmed questions2 questions
- Can you discuss projects you did in university?
- Can you discuss projects you did at work?
Glia Software Engineer Interview Questions
Quoted word for word from Glia interview reports.
“Can you explain the difference between NoSQL and SQL databases?”
Read reports →“Could you create a rest api using express?”
Read reports →“Could you build an endpoint for data retrieval and include its tests?”
Read reports →“Can you design a service like Bitly for URL shortening, and how would you approach scaling it?”
Read reports →“Could you design a URL shortening service, similar to Bitly?”
Read report →“Can you describe how you would build a URL shortening service?”
Read report →“How would you handle a situation where your lead assigns a task you disagree with?”
Read report →“In retrospect, how would you have approached certain past situations differently?”
Read report →“Can you discuss projects you did in university?”
Read report →Formats, difficulty and experience
Across all 10 Glia interview reports.