Tallan Consultant Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Tallan.
Tallan
Lead Consultant
Lead Average Negative experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical
It was pretty straightforward. We discussed my skillsets and experiences, the tech I've worked with, and how it could be utilized in their company. Just gotta be open minded.
Confirmed questions1 question
- Can you tell us about your experience?
Tallan
Consultant
Entry Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation Offer
Interview formats
Behavioral Technical Coding Presentation
I got an email from someone after chatting with a recruiter at a Career Fair. We had a phone chat which was basically to check if I fit the company vibe. Then there was a technical phone interview where they just asked me vocabulary questions about OOP, Algorithms, and Databases. After that, I got an email for the final on-campus interview. This interview included 3 coding questions, a discussion about my answers with an engineer, and then a chat with a manager. For each question, I had to provide pseudocode and then write the actual program in C++, Java, or Python.
Confirmed questions4 questions
- Can you explain short circuiting in logical expressions?
- What distinguishes an abstract class from an interface?
- If you're given a starting day of the week and a number, can you write a function to determine the day of the week that occurs that many days later? For instance, with 'Monday' and 5, what's the output?
Tallan
Consultant
Mid Average Neutral experience No offer 1 round
Interview process
Phone screen Technical screen
Interview formats
Technical Coding Behavioral
It was a technical phone interview that lasted around 30 minutes. First, there were some personal interest questions to kick things off. Then, it quickly moved to rapid-fire definition questions about OOP. Finally, there was an optional database section. None of the questions really tested programming skills.
Confirmed questions3 questions
- Can you define encapsulation?
- Could you provide definitions for OOP concepts?
- Are there questions related to databases?
Tallan Consultant Interview Questions
Quoted word for word from Tallan interview reports.
“What distinguishes an abstract class from an interface?”
Read reports →“If you're given a starting day of the week and a number, can you write a function to determine the day of the week that occurs that many days later? For instance, with 'Monday' and 5, what's the output?”
Read reports →“What is source control and what is the reason for using it?”
Read reports →“Can you define encapsulation?”
Read reports →“Can you explain short circuiting in logical expressions?”
Read report →“Can you explain what an abstract class is?”
Read report →“Could you explain the difference between a synchronous and an asynchronous call?”
Read report →“What are queues, what are stacks, and what are linked lists?”
Read report →“Could you elaborate on the workings of a binary search tree?”
Read report →Formats, difficulty and experience
Across all 13 Tallan interview reports.