Technical screening questions
Ask for one example per question and listen for specifics.
- How do you handle a change request in the middle of a sprint? A good answer: Assess impact, talk to the product owner and re-plan; do not silently absorb it.
- How do you integrate with a system that has no API? A good answer: File exchange, database views or screen integration, with the risks stated.
- How do you find the cause of a production defect? A good answer: Reproduce, read logs, isolate the change and add a test.
- How do you design a database table for a new feature? A good answer: Keys, constraints, indexes and future queries.
- How do you hand over a feature to support? A good answer: Documentation, known issues and monitoring.
Quick screening questions
Use these when you have only a few minutes.
- What kind of business application did you build and who used it?
- How do you work with users who change requirements late?
- Describe an integration you built between two systems.
What separates the levels
Match the level to the requirement before you submit.
- Junior: fixes defects and small features.
- Mid: owns modules.
- Senior: leads design and integrations.
Red flags
Any of these is a reason to probe further.
- Cannot explain the application they built.
- No database knowledge.
- Has never supported production.
Tools you should hear mentioned
An Application developer with real experience usually names several of these without prompting.
- An IDE
- SQL tools
- REST and SOAP clients
- Git
- A build tool
- A ticketing system
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 an Application 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.