Backend Developer (Java/SQL) interview questions
Common interview questions and sample answers for Backend Developer (Java/SQL) roles in IT & Technology across Oman and the GCC.
The 10 questions below are compiled from interviews our consultants have run with IT & Technology employers across Oman and the wider GCC. Each comes with a sample answer and what the interviewer is really listening for.
Category
Opening & warm-up
How interviewers test your communication and preparation right from the start.
Walk me through your backend developer career.
I've been a backend developer for seven years, three in Oman. Started in Java EE at an Indian banking IT vendor, transitioned to Spring Boot microservices over time, and for the past three years I've been senior backend developer at an Omani fintech. Stack: Java 17, Spring Boot, PostgreSQL/Oracle, Kafka, Redis, deployed on Kubernetes. I work on payment processing services with stringent performance and reliability requirements. SCJP and Spring certifications.
Specific backend depth.
Category
Behavioural (STAR)
Past-experience questions. Use the STAR framework: Situation, Task, Action, Result.
Tell me about a complex service you built.
Last year I built our domestic payments service: handles RTGS, ACH, and internal transfers with proper idempotency, retry logic, and reconciliation. About 500K transactions per day at peak. Architecture: event-driven with Kafka, REST API for client interaction, strict transactional boundaries, comprehensive observability. Service has been in production six months with 99.97% availability. Payment services demand both performance and reliability; getting either wrong is unacceptable.
Real backend delivery.
Describe a performance issue you solved.
One of our services was hitting database connection pool exhaustion under load. Investigation showed query patterns creating long-held connections during reconciliation runs. Refactored: query optimisation to reduce hold time, connection pool sizing tuned, async patterns for non-transactional operations. Pool exhaustion eliminated. Performance work requires patience; jumping to solutions without diagnosis usually doesn't fix the right thing.
Performance engineering.
Tell me about a code review situation.
I reviewed a colleague's PR with concerns: she'd implemented a workaround for what I thought was a real issue. I provided specific feedback in the review with the underlying issue explained. She disagreed initially. We discussed in person to align views: turned out my concern was valid but her workaround was acceptable as a tactical fix while we addressed the root cause separately. Code review serves the codebase, not ego; the goal is good code, not winning.
Collaborative code review.
Category
Technical & role-specific
Questions that test your specific skills for this role.
Walk me through your service design.
Bounded context aligned with business capability. REST API as primary interface (with OpenAPI spec). Internal architecture: controller, service, repository layers. Domain model rich, not anaemic. Transactions tightly scoped. Async processing for non-blocking operations via Kafka. Database design: normalised, proper indexing, query optimisation. Resilience: circuit breakers, retries, bulkheading. Observability: distributed tracing, structured logging, metrics. Service design discipline determines what's maintainable five years out.
Real service design depth.
How do you handle database design for high throughput?
Schema normalised but with practical denormalisation where read patterns justify. Indexes designed per query patterns; over-indexing hurts writes. Partitioning for large tables: by date for time-series, by tenant for multi-tenant. Connection pooling configured to load characteristics. Read replicas for read-heavy patterns. Query plans reviewed for unexpected scans. Stored procedures avoided for testability except where genuinely beneficial. Database design for throughput is craft, not formula.
Real DB depth.
Describe your testing approach.
Pyramid. Unit tests on business logic, high coverage. Integration tests for components touching infrastructure. Contract tests for service boundaries. End-to-end tests for critical user flows, kept lean. CI runs all on every PR. Test data management automated. Mocking only at the right boundary; over-mocking creates tests that pass when code is broken. Test quality determines refactoring confidence; without quality tests, code calcifies.
Test discipline.
Category
Situational
Hypothetical scenarios designed to test your judgement and approach.
A production incident is being blamed on your service. How do you respond?
Engage the diagnosis without defensiveness. Look at logs, metrics, traces objectively. If my service is the cause, own it and lead the fix. If it's not, articulate the evidence calmly. If unclear, work the investigation collaboratively. Incidents are learning opportunities, not blame opportunities; the team that handles them objectively improves faster than the team that argues.
Mature incident posture.
Category
Cultural fit & motivation
Why this role, why this company, and how you work with others.
How do you work with the team?
Direct communication, respectful tone. I share knowledge proactively; team value increases when knowledge spreads. I'm patient with juniors; my seniority means investment in their growth, not impatience with their learning curve. I push back constructively when I disagree but commit fully once decision is made. The work environment matters more than narrow technical wins.
Team collaboration.
Category
Closing
The final stretch. Often where deals are won or lost.
What are your salary expectations?
For a senior backend developer role at an Omani fintech I'd target OMR 1,800 to 2,400 total package depending on platform scope and engineering culture. Fintech with significant tech stack and engineering rigor pays a premium. I'd value training and certification budget. I'm on 60 days' notice. Beyond pay I'd value the engineering culture; teams that respect craft produce different careers than teams treating engineering as a cost centre.
Researched range and culture preference.
Practise these with AI
Get 5 fresh questions tailored to Backend Developer (Java/SQL), type your answers, and get per-answer feedback from AI. Free, 10 minutes.
Start AI mock interview