Oci Interviews

I recently went through an intensive interview process for an IC3 role at OCI in the USA. The entire experience was structured across four distinct rounds, each designed to evaluate a different aspect of my software engineering capabilities. It felt quite comprehensive, covering everything from core algorithms to complex system architecture.

Round 1: Technical Coding (HackerRank)

This round was a HackerRank coding challenge focused on Greedy Algorithms and Heap data structures. The specific problem involved minimizing the total cost of an array of prices using a given number of tokens. It was a good test of my algorithmic problem-solving and optimization skills.

Round 2: Behavioral Interview

The second round was purely behavioral. It consisted of scenario-based questions, similar to Amazon's leadership principles interviews. The focus was on my past work experience, projects I've handled, and the decision-making processes I employ. I was asked to discuss situations where I demonstrated leadership principles.

Round 3: System Design

This round was a deep dive into system design. The core problem was to design a Distributed Rate Limiter. The discussion revolved around ensuring scalability, understanding distributed systems concepts, evaluating various trade-offs, and architectural thinking. We covered topics like load balancing, data consistency, and performance optimization.

Round 4: Advanced Coding

The final round was an advanced coding challenge. I was tasked with implementing an LFU (Least Frequently Used) Cache. This problem thoroughly tested my knowledge of data structures, cache replacement algorithms, and my ability to achieve optimal time and space complexity, particularly in balancing frequency tracking with efficient operations.

Key Observations

• Every single round, not just the dedicated behavioral one, included questions related to leadership principles, mirroring Amazon's interview style.
• The technical depth was significant, ranging from intricate algorithmic optimization to high-level system architecture, effectively testing both my coding prowess and my system-level thinking.
• The difficulty felt progressive, with each round building upon different technical skills: algorithms, then behavior, then systems, and finally advanced data structures.

Overall, the process was very well-structured and comprehensive, effectively evaluating both my technical expertise and my potential for leadership within a software engineering context. Each round clearly had a specific purpose in assessing different facets of my competency.

Hey community, I recently gave interview for Senior MTS position with OCI India. Got negative feedback, but still here are the questions that were asked.

Eliminator Round:- Check if words are anagrams. EASY. LRU Cache. MEDIUM Couple of behavioural questions. Some questions on concurrency.

Got call 2 days later that they will take my loop interview. My interviews were scheduled for 2 days. Daily 2 interview

Loop Interview 1: Group Anagrams from a list of strings. MEDIUM Maximum Subarray Print odd even using two threads concurrency problem. Some behavioural questions

Loop Interview 2: This was taken by someone from US. Rain water trapping problem. HARD Generate valid parenthesis (backtracking problem). MEDIUM Some behavioural questions. This was where I froze completely and could not communicate properly at all.

Loop Interview 3: This was with Hiring manager from India. He asked lots of technical questions from my resume. He also gave lots of system design situational based questions. I was asked to design CONFLUENCE.

Loop Interview 4: This was my bar tender/bar raiser round. Plenty of behavioural questions were asked.

Result: REJECTED.

I hope it helps the community in their prep. I applied through their web page. Good luck guys.

Thank you

Phone Screen

In this round, the interviewer presented me with a couple of medium-level LeetCode questions. I was able to provide optimal and workable code for both problems:

• A Dynamic Programming problem similar to Wildcard Matching.
• A question on finding the Least Common Ancestor.

I successfully cleared this round and was invited for four onsite rounds.

LLD with SMTS

This round focused on Low-Level Design for a management system. We discussed various aspects, including database schema choices, API endpoints, and class diagrams. I also encountered behavioral questions, particularly how I would handle conflicts within a team. Additionally, there was a deep dive into one of my past projects.

HM Round

The hiring manager round involved a deep dive into two of my past projects, where I was asked how I could have improved them. This round also included several behavioral questions.

Problem Solving Round with LMTS

This round featured a couple of hard-level LeetCode problems. I provided optimal approaches and wrote workable code for both:

• Text Justification
• Trapping Rain Water

There were also some behavioral questions in this round.

BarRaiser with LMTS

This round was entirely focused on behavioral questions, with a particular emphasis on my background and interests.

Overall, all my initial rounds went well. I appreciated that every interviewer was polite and had their camera on, which isn't always common in my experience.

About seven days later, the recruiter called to inform me about an additional round, which was scheduled within two days.

Round with CMTS

In this final round, I was asked to solve a couple of coding problems:

• Removing even-valued nodes from a given linked list.
• A string compressor problem.

Following the coding questions, I had a High-Level Design discussion about designing a TinyURL service with additional features. We extensively discussed various components and their alternatives.

The debrief happened three days later, and I was fortunate to receive an offer!