-Which game engine do you prefer and why?, -What data structures do you know and like to work with? -Name 3 data structures, -Explain the difference between Stack and Heap, -What does the Singleton Pattern do?, -How does the online mode work in the Unreal Engine, etc.
Where do you see yourself in 3 years?
Can you list some Off-Page and On-Page optimization techniques?
Why do you want to work for Hotwire?
The questions vary. However, it didn't include any coding questions. Most interviewers have terrible English skill. They don't really understand you, and sometimes don't even know how to say things correctly. For example, "Do you know ACID?" (he pronounces ACID as "a, c, i, d" all letters individually spelled out) instead of pronouncing as the word "acid". So if you say no, terrible, you now got a negative mark. He explains what it is, then you say oh you mean acid, which stands for "Atomicty, Consistency..." and then he agrees; but doesn't matter. You already got a negative point there. Most questions are basically like that "do you know x framework" or "x technology". Other type of technical question is "tell me about the architecture of what you're working on" and then when you talk about it, they ask something about that architecture. The problem is, sometimes they ask irrelevant part, which you don't really mention in the architecture. For example if you're doing some back-end work for some product, they might ask you something related to front end. It just seemed to me that they want to steer the conversation to the areas which is outside of your main responsible area. The other thing they insisted was, Alibaba specific open source technologies. They expect you to know it. Best way to study this interview is: 1) Study your tech stack. If it is Java for example, read a lot about how JVM works, threading works, GC works, memory model works etc. 2) Get the job description, read about all the frameworks. Especially if they list something you've not heard of it; or not too sure how it works. This is for back-end purposes. They don't seem to use RESTful APIs, insist using RPC frameworks. So do read up about the web frameworks' RPC support.
Questions about general C++ knowledge, then some about optimizations and how to tackle certain problems when you know nothing about the codebase, also they will ask you about your academic projects (or other profesional projects). Also general questions about yourself.
What are your biggest strength and weaknesses? What skills do you have? A lot of "team" questions as well
I yet to attend interview it's just the question given in the application form why you want to join fleet management? you strength and weakness etc.,?
Asked if i knew what I was doing, and some get to know you questions. Nothing bizarre or intense.
Standard questions, nothing really stood out to me.
Viewing 181 - 190 interview questions