Senior Java Developer

Description

Auto-generated position for Senior Java Developer

Interview Questions (30)

Q1Can you describe a challenging technical problem you encountered in a Java project and how you resolved it?
Experience
Q2Can you describe a challenging Java project you led and the architectural decisions you made to overcome those challenges?
Experience
Q3List three Collections interfaces and the basic contract of each. List concrete implementations of each, how they differ, and performance characteristics in space and time.
Technical
Q4Describe the contract of equals and hashCode. Why is it important that if you implement one, that you implement both?
Technical
Q5What is a deadlock? How can you prevent it?
Technical
Q6What is a race condition and how do you avoid it?
Technical
Q7What are the different statement types and why would you use each?
Technical
Q8How do you prevent SQL injection attacks?
Technical
Q9What are transactions?
Technical
Q10Give an overview of Hibernate and ORM. How do you load objects into the session? What does the session do with the objects while in the session? What is the difference between getting a persistent object from the session and querying for persistent objects?
Technical
Q11When is it better to use plain SQL instead of ORM?
Technical
Q12What are some ways for the client to obtain a reference to the DataSource from the app server?
Technical
Q13What is the difference between SOAP-based web services and REST-based web services?
Technical
Q14Describe SOAP and WSDL.
Technical
Q15What exactly is REST? What is the purpose of each of the HTTP verbs? What is idempotence? What is content-negotiation?
Technical
Q16What is decoupling? Why are loosely-coupled classes desirable? What are some drawbacks?
Technical
Q17What is cohesion? Why are highly cohesive classes desirable? What are some drawbacks?
Technical
Q18Describe polymorphism. What is the importance of contracts between interfaces and concrete types? Why is polymorphic code desirable? What are some drawbacks?
Technical
Q19Pick a Java service you have actually worked on and tell me one architecture decision you would make differently now.
Experience
Q20You inherit a Spring Boot codebase where one service class is three thousand lines and half the app depends on it. How do you decide what to pull apart first, and what to leave alone?
Situational
Q21When would you not reach for microservices, or not add another layer of abstraction?
Situational
Q22A service’s average response time looks fine, but a few times an hour it spikes badly. How do you figure out what is going on?
Situational
Q23A feature request lands as one vague sentence from the CEO. What do you do before you write any code?
Situational
Q24Design a nightly job that processes millions of records without falling over or grinding the database to a halt. Talk me through it.
Situational
Q25Your service runs fine for a week, then memory creeps up until it throws an OutOfMemoryError. Walk me through how you would find the leak.
Situational
Q26Under load, requests start timing out, but CPU usage is low. What is your first hypothesis?
Situational
Q27After a deploy, latency jumps, but only on some instances. Walk me through your investigation.
Situational
Q28You own an API that three other teams build on. You need to change it. How do you do that without breaking them?
Situational
Q29Your new service does everything the old one did, but the teams that call it say it is harder to work with. Why does that happen, and what would you do about it?
Situational
Q30How has AI changed the way you write Java day to day, and where do you not trust it?
Motivational