Technical screening questions
Ask for one example per question and listen for specifics.
- How do you tune a slow query? A good answer: Reads the explain plan, checks indexes and statistics and rewrites the query.
- When do you use a package instead of standalone procedures? A good answer: Grouping, encapsulation and reduced recompilation.
- How do you handle exceptions in PL/SQL? A good answer: Named exceptions, logging and re-raising.
- What are bulk collect and forall? A good answer: Reducing context switches for set-based processing.
- How have you supported an EBS customization? A good answer: Customization approach, patching and testing.
Quick screening questions
Use these when you have only a few minutes.
- How do you tune a slow query?
- EBS, Fusion or both?
- Describe a data migration you led.
What separates the levels
Match the level to the requirement before you submit.
- Junior: writes procedures and fixes defects.
- Mid: owns modules and tuning.
- Senior: designs data architecture and mentors.
Red flags
Any of these is a reason to probe further.
- Only basic SQL queries.
- No tuning experience.
- Cannot discuss transactions.
Tools you should hear mentioned
An Oracle developer with real experience usually names several of these without prompting.
- Oracle Database
- PL/SQL
- SQL Developer
- Oracle Forms or Reports
- EBS or Fusion
- Explain plans
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 Oracle 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.