Please Read the Referral Process till the End Before Contacting For Referral - CLICK HERE for Referral Process Information
INTERVIEW SLOT DETAILS
Candidate Name: Anonymous
Slot Time: 2025-07-24, 10:00 AM IST
Mode: Online
Role: Software Developer 2
Company: Oracle
Location: Bengaluru, Karnataka
Level: IC2 (0–2 years, early-career)
REAL INTERVIEW QUESTIONS ASKED – IC2 LEVEL (Oracle SD2)
TECHNICAL ROUND
Q1. Explain how you would design and deploy a cloud-native service on OCI. What factors would you consider during design?
Candidate Answer:
"I’d start with defining the service boundaries and designing it as a stateless microservice. For deployment on OCI, I’d use Oracle Kubernetes Engine or OCI Functions, depending on the use case. Key design factors would include scalability, observability (logs/metrics), fault tolerance, and how the service communicates with others — likely over gRPC or REST. I'd also enforce retries and circuit breakers."
Feedback: Great understanding of cloud-native principles, but needed more OCI-specific components (e.g., Autonomous DB, Oracle Service Mesh).
Skill Assessed: Cloud-native architecture, OCI familiarity
Mistakes to Avoid: Keep answers OCI-aware, not generic cloud terms.
Q2. Compare gRPC vs REST for service-to-service communication. When would you use each?
Candidate Answer:
"REST is simpler and more interoperable, great for public APIs. gRPC offers better performance and supports bi-directional streaming, ideal for internal service comms in microservices architecture."
Feedback: Nailed it. Could’ve added protobuf's role and language bindings.
Skill Assessed: Communication protocol tradeoffs
Mistakes to Avoid: Don't skip data serialization details.
Q3. You’re on-call. A service has spiked in memory usage and is crashing intermittently. Walk me through your triage process.
Candidate Answer:
"I'd first check alerts and logs to correlate patterns — maybe memory leaks or input volume spikes. Then isolate recent deploys or changes. I'd check JVM heap if it's a Java service, use tools like jmap or OCI Monitoring dashboards. If it's reproducible, I’d roll back and open an RCA doc."
Feedback: Strong ops mindset. Smart mention of JVM + rollback.
Skill Assessed: Production support, on-call triaging
Mistakes to Avoid: Never say “restart the server” as a first step.
Q4. Describe how you'd design alerting and KPIs for a newly built microservice.
Candidate Answer:
"I’d define KPIs like latency, throughput, error rate, and availability (SLIs). Then use OCI Monitoring to set thresholds for alerts. I’d follow RED or USE metrics for structured observability."
Feedback: Great. Could’ve added specific dashboarding tool or alert notification logic.
Skill Assessed: Observability & metrics
Mistakes to Avoid: Don’t mix up KPIs with logs.
Q5. Implement a producer-consumer pattern in Go or Java.
Candidate Answer:
(Uses Java with BlockingQueue to show multiple producer threads pushing messages and a single consumer thread polling them.)
Feedback: Efficient and idiomatic. Good use of built-in concurrency structures.
Skill Assessed: Concurrency, threading
Mistakes to Avoid: Avoid tight loops and busy-wait.
Q6. When designing distributed systems, how do you ensure reliability and consistency?
Candidate Answer:
"Use retries with backoff, idempotency keys for APIs, replication with quorum reads/writes, and eventually consistent models when needed. Logging and tracing help debug state divergence."
Feedback: Smart answer. Should’ve mentioned CAP theorem trade-offs explicitly.
Skill Assessed: Distributed systems
Mistakes to Avoid: Never assume consistency is default.
... (24+ technical questions continue: microservices lifecycle, lifecycle of requests, scripting automation with Python, deployment CI/CD flow, writing design docs, etc.)
BEHAVIORAL ROUND
Q25. Tell me about a time you had to debug a production issue under pressure.
Candidate Answer:
"There was a CPU spike in our API server. While others assumed infra failure, I checked application logs and found a loop caused by malformed user input. We hotfixed the parser and added a validation layer."
Feedback: Great initiative. Showed calm under pressure.
Skill Assessed: Problem solving, debugging
Mistakes to Avoid: Avoid “I panicked” narratives.
Q26. Describe a time you disagreed with your team on a technical decision. What did you do?
Candidate Answer:
"I once disagreed about using an in-memory cache vs Redis. I wrote a test benchmark and presented pros/cons with metrics. We ended up going with Redis but with an in-process cache fallback."
Feedback: Beautiful use of data to drive consensus.
Skill Assessed: Conflict resolution, data-driven decision-making
SITUATIONAL ROUND
Q29. Your service is getting timeout errors from another team’s microservice. What’s your course of action?
Candidate Answer:
"First, check if the issue is within our network boundary. Then collaborate with their team — sharing logs, correlation IDs, and impact metrics. Meanwhile, implement graceful degradation and fallback behavior."
Feedback: Shows collaboration and fault-tolerant thinking.
Skill Assessed: Cross-team debugging
Mistakes to Avoid: Blame game.
Q30. You’re given a legacy service to modernize for cloud. What’s your plan?
Candidate Answer:
"Understand dependencies and traffic patterns. Containerize the app, externalize configs, add health checks, break monolith into modules. Use feature flags for gradual rollout."
Feedback: Thoughtful approach. Missed DB migration details.
Skill Assessed: Migration strategy, cloud adoption
Mistakes to Avoid: Never say “just rewrite from scratch.”
HR ROUND
Q31. Are you comfortable going on-call? How do you balance it with work-life?
Candidate Answer:
"Yes, I’ve done on-call rotations. I ensure all alerts are actionable and downtime is minimized by good observability and testing. I maintain balance by blocking recovery time after incident-heavy days."
Feedback: Very mature answer.
Skill Assessed: Readiness, accountability
Q32. Why Oracle and this team?
Candidate Answer:
"I admire Oracle’s push into cloud-native infra and want to grow in distributed systems. The OCI team’s scale and problem space excite me."
Feedback: Personal + tech-aligned answer
Skill Assessed: Cultural fit, motivation
INTERVIEW SUMMARY
Technical Performance: 8.5/10
Communication Skills: 9/10
Confidence Level: Medium → High
Recommendation: Shortlist (Ready for next round or offer depending on bandwidth)
What the Candidate Missed:
-
OCI-specific architecture components (Object Storage, Oracle Functions, Service Connector Hub)
-
Slightly vague on real DB interaction patterns
-
More depth on design-doc writing