Full stack developer Interview Questions

1st answer. Copy all elements to an array and then get the index, index1 is x = x){ index1--; // fall back to first element with in current range }else if(array[index1] < x ){ // Too long. you get the idea. } } } if(index2 % 2 == 1){ if(array[index2] < y){ array[index2] = y; } }else if(index2 % 2 == 0){ if(array[index2] == y){ index2++; // point to second element with in the Range } } // Finally i remove the elements between index1 and index2, and reconstruct ranges and return new list of ranges.

Use binary search to bisect the array A into A_1, A_2 such that all ranges with starting time greater than or equal to x are in the new sub array A_2. Now repeat the process, this time bisecting A_2 into B_1, B_2, such that all ranges with ending time less than or equal to y are in B_1. Output is A_1 U {} U B_2 Runtime is O(log n)

Binary search

Spoke about my previous experience.

What your interviewer is really trying to do with this question—beyond identifying any major red flags—is to gauge your self-awareness and honesty. So, “I can't meet a deadline to save my life” is not an option—but neither is “Nothing! I'm perfect!” Strike a balance by thinking of something that you struggle with but that you’re working to improve. For example, maybe you’ve never been strong at public speaking, but you've recently volunteered to run meetings to help you be more comfortable when addressing a crowd.

This question seems forward (not to mention intimidating!), but if you're asked it, you're in luck: There's no better setup for you to sell yourself and your skills to the hiring manager. Your job here is to craft an answer that covers three things: that you can not only do the work, you can deliver great results; that you'll really fit in with the team and culture; and that you'd be a better hire than any of the other candidates.

I told them about a previous Django project.

Not tremendously! I tried to throw in as much technical detail as I could conjure regarding HTTP protocol, networking, http servers, wsgi servers, and the application itself, but the huge scope and general nature of the question made me uncertain of my answer, shook my confidence, and I forgot many details. After a bit, I was asked to focus only on the part after the request is received by Django. I immediately wished I spent less time in the docs, and more time in the framework's code. When I got home, that is the first thing I did. I think the key to answering this question is to be confident. You probably won't remember most of what you have encountered in the past and are actually familiar with, but you probably know way more than enough. Give yourself some credit. Try answering the question like a story and include sound effects.