Urban Science Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Urban Science.
Urban Science
Software Engineer Intern
Intern Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Coding
The interview process was pretty simple. First, they asked some behavioral questions, then moved on to technical ones. After that, I had to solve a coding problem and explain my thinking. I'd suggest brushing up on object-oriented programming and SQL basics before the interview.
Confirmed questions1 question
- What is encapsulation?
Urban Science
Software Developer
Mid Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical
Applied and got a call from the recruiter about 10 days later. He asked some basic stuff and told me about the company and the job. Then, I had a phone interview with a development manager who went a bit deeper into the technical side. After that, they invited me for an in-person interview. It was with two groups of managers, each group having two people. It lasted about an hour and a half. Besides general background questions, it was mostly situational stuff, like asking about a past failure and what I learned, or how I deal with not having enough resources or facing a tight deadline.
Confirmed questions3 questions
- What is your approach when a project falls behind schedule?
- Describe a failure you experienced and the lessons you took away from it.
- How do you manage when you have limited resources or a strict deadline?
Urban Science
Software Developer
Entry Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Coding
The interview process was straightforward, with some OO and SQL questions. I didn't know SQL at the time of my first interview, but I never got a rejection. A few months later, they emailed me about interviewing again for the same role with the same recruiter. So, I thought I'd get a second chance. We went through it all again, and the result was the same: no word after the technical interview. I just got an email for the third time, and I'm not going to reply this time.
Confirmed questions3 questions
- How would you implement quick sort?
- Can you explain some Object-Oriented Programming concepts?
- What are some common SQL queries or operations?
Urban Science Software Engineer Interview Questions
Quoted word for word from Urban Science interview reports.
“What differentiates an abstract class from an interface?”
Read reports →“Explain the difference between left join and right join.”
Read reports →“What are the core concepts of Object-Oriented Programming?”
Read reports →“How do you optimize SQL queries?”
Read reports →“How would you implement quick sort?”
Read report →“What are some common SQL queries or operations?”
Read report →“Can you explain the principles of OOP and provide examples for each?”
Read report →“Can you explain abstract methods, abstract classes, OOP, static members, static member functions, and public interfaces?”
Read report →“How would you handle a situation where you have a conflict with a teammate who is not willing to communicate?”
Read report →Formats, difficulty and experience
Across all 14 Urban Science interview reports.