Interview Experience - Oracle SMTS

oracle logo
oracle
MTS II3.1 years
April 20, 20255 reads

Summary

I interviewed for the Senior Member of Technical Staff (SMTS) role at Oracle with 3.10 YOE. The process involved a screening round with a coding test, three loop interviews covering DSA, System Design, and project deep dives, and I ultimately received an offer.

Full Experience

I recently interviewed for the SMTS (Senior Member of Technical Staff) role at Oracle. Here's a breakdown of the process:

📍 Screening Round
Duration: 1 Hour

Format: Online Coding Test (Peer Programming)
Questions was similar to this problem.

Content:

2 LeetCode Medium-level DSA problems

Focus was on problem-solving skills and optimal solutions

Standard topics like Graphs, HashMaps, and Two Pointers

🔁 Loop Interviews (3 Rounds)
Round 1: DSA-Focused Round
Duration: 1 Hour

Format: Live Coding

Content:

Solved 2 LeetCode Medium questions

Interviewer focused on writing clean code and explaining time/space complexities

Follow-ups involved optimizing initial approaches

Round 2: System Design + DSA
Duration: 1 Hour (45 min System Design + 15 min DSA)

Format: Virtual Whiteboard/Discussion

Content:

System Design: Design a healthcare system for doctors and patients

Covered components, data flow, entities, APIs, scalability, and data consistency

DSA: One short LeetCode-style problem (more of a warm-up to wrap up the round)

Round 3: Director Round (Tech Deep Dive)
Duration: 1 Hour

Content:

In-depth discussion on current/past projects

Walked through architecture decisions, design trade-offs, scalability, and tech stack choices

Questions like "Why did you choose this design?", "How would you improve it?", "What challenges did you face?"

Interview Questions (3)

Q1
Number of Islands (similar problem)
Data Structures & AlgorithmsMedium

The question in the screening round was similar to the 'Number of Islands' problem on LeetCode.

Q2
Design a Healthcare System
System Design

Design a healthcare system for doctors and patients. The discussion covered various components, data flow, entities, APIs, scalability, and data consistency.

Q3
Project Deep Dive and Design Decisions
Behavioral

An in-depth discussion on current/past projects, focusing on architecture decisions, design trade-offs, scalability, and technology stack choices. Questions included: "Why did you choose this design?", "How would you improve it?", and "What challenges did you face?"

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!