Glint Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Glint.
Glint
Software Engineer
Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Technical Behavioral
I applied and chatted with the Head of Engineering. We discussed the company, my role, and my background. It went well. Then, I got a technical challenge to do at home. I spent about 5 days on it, but never heard back about it. It felt like I just did a lot of free work for Glint. The challenge had many requirements but wasn't super hard, just time-consuming.
Confirmed questions4 questions
- Regarding the technical challenge, were there questions about mobile/desktop layout?
- Did the technical challenge include questions on state/session management?
- Were unit tests a part of the technical challenge?
Glint
Software Engineer
Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical
The interview process was excellent and mirrored what a good interview process should be, ensuring mutual fit between the candidate and the company. I appreciated the transparency and their readiness to answer all my questions. It was clear this company has a strong culture and leadership, making me want to join. The process was also very efficient, with quick feedback and no waiting periods. It included several phone interviews followed by an in-person interview.
Confirmed questions1 question
- What feedback would your colleagues give about your leadership abilities?
Glint
Software Engineer
Entry Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding
This interview process wasn't great for finding good engineers. It was too focused on specific Java knowledge and didn't seem to consider candidates with other backgrounds. They didn't even review my resume properly. I was rejected because I wasn't proficient in Java, even though my code passed all test cases and my resume clearly stated I wasn't actively coding in Java.
Confirmed questions1 question
- Given a list of numbers and a starting position, find a sequence of valid jumps to reach the end of the list. A valid jump from a position `pos` can be anywhere from 0 to `list.get(pos)`. Return the sequence of jumps or null if no such sequence exists.
Glint Software Engineer Interview Questions
Quoted word for word from Glint interview reports.
“Given a list of numbers and a starting position, find a sequence of valid jumps to reach the end of the list. A valid jump from a position `pos` can be anywhere from 0 to `list.get(pos)`. Return the sequence of jumps or null if no such sequence exists.”
Read reports →“Can you explain the details of database transaction management?”
Read reports →“Regarding the technical challenge, were there questions about mobile/desktop layout?”
Read reports →“Did the technical challenge include questions on state/session management?”
Read reports →“Were unit tests a part of the technical challenge?”
Read report →“Were there questions about design decisions in the technical challenge?”
Read report →“Can you describe how you would design a given webpage example?”
Read report →“What feedback would your colleagues give about your leadership abilities?”
Read report →Formats, difficulty and experience
Across all 7 Glint interview reports.