Winshuttle Software Engineer 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 Winshuttle.
Winshuttle
Senior Software Engineer
Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Behavioral
It was three rounds. The first two were technical interviews, and the last one was a chat with the manager about the projects at my current company. The first round covered basic stuff about my tech stack and some code complexity questions. The second round was also technical, focusing on senior-level concepts.
Confirmed questions4 questions
- Could you answer technical questions about your stack, such as design patterns?
- Can you discuss code complexity?
- Do you have technical experience with scenarios?
Winshuttle
Software Engineer
Mid Easy Negative experience No offer 3 rounds
Interview process
Phone screen Onsite Recruiter call
Interview formats
Technical Behavioral
The interview involved two phone calls and then a manager meeting in Chandigarh. The phone interviews went well, with questions directly related to the job. However, the manager round focused on how other companies use tools like Jira and included some puzzle questions. The manager seemed to lack knowledge about architecture but still asked me to explain my project's architecture, and didn't seem to understand when I did. After it all, they didn't even let me know if I got the job, just said they'd inform me later.
Confirmed questions2 questions
- Tell me about garbage collection finalization.
- Can you explain some design patterns?
Winshuttle
Software Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
It seemed to be a behavioral and technical interview, but they only revealed that during the phone screen. The interview was cut short because they felt there wasn't a match. I said goodbye, but honestly, that was the rudest interview I've had in years. They didn't explain what they were looking for, and instead, they waited for me to describe my projects. These kinds of quick and dirty interviews aren't good for anyone and make you wonder about other company procedures.
Confirmed questions1 question
- Can you tell me about your current projects?
Winshuttle Software Engineer Interview Questions
Quoted word for word from Winshuttle interview reports.
“Write a C program to reverse a string.”
Read reports →“Can you design a C code to check if one string is a rotation of another without using extra string/array memory, only basic variables?”
Read reports →“Can you solve this puzzle: Given a 7-inch golden bar, how many cuts are needed to divide it so that you can pay out 1 inch of gold each day?”
Read reports →“What are the basics of .Net?”
Read reports →“Tell me about garbage collection finalization.”
Read report →“For the Snake game, like the one on Nokia phones, what's the best data structure to use for it? Also, what new features could be added and how would you test them?”
Read report →“Could you explain the IDisposable design pattern?”
Read report →“What do you understand by the 'Solid' principles in OOP?”
Read report →“Can you explain Continuous Integration?”
Read report →Formats, difficulty and experience
Across all 13 Winshuttle interview reports.