Got the offerSMTS/SDE3 (Senior Member of Technical Staff) at Oracle
- Difficulty
- Process took
- 6+ Weeks
- Rounds
- 5
- Format
- Remote
- Applied via
- Company Website
How it went
- The whole process took me more than one month, and honestly, the waiting periods were the hardest part. But use that time wisely, after each round, I'd write down what went well and what I could improve.
- One thing that really helped me was treating each round as a learning experience, not just a test. That mindset made it easier to stay calm, and I could genuinely enjoy the process instead of stressing over it.
What they would tell you
- The whole process took me more than one month, and honestly, the waiting periods were the hardest part. But use that time wisely, after each round, I'd write down what went well and what I could improve.
- One thing that really helped me was treating each round as a learning experience, not just a test. That mindset made it easier to stay calm, and I could genuinely enjoy the process instead of stressing over it.
How to prepare
- Look, this is not your typical whiteboard coding session. Oracle gives you an actual online IDE and expects your code to run perfectly. I'd suggest practicing on different coding platforms, where you have to submit working code, not just write pseudocode.
- Dynamic programming is huge at Oracle, I got coin change, and I've heard others get knapsack variations and string manipulation problems. Don't just memorize solutions; understand the patterns.
Their background
I recently went through Oracle's interview process for the SMTS/SDE3 position and I'm happy to share that I got selected. The whole experience was quite a journey, and I know how valuable it can be to read about others' experiences when you're preparing for similar interviews. I'm currently a software engineer with 5 years of experience, and I've been working across different areas, from feature development to system design. I decided to document my entire interview experience here because I remember how much it helped me when I was preparing, reading through other people's experiences, understanding what to expect, and learning from their mistakes and successes. The tech interview process can be pretty stressful, and having some insight into what actually happens can make a huge difference.
Round by round
- 1
Technical Screening60 min
The screening round was conducted by a PMTS/Tech Lead who wasted no time getting to the core of my algorithmic thinking. What I appreciated most was the practical approach, not just theoretical knowledge. The interviewer provided an online compiler and expected fully functional code, which felt much more realistic than whiteboard coding. Questions: Two well-chosen problems that tested different aspects of my DSA knowledge, medium-level array manipulation problem that required careful consideration of edge cases and other priority queue problem that tested my understanding of heap operations and their practical applications. Both problems required not just correct solutions, but efficient ones that could handle the various test cases thrown at them. The interviewer was thorough in testing different scenarios.
- 2
Advanced Coding Challenge60 min
This round, led by an LMTS/SDE4, the interviewer had a keen eye for detail and wanted to see my thought process evolve from basic recursive solutions to optimized dynamic programming approaches. Coin Change Problem - Started with recursive approach, then optimized to DP. The interviewer was interested in seeing how I identified overlapping subproblems and built the optimal solution step by step. Minimum insertions to make string palindrome (modified version) - This was a tricky string manipulation problem that required understanding of longest common subsequence concepts and dynamic programming. The modification involved additional constraints that made the standard approach more complex.
- 3
System Design60 min
This was where things got really interesting. The interviewer first wanted to understand my recent project experience, then threw me into designing a distributed job scheduler - not exactly something I'd prepared for specifically, but the fundamentals I knew came in handy. Questions: Design a distributed job scheduler capable of handling high-throughput task processing. Started with basic architecture using Kafka for message queuing and appropriate database choices, then evolved the design as new requirements emerged. The interviewer was particularly interested in failure handling, scalability bottlenecks, and task prioritization mechanisms.
- 4
Technical Architecture Review60 min
This round with a director was intellectually demanding in the best possible way. Rather than giving me a new problem to solve, they wanted to understand how I approach real-world engineering decisions. The detailed exploration of my project's architecture, the justification for technology choices, and the discussion of alternative designs felt like a masterclass in system thinking. Questions: Comprehensive architectural review of my recent project including:
- Detailed explanation of system components and their interactions
- Justification for specific technology choices and trade-offs made
- Discussion of components designed by teammates and how they fit into the overall architecture
- Exploration of alternative design approaches and their implications
- 5
Leadership and Behavioral Assessment60 min
Two directors conducted this comprehensive behavioural interview, focusing on real-world leadership scenarios and professional growth. The questions were thoughtfully designed to understand not just what I've done, but how I think about challenges, conflicts, and team dynamics. Questions:
- What's your approach when you disagree with a technical decision made by someone more senior?
- How do you ensure code quality standards across your team?
- How do you prioritize technical debt versus new feature development?
- Tell me about a time when you had to deliver bad news to stakeholders
- What keeps you motivated in your day-to-day work?
- How do you handle design conflicts among multiple senior developers?
- Describe a situation where you had to learn a completely new technology under tight deadlines
- Share an experience where you mentored and led other developers
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.