Technical screening questions
Ask for one example per question and listen for specifics.
- What are governor limits and how have you worked within them? A good answer: Names limits such as SOQL queries per transaction and describes bulkification.
- When do you use Flow instead of Apex? A good answer: Declarative first for simple automation; Apex for complex logic, performance or callouts.
- How do you deploy changes between environments? A good answer: Change sets, Salesforce CLI or a CI pipeline, with test coverage requirements.
- How do you secure data in Salesforce? A good answer: Profiles, permission sets, sharing rules and field-level security.
- Describe an integration you built. A good answer: Callouts, named credentials, error handling and retry.
Quick screening questions
Use these when you have only a few minutes.
- Which Salesforce certifications do you hold?
- How do you handle governor limits in bulk operations?
- Describe an integration you built.
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds components and triggers with guidance.
- Mid: owns features and integrations.
- Senior: designs the org architecture and mentors developers.
Red flags
Any of these is a reason to probe further.
- Only configuration work presented as development.
- Cannot explain bulkification.
- No exposure to deployment tooling.
Tools you should hear mentioned
A Salesforce developer with real experience usually names several of these without prompting.
- Apex
- Lightning Web Components
- SOQL and SOSL
- Salesforce CLI and DX
- Git
- Platform Events or MuleSoft
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 Salesforce 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.