Technical screening questions
Ask for one example per question and listen for specifics.
- How do you secure the API for a single-page app? A good answer: Tokens, CORS and authorization.
- How do you handle API errors in the UI? A good answer: Central handling and user feedback.
- How do you avoid N+1 queries? A good answer: Fetch strategy and batching.
- How do you structure the front end? A good answer: Components, state and services.
- How do you test across layers? A good answer: Unit, integration and end-to-end tests.
Quick screening questions
Use these when you have only a few minutes.
- Walk me through a feature from the database to the UI.
- How do you secure a Spring Boot API used by a single-page app?
- How do you handle state and API errors in the front end?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds screens and endpoints.
- Mid: delivers features end to end.
- Senior: designs the system.
Red flags
Any of these is a reason to probe further.
- Strong on one side only.
- No tests.
- Cannot discuss security.
Tools you should hear mentioned
A Java full stack developer with real experience usually names several of these without prompting.
- Java and Spring Boot
- Angular or React
- REST APIs
- SQL
- Maven or Gradle
- Git
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a Java full stack developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.