Due to the way the first project is specified you must have ONE project that you worked on that displays your skills in project planning and project delivery. This can be difficult to meet if your experience is distributed across multiple companies and projects, especially since this question was asked for a technical software engineering position.
problem solving based on the role and language
React native lifecycle Context API, Redux, Redux saga, JavaScript questions, react js questions
Knowledge in .NET
Wasn't familiar with term uml, but knew about the OOP relationships in the diagram.
They ask for Android developers but want people who are good at memorizing more than problem-solving skills.
A series of general technical questions unrelated to the job position
First interview questions: 1- tell me about yourself 2- talk about your experience in flutter 3- talk about your experience in deployement 4- do you have experience using Jira and Agile? 5- which version control did you used? 6-give me names of apps that you have build and deploy 7- did you work by yourself or with team? 8- what do you like in the company? 9-what are your salary expectations? 10- how soon can you start? 2nd interview: 1- what a mistake did you make, and what did you learn from ? 2- their core values are: Generosity, Respect, Innovation, and Teamwork. which one describe you the most? 3-How do you make sure you’re constantly improving your skills? 4- what are you hobbies 5- other personnel questions
Pt1) Given a list of object's Player(), randomly pick two players and return the one with the highest fppg (a variable of the object). Pt2) How would you do Unit Testing for the first function Pt3) Now return the function 5 times without comparing duplicates.
The technical questions covered a wide range of areas which I appreciated. The areas included object oriented design, architecture design, problem-solving/algorithms, objective-c (blocks, view controllers, etc.), and mobile specific questions. The most difficult question I was asked was to design a document upload/fetcher system for mobile (kinda like dropbox for the iphone). The difficulty was really in all the details of the problem (caching, database modeling, security, sessions, etc). Algorithm questions ranged from binary tree search questions to array pattern searching. The most unexpected question was the interviewer gave me a stream of digits and asked me to find the pattern. I got really stumped on this problem, it was my last interview of the day and I just blanked out. I guess I did well enough throughout the day because I got the job. By no means an easy interview, but not extremely hard, I was extremely well prepared as I had been interviewing for a while. Id say its on the average to difficult scale, if you are bad at architecting systems then this interview would have been HIGH diff.
Viewing 491 - 500 interview questions