What's on your mind?

Bounce Daily Is Hiring Software Developer Interns!

Anonymous1 day ago

Job Details

  • Company: Bounce Daily

  • Role: Software Developer Intern

  • Opportunities: Internship and Software Development Engineer

  • Stipend: Competitive

  • Location: Not specified

  • Work Mode: Not specified

What They're Looking For

  • Interest in software development and engineering.

  • Relevant projects or products that demonstrate your development skills.

  • Ability to explain your technical contributions and work clearly.

  • Candidates open to internship opportunities.

Apply Here

https://docs.google.com/forms/d/e/1FAIpQLSepFOn-4YConc-wx-ginZXkMgMsoXta-YNqCPaX4moMfJ7jGA/viewform

Decentro SDE-1 Interview Experience | 3 YOE | Rejected

Anonymous1 day ago

Recently interviewed for the SDE-1 role at Decentro.
I have around 3 years of experience, and the interview process had three rounds. Sharing the questions I remember from each round.
Interview Rounds: 3

AI Interview

The first round was a call with an AI voice agent. It asked some basic questions about me and my work experience.

A few questions were:

  • Tell me about yourself.

  • What do you do at your current organisation?

  • Explain some of the projects mentioned in your resume.

This was my first AI interview, so I wasn't really sure what to expect. But it went pretty smoothly.


Basic Coding Round (HackerRank)

This round had five questions covering DSA, SQL, API implementation, and LLD.

DSA: First Non-Repeating Character

Given a string, find the first character that appears only once.

No.

Name

1.

Find Non-Repeating Characters in a String

Example:

  • Input: "swiss"

  • Output: "w"

I used a HashMap to store the frequency of each character and then traversed the string again to find the first character with a frequency of one.

SQL: Count Exams Taken by Each Student

Given Student and Exams tables, find how many times each student has appeared for an exam.

API Implementation: Restaurant Filtering

Given a restaurant API, find all restaurants in a particular city whose rating is above a given threshold. If multiple restaurants match, return the one with the lowest cost.

I used Python to implement this. We could choose any programming language.

LLD Questions

Both questions were basic and related to OOP concepts.

One question was about how to avoid code duplication when two subclasses have the same piece of code. I don't remember the exact wording of the other question, but both were quite easy.


Technical Interview (BarRaiser)

This round mainly focused on Python, SQL, and DSA.

Python

Started with a quick introduction, followed by questions about my experience with Python.

Some of the questions were:

  • Explain the four pillars of OOP.

  • What is a context manager in Python?

  • What is GIL (Global Interpreter Lock)?

  • A few questions around Python internals and software engineering basics.

There were a few more, but I don't remember all of them.

SQL & Database

Questions around database concepts included:

  • What are indexes and why do we use them?

  • What are the different types of indexes?

  • What is a Splay Tree?

  • What are the trade-offs of using indexes?

DSA: Combination Sum

This is where I got stuck.

The question was to find all unique combinations of numbers from an array that add up to a given target. Each number could be used multiple times.

No.

Name

1.

Combination Sum

I figured out that recursion and backtracking would be needed, but couldn't come up with the complete solution.


I couldn't clear the third round. The DSA question was where I struggled, even though the earlier discussions went reasonably well.

Anyway, back to preparation. Will keep learning and trying!

My Deloitte Offer

Anonymous1 day ago

Hi everyone,

I recently received an offer from Deloitte and wanted to share the details here to get some feedback from the community.

My Profile

  • Experience: 5 years (service based company)

  • Tech Stack: Java Backend

  • Current CTC: ₹13 LPA

Deloitte Offer

  • Fixed CTC: ₹21 LPA

  • Variable Pay: 10%

Is this a good offer for someone with 5 years of experience in Java Backend?

Apple Is Hiring Junior SDET Engineers in Bengaluru!

Anonymous1 day ago

Apple is looking for a Junior Software Development Engineer in Test to join its Sales Engineering team. The role focuses on software quality, test automation, API testing, and ensuring reliable applications across Apple's global sales and operations systems.

Job Details

  • Company: Apple

  • Role: Junior Software Development Engineer in Test

  • Location: Bengaluru, Karnataka

  • Experience: 1-2 years

  • Work Schedule: 40 hours/week

  • Job ID: 200694886-0321

  • Posted On: 20 November 2026

What You'll Work On

  • Create test strategies, plans, and test cases for applications and features.

  • Perform functional, system, integration, and exploratory testing.

  • Automate testing for web applications, mobile apps, and APIs.

  • Conduct performance and code quality testing.

  • Work with development and product teams to identify issues and perform root cause analysis.

  • Use GenAI models and AI-assisted automation to improve testing workflows.

  • Track testing progress and communicate results across project teams.

Required Skills

  • Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience.

  • 1-2 years of experience in SDET or Quality Engineering.

  • Experience creating test strategies and test cases for UI, APIs, web services, and database workflows.

  • Knowledge of functional, system, integration, and exploratory testing.

  • Exposure to automation, performance testing, and CI/CD integrations.

  • Programming experience with Java, JavaScript, or TypeScript.

Good to Have

  • Familiarity with GenAI solutions and AI models.

  • Experience identifying repetitive testing tasks that can be automated using AI.

  • Strong debugging, analytical, and problem-solving skills.

  • Ability to work in Agile teams and adapt to a fast-paced environment.

https://jobs.apple.com/en-us/details/200694886-0321/junior-software-development-engineer-in-test-sales-engineering?team=SFTWR

LinkedIn IC2 Apps Interview Experience

Anonymous1 day ago

Got an opportunity to interview for the IC2 Apps role at LinkedIn.

Sharing the questions and a few things I learned along the way.

Phone Screen Round

The round started with a discussion around my resume and previous projects.

Some of the questions were:

  • Explain some of the design decisions you made in your project.

  • Why did you choose Cassandra as the database?

  • Is there anything you would do differently if you were building the same system again?

DSA Questions:

  1. Sqrt(x)

  2. Maximum Subarray

Follow-up: How would you solve the Maximum Product Subarray problem?

No.

Name

1.

Maximum Product Subarray in an Array

I cleared this round and got shortlisted for the full interview loop.


Technical Coding Round

This round focused on DSA and problem-solving.

The questions asked were:

No.

Name

1.

Rotten Oranges

Maximum Subarray Sum After One Operation

No.

Name

1.

Maximum Subarray Sum After One Operation

Tip: Practise commonly asked LinkedIn-tagged coding questions. The top 50 questions are a good starting point.


AI Coding Round

This was a slightly different experience compared to a regular coding round.

The problem was related to finding first-level and second-level connections in a social media platform using a graph.

There were four parts to the problem, and each part had its own test cases that needed to pass.

A few things I would suggest:

  • Get familiar with the coding environment before the interview.

  • Practise AI-assisted coding questions, including those discussed on Hello Interview.

  • Don't blindly accept the AI's output. Verify the code and understand what it is doing.

  • Be clear about the approach and guide the AI instead of depending entirely on it.


Hiring Manager Round

We had an in-depth discussion about one of the most technically challenging and impactful projects I had worked on at my previous company.

I was asked to explain the project, the technical challenges involved, and the decisions I made.

HLD Question:

Design a Metrics Monitoring System.

The discussion focused on how I would approach the design and the decisions involved.


Technical Communication Round

This round was again centred around a project, but the discussion was much more detailed than the previous one.

I had to choose a project and explain it as if the interviewer were a new joinee joining my team.

The focus was on how clearly I could explain the architecture, components, workflows, and technical decisions to someone unfamiliar with the project.

Tip: Be prepared to explain the parts of your project that are one level above and one level below your own work. You should understand the bigger system as well as the implementation details.


System Design Round

The recruiter had asked me to prepare both HLD and LLD, but this turned out to be a pure HLD round.

Question: Design a Calendaring Website

The requirements were:

  • Users should be able to register and create calendar events.

  • Users should be able to invite others to events using their email addresses.

  • If an invitee is already registered, the system should show their free/busy information.

  • Users should be able to check the availability of all invitees before scheduling an event.

The interviewer discussed almost every design decision in detail.

Some of the discussions included:

  • Why choose AP over CP?

  • Exactly-once vs. at-least-once message delivery.

  • Trade-offs involved in the design.

Follow-up: What changes would you make if a user could create multiple calendars, such as Work, Personal, etc.?

Tip: Go through previous interview experiences and practise system design questions thoroughly. More importantly, be ready to explain the reasoning behind every major design decision.

Verdict: Selected

Hope this helps anyone preparing for the LinkedIn IC2 Apps interview. All the best!

How my Java Backend Interview Went

Anonymous1 day ago

Two technical rounds, a mix of DSA and backend concepts, and an on-site interview process.

Company: TripJack
Role: SDE-1 Java Backend
Experience: 2 Years
Education: B.Tech
Interview Mode: Face-to-face (On-site)
Total Rounds: 2

Round 1: DSA (60 Minutes)

The first round was conducted at the company's office. I was given two coding problems to solve using an online compiler.

1. Bellman-Ford Algorithm

Implement the Bellman-Ford algorithm to find the shortest paths from a source vertex in a weighted graph. The discussion focused on the approach and how the algorithm handles negative edge weights.

No.

Name

1.

Bellman ford algorithm

2. Search in Rotated Sorted Array - I

Given a rotated sorted array and a target element, find its index efficiently.

No.

Name

1.

Search in rotated sorted array-I

After solving both problems, I had to explain the logic, walk the interviewer through my code, and discuss the approach.

Round 2: Technical Interview

The second round covered my previous experience, Java backend fundamentals, low-level design, and Kafka.

Resume & Project Discussion

  • Walkthrough of my previous work experience.

  • Technologies used in my projects.

  • My role, responsibilities, and technical contributions.

Java & Spring Boot

  • What is the difference between a Load Balancer and an API Gateway?

  • Explain the Spring Bean lifecycle in Spring Boot.

Low-Level Design (LLD)

  • Discussion around fundamental LLD principles.

  • Questions on commonly used design patterns and their practical applications.

System Design & Kafka

  • How would you handle multiple events in Kafka?

  • Questions about Kafka internals and how Kafka works behind the scenes.

Final Outcome: Rejected

Unfortunately, I couldn't make it through the second round. Although the process didn't result in an offer, it was a useful experience covering DSA, Java fundamentals, Spring Boot, LLD, and Kafka.

Microsoft Interview Experience (3+ YOE)

Anonymous1 day ago

I recently appeared for the Microsoft interview process for a position requiring 3+ years of experience.

Sharing the questions and my experience from each round.

Round 1: Hiring Manager + System Design

The first round started with a discussion about my background and professional experience.

For around 50 minutes, the interviewer asked about:

  • My resume and previous projects.

  • My current responsibilities.

  • The technical decisions I had made in my projects.

  • My overall work experience.

After that, moved to a system design question, which lasted approximately 30 minutes.

I started with a basic design for a single client and gradually expanded it by discussing:

  • Load balancing.

  • Horizontal scaling.

  • Database sharding.

  • Handling increasing traffic.

The interviewer felt that my theoretical understanding was good but expected more practical depth and implementation-level clarity for the experience level required for the role.


Round 2: Object-Oriented Design (OOD)

This round had two parts and focused on designing and implementing an attack-path analysis system.

Part 1: Design an Attack Path System

Asked to design a system that could represent attack paths across different infrastructure components.

The main entities included:

  • Node: Contained an ID, name, and criticality.

  • VirtualMachine: Extended Node and included an internet-connectivity property.

  • Database: Extended Node and included a flag indicating whether it contained sensitive data.

  • Edge: Represented a connection between a source and target node, with its own criticality.

  • AttackPath: Contained a collection of nodes and edges along with an overall severity.

I discussed the class relationships, responsibilities, and how these entities would work together.

The interviewer mentioned that there wasn't one fixed or correct design and seemed satisfied with the approach.

Part 2: Implement the Attack Path Logic

Next, I was asked to implement a function that could validate and construct an attack path using the given nodes and edges.

I explained my proposed algorithm with an example and started implementing it. However, I couldn't complete the implementation within the available time.


Round 3: Data Structures & Algorithms

This was a 60-minute coding round with three questions.

Question 1: Maximum Consecutive Ones After K Flips

Given a binary array, find the maximum number of consecutive 1s possible by flipping at most K zeros.

Approach: I used the sliding window technique with two pointers. I expanded the window while keeping track of the number of zeros. Whenever the count exceeded K, I moved the left pointer until the window became valid again.

  • Time Complexity: O(n)

  • Space Complexity: O(1)

Question 2: Minimum Time to Burn a Binary Tree

Given a binary tree and a target node, find the minimum time required to burn the entire tree if the fire spreads to adjacent nodes every second.

Approach: I used BFS after first identifying the target node. Since the input nodes already had parent pointers, I could traverse in all three directions: left child, right child, and parent.

A visited set prevented revisiting nodes, and each BFS level represented one unit of time.

  • Time Complexity: O(n)

  • Space Complexity: O(n)

I completed the implementation, and the interviewer confirmed that the solution was correct.

Question 3: Message Filtering Within a K-Second Window

Given a list of messages with timestamps and a time window K, return a boolean array indicating whether each message should be accepted or suppressed.

A message should only be accepted if it hasn't been accepted within the previous K seconds.

Approach: I used a hash map to store the timestamp of the last accepted occurrence of each message.

For every incoming message:

  • If it hadn't appeared before, I accepted it.

  • If the difference between the current timestamp and its last accepted timestamp was at least K, I accepted it.

  • Otherwise, I suppressed it.

The important detail was to update the timestamp only when a message was accepted. If the requirement were to track every occurrence instead, the timestamp update logic would need to change.

  • Time Complexity: O(n) expected

  • Space Complexity: O(m), where m is the number of distinct messages.

I completed all three coding questions comfortably within the round.

Final Outcome: Rejected

Although I was able to solve all three DSA questions and received positive feedback on the OOD design discussion, I couldn't complete the implementation in the second round. The feedback from the first round also indicated that I needed more practical depth in system design.

Overall, it was a good learning experience.

Salesforce SMTS Offer

Anonymous1 day ago

Received an offer from Salesforce for the SMTS (Senior Member of Technical Staff) role with an overall CTC of approximately ₹75 LPA.

My Profile

  • Experience: 5 years

  • College: Tier 3

  • Current Role: Software Engineer

  • Current Company: Product-based MNC (Fintech)

  • Current Compensation: ₹25 LPA fixed + 10% variable + $10K stocks

  • Location: Bengaluru

Salesforce Offer

  • Role: SMTS

  • Location: Bengaluru

  • Fixed Compensation: ₹50 LPA

  • Target Variable: 15%

  • RSUs: $75,000 over 4 years (25% annual vesting)

  • Total CTC: Approximately ₹75 LPA, including annualized RSUs

Many artciles are missing fromA2Zsheet

BEAST_BHAVISHYA2 days ago

many of the articles are missing from the a2z shet which is making it difficult for me to revise the uqedtions i marked for teh revision adn the website form is a bit cluttery there areany features out there but of no use ...i wantthe articles if anyone know wheretehy are then please do lemme knowso athat i can continue my revsision

Help me I am struggling to convert logic into code in DSA

k4havv4 days ago

Can anyone please help me?

I am a beginner in DSA, nd I currently learning recursion I can understand the concepts and but I unable to write the code on my own without looking at the soln

I understand what needs to be done, but when I sit down to code, I get stuck and don't know how to proceed.

Has anyone faced this issue before? If so, how did you overcome it?

I really appreciate any advice or suggestions Thnk u

Transitioning from DBA to Data Science

panthaganisai1235 days ago

Hello Everyone,

I hope you're doing well.

My name is Saikiran Panthagani, and I have been working as a Database Administrator (DBA). Over the last six months, I have been actively trying to transition into the Data Science domain. I have been learning new concepts, improving my skills, and applying for relevant opportunities. However, despite my efforts, I have not been receiving interview calls.

To be honest, this has affected my confidence, and there are times when I feel demotivated and unsure about what I might be missing in my approach.

I would greatly appreciate guidance from professionals who have successfully made a similar transition or who are currently working in Data Science, Analytics, or AI-related roles.

Specifically, I would love advice on:

  • Skills that recruiters currently expect from aspiring Data Scientists
  • Certifications that add value to a profile
  • Portfolio projects that can attract interview calls
  • Resume improvements for career transition candidates
  • Networking and job search strategies

Coming from a database background, I have strong experience in SQL, database administration, troubleshooting, performance tuning, backup and recovery, and data management. I am eager to leverage this foundation and build a career in Data Science.

If anyone can share their experience, review my approach, or suggest a roadmap, I would be truly grateful.

Thank you for your time and support.

Seeking Guidance

iamabhay1 week ago

Hi everyone,

I’m a MERN Stack Developer with 4+ years of experience, but lately, I’ve been struggling to get interview calls despite being confident in my development skills. I know I can build things, understand complex requirements, and deliver solutions, but I feel like I’ve reached a point where I need a change.

I've been working at the same company for the past three years, and now I want to move to a good company where I can grow professionally, take on new challenges, and improve my skills.

However, looking at the current market expectations, I feel overwhelmed. It seems like I need to be strong in DSA, System Design, and Agentic AI to land a good opportunity.

The biggest challenge isn't necessarily learning these technologies; it's getting started. Every time I try to begin preparing, I start feeling underconfident, question my abilities, and eventually lose motivation.

I know I have the potential, but somewhere along the way, I've lost confidence in myself.

For those who have been through a similar phase or successfully made this transition:

  • How did you rebuild your confidence?
  • How should I prioritize DSA, System Design, and Agentic AI without getting overwhelmed?
  • What should my preparation strategy look like as a 4+ years experienced developer targeting good companies?
  • How do I stay consistent and motivated throughout the process?

I'd genuinely appreciate your advice, experiences, and guidance. I don't want to stay stuck in this phase anymore; I just need some direction to get started.

Seeking guidance regarding JOB application.

Yuvaan16931 week ago

Anyone with experience this post is in regards to learn a the way one's who are getting interview calls and getting hired for a person like me who is being unemployed for the last 6 months is seeking help from the community. **I'm from a reputed government college (IIIT Gwalior) but I still get rejections from everywhere. I have graduated in 2023 since then I worked at my first company for almost 2 years after that I were being unemployed for almost a year and picked a contract role for six months then I again became jobless for the next since months. It would be very helpful if someone could guide me in my current difficult times. If you can help all please share your guidance and contact me at below email address. if you have suitable roles that I could apply for I can dm my resume. Any help is welcomed (**Thank you in advance.) email: yuvaansingh100@gmail.com

Github account suspension

fara_281 week ago

My github account got suspended how to recover Iam a student I had many repositories and I also did contributions I was preparing for GSOC since july and contributing and this happened suddenly how to get my account back .. I would be great If anyone could help me out

A weekly review that keeps prep honest

xingqpa21 week ago

Preparation has a way of feeling productive while quietly going nowhere. You read a chapter, watch an explanation, skim three solutions, and at the end of the week you have a pleasant sense of effort and very little you could reproduce under pressure.

The thing that fixed this for me was a short review at the end of every week. Twenty minutes, same three columns, no tooling.

The first column is what I can now do without help. The bar is deliberately high: I have to be able to start from an empty file and get to a working answer while explaining the reasoning. If I need to peek, it does not go in this column. Most weeks this column is shorter than it feels like it should be, and that gap is the entire point of the exercise.

The second column is what I touched but cannot reproduce. This is where most of the week’s reading ends up. It is not wasted, but calling it learned is how you end up surprised in an interview. Items here either get scheduled for real practice or get dropped on purpose.

The third column is what got in the way. Interruptions, a topic that turned out to need a prerequisite I did not have, an evening lost to a tool that did not work. Writing this down stopped me from making the same plan again the following week and expecting a different result.

Two small rules keep it from decaying. I write it at a fixed time, because a review that waits for a good moment never happens. And I keep the previous week visible while writing the new one, which makes drift obvious: when the same item sits in the middle column for three weeks running, the honest move is to either start it properly or admit it is not a priority right now.

What surprised me was how much this changed planning rather than studying. Knowing that the first column has to be filled with things I can actually do makes me choose fewer topics and go deeper on them, which is what I would have claimed to be doing anyway.

Packet Capture Tool Comparison: Charles, Fiddler, TraceEagle, Wireshark, and Proxyman

xqpat1 week ago

Packet capture is one of the most common techniques developers use in daily debugging. There are many tools on the market, but each has a distinct positioning and applicable scenario, so choosing the right one can save a lot of time.

Charles: The Most Widely Used Proxy Packet Capture Tool

Charles has the largest user base for HTTP/HTTPS packet capture. Its advantage lies in its low learning curve—after installing it on a Mac, configuring the proxy on your phone, and installing the certificate, you can see the request list within minutes. It supports Breakpoint interception to modify requests, Repeat for replaying requests, and Map Local/Remote for request mapping. Once SSL Proxying is configured with the target domains, HTTPS traffic can also be decrypted.

Charles's limitations appear mainly in several scenarios: with SSL Pinning, proxy certificates are rejected by the client, leaving only handshake failure records; traffic from apps that ignore the system proxy is not captured; HTTP/3 and QUIC support is insufficient; and the certificate configuration flow on Windows is more complex than on Mac.

Fiddler: The Main Packet Capture Tool in the Windows Ecosystem

Fiddler is widely used on Windows. Its core strength is FiddlerScript—writing scripts in C# to customize request and response handling, which suits automated testing scenarios. It supports breakpoint debugging and request construction. A built-in performance analysis panel shows request latency and bandwidth usage.

Fiddler's shortcomings are also obvious: on macOS only a limited-feature Beta version exists, and Windows remains the primary platform; HTTPS decryption requires manually configuring certificates, with more steps than Charles; the interface feels dated, and filtering is less convenient when handling large volumes of data.

TraceEagle: Covers More Edge Cases

TraceEagle takes a different approach from the tools mentioned above. It builds on proxy-based capture and fills the blind spots of other tools: apps that ignore the system proxy can be captured directly from the network interface or via in-app stream extraction; in SSL Pinning scenarios, there is no need to swap certificates in the middle—plaintext can be obtained directly from inside the app; HTTP/3 and QUIC are handled via three modes: downgrade capture, fidelity transparent passthrough, and actual decryption.

The workflow after packets are captured is also more complete—you can set breakpoints and modify requests in the same interface, right-click to run load tests and view p99 tail latency, compare differences line by line, and reverse-engineer OpenAPI documents. It supports packet capture on iOS without jailbreak and on Android without installing certificates, and runs on Windows, macOS, and Linux.

Wireshark: The Most Comprehensive Protocol Analyzer

Wireshark is unrivaled in the depth of protocol analysis, supporting parsing of thousands of protocols. Its filter expressions are powerful, allowing you to combine source IP, port, protocol, and other conditions to locate specific traffic. It is the standard tool for troubleshooting TCP retransmissions and TLS handshake details.

To capture iOS mobile traffic with Wireshark, you need to use the rvictl command on a Mac to create a virtual interface; it cannot be used directly on Windows. Moreover, Wireshark does not handle HTTPS decryption—you must export keys separately. For everyday API debugging, Wireshark's operational workflow is longer than that of proxy-based tools.

Proxyman: A Modern Choice on macOS

Proxyman is a packet capture tool that has become popular on macOS in recent years. Its interface is more modern than Charles and Fiddler, and the visual configuration for request filtering rules is more intuitive. It supports grouping by domain, advanced search, and script extensions. In SSL Pinning scenarios, it can be solved by installing a root certificate together with iOS's SSL Kill Switch.

Proxyman's limitation is that it supports macOS only, so Windows users cannot use it. HTTP/3 support is also limited. Its deep analysis capability and script flexibility are not as strong as Fiddler's.

Selection Recommendations

For simple HTTP API debugging in daily work, Charles or Proxyman is sufficient. In Windows environments where scripting capability is required, choose Fiddler. For deep dives into the TCP protocol layer, Wireshark is a must. When encountering edge cases such as certificate pinning, HTTP/3, or proprietary protocols in a project, adding TraceEagle to your toolchain fills in the blind spots.

Infosys Specialist Programmer (SP) L1 – On-Campus Interview Experience

ayushdwivedi_1 week ago

Interview Experience | On-Campus Placement

My Infosys Specialist Programmer L1 interview was focused on DSA, problem-solving, OOPs, RAG (Retrieval-Augmented Generation), and SQL.

1. DSA and Coding Round

The interview started with DSA questions. The interviewer asked me to open LeetCode and solve coding problems.

  • Around 4 coding questions were given.
  • The questions covered general DSA concepts.
  • I was expected to explain my approach, logic, and time and space complexity.
  • The interviewer focused on problem-solving ability and code optimization.

2. Wingspan / Coding Assessment

There was also a 30-minute coding segment involving a greedy-based problem.

  • A greedy algorithm problem was asked.
  • I had to identify the optimal approach and explain the reasoning.
  • Time management and efficient implementation were important.

3. OOPs

After the coding discussion, the interviewer asked a few OOPs questions, covering fundamental object-oriented programming concepts.

Important topics to prepare:

  • Four pillars of OOPs.
  • Inheritance and polymorphism.
  • Function overloading vs overriding.
  • Abstraction vs encapsulation.
  • Virtual functions and runtime polymorphism.

4. RAG (Retrieval-Augmented Generation)

The interviewer also asked about RAG, an important concept in Generative AI.

Topics to prepare:

  • What is RAG?
  • Why is RAG used?
  • How does a RAG pipeline work?
  • Embeddings and vector databases.
  • Retrieval vs generation.
  • RAG vs fine-tuning.

5. SQL

The interview also included SQL-related questions.

Important topics:

  • Joins (INNER, LEFT, RIGHT).
  • GROUP BY and HAVING.
  • Aggregate functions.
  • Subqueries.
  • Primary key and foreign key.
  • Second-highest salary query.
  • DELETE vs TRUNCATE vs DROP.

Overall Experience

The interview covered multiple areas, with a strong emphasis on DSA and coding, followed by OOPs, RAG, and SQL.

My preparation advice: Focus on LeetCode problem-solving, greedy algorithms, core OOPs concepts, SQL queries, and basic Generative AI concepts, especially RAG.

_Note: This experience has been reconstructed from my recollection of the interview. The exact coding questions and individual OOPs/SQL questions are not specified._

Cohesity MTS-3 Interview Experience

Anonymous2 weeks ago

There were 3 rounds in total, each scheduled for 60 minutes.

Round 1: DSA + Resume Discussion (60 min)

  • Two standard DSA questions were asked.

  • Both questions were based on commonly practised patterns from Striver's SDE Sheet.

  • Topics covered:

    • Two Pointers (Max Consecutive Ones III)

    • Graphs (a problem similar to Connected Components)

  • We also discussed my previous projects and the experience mentioned in my resume.

Interviewer feedback: Towards the end of the round, the interviewer personally mentioned that I had done well and wished me all the best for the next round.

Round 2: System Design - HLD (60 min)

  • This round was entirely focused on High-Level Design.

  • The recruiter had informed me beforehand that LLD might also be covered, but that wasn't the case during my interview.

  • Question: Design an Order Management System.

Interviewer feedback: Similar to the first round, the interviewer mentioned that I had done well and wished me luck for the next round.

Round 3: Hiring Manager (HM) Round (60 min)

The first 30 minutes were mainly focused on my current project and previous experience.

Questions included:

  1. Explain your current project and the work you have been doing.

  2. Why are you planning to leave your current company?

  3. What are your compensation expectations?

  4. Why didn't you accept the offer from the other Cohesity team?

The discussion was quite straightforward and transparent.

One interesting observation: Based on how the conversation went, I personally felt that the HM had already made up his mind about selecting me even before the interview started. It felt more like a discussion to understand my background, expectations and motivation rather than another technical evaluation.

At the end of the conversation, the HM explicitly informed me that I had been selected for this particular role.

Selected

Received an email from the recruiter within 2 days.

Agoda | SDE-2 (SSE)

Anonymous2 weeks ago

Status: B.Tech, 4 YOE, Backend
Position: Senior Software Engineer (SDE-2) at Agoda
Verdict: Selected

Round 0: Recruiter Screening (30 min)

  • Intro, current role, tech stack, notice period, expectations

  • Why Agoda? Why Bangkok?

Round 1: DSA (60 min)

Full working code was required, and it was tested against their own test cases.

Q1: Reverse the words in a string ("I love coding" => "coding love I")

Q2: Trapping Rain Water

Prep: Striver's DSA course and practice sheets, along with easy and medium-level coding problems.

Round 2: Coding with OOP/LLD (60 min, Java)

Q1: Design an ATM System (cash withdrawal, deposits, balance inquiry, transaction history, and account validation).

Round 3: System Design / HLD (60 min)

Q1: Design a Food Delivery Platform (restaurant discovery, order placement, delivery partner assignment, and real-time order tracking).

Prep: System design books.

Round 4: Architecture / Platform Design (60 min)

Q1: Design WhatsApp.

Prep: Same HLD book as above.

Round 5: Hiring Manager / Cultural Fit (60 min)

  • Deep dive into my current project and architecture

  • Situational and behavioural questions (conflict, ownership, deadlines, mentoring)

  • Python and GenAI concepts

  • Why Agoda? Why switch? Why Bangkok?

"Why Should We Hire You?" No, "Why Are You Leaving?"

Anonymous2 weeks ago

One question that almost always comes up when you're interviewing for a new job is, "Why are you looking to switch?"

At first, it might seem like a simple question, but I've seen candidates struggle with it because they aren't sure how much they should reveal.

Should you talk about salary? Are you unhappy with your current manager? Do you want better opportunities? Or should you simply say that you're looking for career growth?

I think the biggest mistake candidates make is either being too honest in the wrong way or giving an answer that sounds rehearsed and generic.

The interviewer isn't necessarily expecting you to have a perfect reason for leaving. They want to understand your motivation, career goals, and whether you're genuinely interested in the new opportunity.

Here are a few things I'd keep in mind while answering this question.

Keep Your Answer Positive

Even if you're unhappy with your current company, avoid making negative comments about your manager, teammates, or organization.

For example, instead of saying:

"I'm switching because my manager doesn't appreciate my work and there is no good work environment."

You could say:

"I'm grateful for what I've learned in my current role, but I'm now looking for an opportunity where I can take on more challenging responsibilities and continue growing as an engineer."

The idea is to focus on what you're moving towards rather than what you're trying to escape.


Be Clear About Your Reason

Before attending an interview, I'd suggest being clear about why you actually want to switch.

Some common reasons include:

  • Career Growth: You feel you've reached a point where you're ready for more responsibility and challenging work.

  • Better Technical Exposure: You want to work with larger systems, new technologies, or more complex engineering problems.

  • Learning Opportunities: You want to work with experienced engineers and learn better development practices.

  • Role Change: You're looking for responsibilities that align more closely with your long-term career goals.

  • Limited Opportunities: Your current role doesn't offer enough opportunities to explore new challenges.

Choose the reason that genuinely reflects your situation instead of picking an answer just because it sounds impressive.


If Salary Is Your Main Reason

Let's be honest. Compensation is also a valid reason to explore new opportunities.

However, I'd avoid making salary the only focus of your answer.

Instead of saying:

"I'm switching because I want a higher package."

You can say:

"I'm looking for a role that offers better alignment with my experience, responsibilities, and market expectations. Compensation is certainly a consideration, but I'm also looking for opportunities where I can contribute and grow professionally."

This communicates your expectations without making the conversation entirely about money.


If You Don't Have Enough Learning Opportunities

Sometimes, you might feel that your current role has become repetitive and you're no longer getting opportunities to work on challenging problems.

In that situation, you could say:

"I've learned a lot in my current organization, but over time, my responsibilities have become more predictable. I'm now looking for opportunities where I can work on more challenging problems, take greater ownership, and improve my technical skills."

This shows that you're thinking about your long-term growth.


If You're Switching Because of Company Culture

If the work environment or management style isn't suitable for you, be careful about how you explain it.

Avoid directly criticizing your current organization.

Instead, focus on the kind of environment where you believe you can perform better.

For example:

"I'm looking for a collaborative engineering environment where I can exchange ideas, take ownership of projects, and work with people who encourage continuous learning."


Avoid These Common Mistakes

A few things I'd personally avoid while answering this question:

  • Don't complain about your current manager or teammates.

  • Don't make your current company look bad.

  • Don't give a completely memorized answer.

  • Don't make unrealistic claims about the new company.

  • Don't focus only on salary unless specifically asked about compensation.

  • Don't give a very long explanation when a simple answer is enough.