
CLEAR Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at CLEAR.
Software Engineer Intern
You start with a codesignal assessment. If you pass that, you have a 30 minute recruiter call. If that goes well, then you do an hour long technical interview on codesignal. Right after the technical interview, there's a 30 minute behavorial interview.
- Describe a time you made an error.
Software Engineer
I applied online and heard back from a recruiter about a week later. After that initial call, they set up a tech screen. It took about two weeks to get an update, and then they changed the tech screen to a take-home assignment. Once I finished the take-home, I waited another week for the final round, which had one behavioral and one technical interview. Another two weeks passed before I heard back. After the final round, they wanted me to have a casual chat with one of the directors. Three more weeks went by, and then I got the rejection.
- Questions about data structures like stacks and queues were asked, specifically to implement undo/redo and a banking system with cashback.
- Behavioral questions were standard.
Software Engineer
I had a call with the recruiter, then a one hour tech screen, followed by a one hour data structure interview, a one hour system design interview, and finally a one hour collaboration interview. None of it was super tough, but the interviewers were kind of distant. One interviewer seemed to be texting while I was talking.
- Call with recruiter
- one hour tech screen
- one hour data structure interview
CLEAR Software Engineer Interview Questions
Quoted word for word from CLEAR interview reports.
“Implement Caesar's Cipher in Java.”
Read reports →“Find the 1-indexed position of a value in a sorted array in logarithmic time. If the value isn't found, return the negative of the 1-indexed position where it should be inserted. For example, finding an element at index 0 should return 1, and if it should be inserted at index 0, return -1. Test cases were provided.”
Read reports →“Solve one medium LeetCode problem.”
Read reports →“Solve one easy LeetCode problem.”
Read reports →“Can you solve a DFS problem?”
Read report →“Was there an island/graph/DFS Leetcode question for the online test?”
Read report →“What do you want?”
Read report →“Can you describe how to run the code you wrote?”
Read report →“Active or passive job search?”
Read report →Formats, difficulty and experience
Across all 18 CLEAR interview reports.