Q2) The is a binary tree, which has string values only on leaf nodes and all other nodes have empty values. Example is below. When you sum all the leaf node values from left to right. the values will be : example: abcdefghblahblahblahblah etc. Implement the below method that will give 'n'th character of the result. Example: find the 5th character. here it will be 'e'. (BLANK) |---------------------------^---------------------------| (BLANK) (BLANK) |-------------^-------------| |-------------^-------------| abc (BLANK) ijklmnopq rstuvwxyz |------| defgh // Strucutre of the Node with below implemented methods. class Node { Node getLeft(); Node getRight(); boolean isBlank(); String getData(); }

Q3) How would you design and make use of React and Redux when there is a multiform submission. Ex: User Info form, Features form, Additional Details form Conditions: 1) At any given point of time the user filled data should be saved. and when user moves back and forth the data needs to be available. Improvisation: 2) At any given point if the user moves from desktop to mobile. He should be able to access the half-filled data. Ex. the user has filled 1st form(user info form) and then half of the features form, then the user should see the same in the mobile browser. 3) if the "Features form" is a big one and it is difficult to scroll in mobile. The UI Designer wants to split that into further three pages. Then how would you write the code? Would you write different components for "Feature form" for both mobile and desktop? If yes, then any change made in the future will result in editing both places. How to write single component with different runtime behavior?

Q4) Server (avg response 500ms) <---> Security Gateway (timeout is 100ms) <---> Client (React UI) This is a setup where the average server response time is 500ms, but the organization's security gateway is 200ms. You can't change the security gateway. And also you can't greatly scale the server.. (ex by adding more machines and loadbalancing them, introducing caches like Redis for faster lookup etc to reduce the response time from 500ms). So the avg response time 500ms is fixed. You have only control over the client and server. And can make small changes.

Q5) If you are designing a Google search like application. And you need to send the search api request only when the keypress interval between two keypresses is more than 2s.