Which books you use to learn the technologies you worked on? Like which book for OAuth did you read?
Sr Java Developer Interview Questions
5,566 sr java developer interview questions shared by candidates
1st Technical Round : 1) What is Exception ? 2) What is your expectations ? 2nd Technical Round : 1) What are few features introduced by Java 8 ? 2) Why CLSA ? 3rd Round : 1) What is your project ? 2) What do you do for Agile Methodology ? 3) Have You resigned ? 4) I'll explain your role if you join MD : 1) Why do want so much money, less should be sufficient. 2) Why do you come for another interview if you already have offer in hand HR : He is worst in the world. He talks in local language with regional tone and bugs you like sometime police bugs when they want money. 1) What do you think of yourself, you are nothing, accept other lesser offer than you hold. 2) Why do you wear such dress etc. 3) Personal information, what your brother does, father does etc.
mostly on collections and threads
comparable interface
Design in high-level, the schematics (block diagram) for an HTTP RESTful web application that delivers the following functionality: Given a combination of first + last name of any celebrity will search multiple social networks and accumulate up to hundreds of responses (from various social networks) into a unified OR cumulative (at your discretion) response*. Initially, you may assume the system is required only to respond (within a reasonable time frame) to user bound requests, based on UI interactions exclusively. Be willing to defend your choices, debate pros/cons and offer alternatives for every off-the-shelf solution you may use in your design. * As long as the user is eventually presented with the sum of all responses in a sensible way, it's fine. Requirements: * Start off with a monolith and then gradually move away from it towards microservices. * Assume each social network always returns a result containing just a single entity. * Don't get hanged on the security aspects of this solution, for simplicity, ignore those. * Assume that each social network API is accessed using HTTP RESTful calls. * Design the system for high availability at the expense of consistency if a conflict between the two raises due to partitioning issues. Followups: ------------- 1. What changes would you introduce to effectively support machine to machine API invocations? 1.1 In what ways, the introduction of this requirement might affect the quality of service given your initial design? 1.2 What supporting mechanisms should be put in-place to maintain system high availability? 2. How would you handle rate limitations/delays/unavailability while calling social networks? 2.1 Depending on the inner workings of your initial design, suggest a strategy to maintain high availability and short response times (up to a given threshold) with minimal changes to the codebase. 3. Explain how you could avoid submitting duplicated/repeated requests for the same personas (yielding the same responses) from executing? 3.1 Debate on the potential gains vs challenges/issues involved in implementing (3)
2 scheduler application performing same job and updating same record at a time how to prevent that
Are you comfortable in mentoring
What new technology learned in past 6 months
What kind of java frameworks have you worked with?
How do you make an object immutable?
Viewing 791 - 800 interview questions