Skip to contentSkip to footer

Senior Java Developer Interviews

Salaries
Interviews

Senior Java Developer Interview Questions

"Senior developers have years of experience in Java and have the knowledge and communication skills to mentor other developers. Companies prioritize strong technical skills and questions will focus on problem solving and critical thinking. A bachelor's degree in computer science or a related field, along with years of industry experience are standard."

5,284 senior java developer interview questions shared by candidates

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)
avatar

Senior Java Developer

Interviewed at Cybereason

2.8★
May 18, 2023

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)

Viewing 751 - 760 interview questions

Glassdoor has 5,284 interview questions and reports from Senior java developer interviews. Prepare for your interview. Get hired. Love your job.