Scribd
Upload
3 views2 pages

Java Developer - Screening Question

The document outlines a set of interview questions for a Java Developer with 3 years of experience, focusing on their technical skills, problem-solving abilities, and collaboration during releases. It covers topics such as experience with specific tech stacks, exception handling, data access optimization, incident management, performance checks, and analytical reasoning. Additionally, it provides a checklist for assessing candidates on various essential skills and practices.

Uploaded by

devender.yadav17dy
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views2 pages

Java Developer - Screening Question

The document outlines a set of interview questions for a Java Developer with 3 years of experience, focusing on their technical skills, problem-solving abilities, and collaboration during releases. It covers topics such as experience with specific tech stacks, exception handling, data access optimization, incident management, performance checks, and analytical reasoning. Additionally, it provides a checklist for assessing candidates on various essential skills and practices.

Uploaded by

devender.yadav17dy
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Java Developer (3 Years) —

Q1) Experience snapshot & stack (hands-on clarity)

“In the last 1–2 years, which modules or features did you work on regularly, and what tech stack did
you use day to day? Please mention Java version, Spring Boot version, build tool, and any
cloud/monitoring tools.”

Q2) Exception handling & logging hygiene

“How do you make sure users don’t see stack traces, while your team still gets enough details to
debug issues in production? Please give one example.”

 “Which tool alerts you if errors increase suddenly?”

Q3) Data access & speed — “last 50 orders” (no SQL; practical)
“Customers often open their last 50 orders. Without writing SQL, how will you keep this fast as data
grows?”

 “What would you index here to keep it fast?”

 “If it’s still slow, what’s your next step?”

Q4) Post-release incident — HTTP 500 with NullPointerException (stabilise first)

“Right after a release, 500 errors increase on one flow due to a NullPointerException. It worked on
your laptop. What are your first steps to keep users safe and fix it?”

 “What will you do immediately so customers are safe?”

 “How will you prevent this in future?”

Q5) Performance slowdown — Order List page feels slow (first checks)

“QA reports the Order List page is slow for some customers. In simple words, what will you check
first?”

 “If the query is the issue, what simple fix helps?”

 “If too much data is coming, what will you do first?”


Q6) MANDATORY — Analytical (work-rate, no maths tricks)

“Together, two developers fix 36 bugs in 6 hours. Dev A works twice as fast as Dev B. How many
bugs did A and B fix?”

 “What is their combined speed per hour?” → 6 bugs/hour.

 “If A is twice B, how do you split the 6 bugs/hour?” → Into 4 (A) and 2 (B).

Q7) Collaboration during release (QA + DevOps)


“How do you coordinate with QA and DevOps during a release? Just your normal steps.”

 “Do you share test data with QA?”

 “What do you monitor right after go-live?”

TA quick-ticks (printable checklist)

 Stack clarity: ☐ Java version ☐ Spring Boot version ☐ Maven/Gradle ☐


Jenkins/GitHub/GitLab CI ☐ Postman/Swagger ☐ CloudWatch/Grafana/ELK/Splunk

 Exceptions & logs: ☐ Central handler ☐ Clean error response ☐ Trace/Ref ID ☐ PII masked
☐ Alerts set up

 Data speed sense: ☐ Pagination 50 latest ☐ Small payload ☐ Index (customer+date) ☐


Archive/read-replica ☐ Before/after check

 Prod hygiene: ☐ Feature flag/rollback ☐ Same build repro ☐ Stack-trace line ☐ Config
difference ☐ Constructor injection ☐ Null-guard ☐ Unit test ☐ Hotfix via QA/UAT

 Performance basics: ☐ Avoid N+1 ☐ Index on filters ☐ Recent-change check ☐ Measured


improvement

 Analytical judgement: ☐ Users/revenue first ☐ Unblock team ☐ Delegate/renegotiate


demo ☐ Clear first actions ☐ ETA updates

 Release collaboration: ☐ QA test data ☐ Smoke tests ☐ Dashboards/alerts ☐ ETA/war-


room ☐ Post-release checks

You might also like