Rejected | Salesforce AMTS Interview Experience (End-to-End)

I appeared for the AMTS role at Salesforce.

I applied through the portal after seeing the job posting on LinkedIn. After a few days, I received the Online Assessment (OA). The questions were mainly focused on Graphs and Dynamic Programming.

The OA difficulty was medium-hard, and due to the time limit, you need to be familiar with LeetCode Hard problems, especially in Graphs.

After that, I received a mail stating that my interview was scheduled exactly one week later.

Resume

My resume consisted of experience from two companies. I previously worked as an SDE Intern at an MNC during my 7th semester, and currently I am working at a startup which I joined in April 2026.

For projects, I had one Full Stack + Multi AI Agent project focused on autonomous event scheduling, conflict detection, and resolution. Another project was a Full Stack Movie Ticket Booking application. Apart from that, I also had one Open Source contribution mentioned in my resume.

First Technical Round

The interview started with a basic introduction where the interviewer first introduced themselves and shared their experience.

After that, I introduced myself in a present-past-future format.

• Currently working at a startup that I joined last month.
• Previously worked as an SDE Intern at an MNC during my 4th year.

Then I explained one of my resume projects briefly. It was a full-stack autonomous AI agent system for event scheduling, conflict detection, and conflict resolution.

I also had another project , a normal full-stack movie ticket booking application , but I did not mention it during the introduction.

Questions Asked

DNS

They asked:

What is DNS?

I explained that DNS is used for mapping human-readable names to IP addresses.

DevOps / System Questions

After that, the interview became more focused on the DevOps side.

They asked about:

• Containers
• Virtual Machines
• Docker
• Kubernetes
• Operating Systems

I was able to explain most of them comfortably.

For Operating Systems, I also explained:

• User Space
• Kernel Space
• System Calls

Kubernetes Discussion

They then asked how we would use Kubernetes to run containers and what are the basic things needed to do that.

Since I had never used Kubernetes practically, I honestly told the interviewer:

“I am familiar with Docker and know the concepts of Kubernetes, so I will explain based on that.”

Then I explained concepts mainly around:

• Monitoring
• Auto Scaling
• State Management

Parking Lot System Design

Next, they asked me to design or give an overview of a Parking Lot system.

I first asked about the functional requirements.

Then I started with High-Level Design (HLD).

One mistake from my side was that I was doing this in Notepad instead of using a sketching tool or canvas.

I divided the HLD into 3 parts:

1. Client
2. API Gateway
3. Microservices

I also explained scenarios where multiple users simultaneously try to book the same parking spot.

For handling concurrency, I mentioned using Redis locking, since that was the approach I was familiar with.

After that, I asked more about the role, and the interview ended.

Mistakes in Round 1

Some mistakes from my side:

• I was not properly prepared for High-Level Design.
• Under pressure, I made avoidable mistakes.
• Explaining architecture in plain text instead of diagrams was not ideal.

The allocated time was 1 hour, but I finished the interview in around 25 minutes.

Gap Before Second Round

I got a call saying that the next technical round would happen in 1 hour.

During that time, I quickly revised:

• High-Level Design basics
• Topics I was unable to answer properly
• Some DevOps concepts

Since I was already familiar with LLD/OOPs, I focused more on HLD preparation.

Second Technical Interview

The second interview again started with a basic introduction.

This round was comparatively harder but intresting.

DNS Deep Dive

They again asked about DNS, but this time more deeply.

The question was:

How do we know the exact IP of the DNS server we hit when we visit a website?

I told the interviewer that I was unaware of the exact commands, but I knew we could not directly do it from the browser and would need terminal commands like ping.

AI + Pipelines Discussion

After that, the discussion shifted toward pipelines and AI usage in reducing human effort.

I explained that:

• LLMs can help in reasoning when pipelines fail.
• Screenshots can be captured at the exact moment when an application fails.
• AI can assist in debugging and reducing manual effort.

However, I was not able to answer this section in deep detail.

Jenkins

Then we discussed Jenkins and CI/CD concepts.

DSA Question

They asked an easy DSA question:

Merge two sorted linked lists while avoiding duplicates.

I directly started with the optimized two-pointer approach using a new linked list explained edge cases and duplicates with examples before writing code.

I forgot to handle the edge case where one linked list ends before the other when i was wring the code.

Before I could finish, the interviewer hinted:

“You are forgetting one case.”

Then I added the missing logic.

I also dry-ran and explained the solution before writing the code.

SQL Question

Next, they asked me to write an SQL query:

Join Employee and Department tables and count the number of employees per department.

I used JOIN correctly, but due to pressure, I wrote an unnecessary outer SELECT statement which introduced redundancy.

They moved on afterward.

Project Discussion

They looked at my movie ticket booking project and asked:

How would you handle duplicates and simultaneous bookings?

I again explained using Redis.

Amazon Cart / Frontend Design Discussion

Then they asked:

How would you design an Amazon cart or section?

I misunderstood the question.

Since it was specific for React/frontend-specific, I started talking about:

• Lazy Loading
• Pagination
• Code Splitting

Even after they restated the problem, I still could not fully understand what they were expecting.

Eventually, I told them honestly that I was not understanding the requirement, and we moved on.

End of Round 2

At the end, I asked more about the role and expectations.

Overall, it was a good round.

The interviewer was friendly, and the interview lasted more than an hour.

Manager Round

After that, I got a call for the Manager Round.

The recruiter mentioned that the feedback till then was “Good Hire”.

The round was scheduled around half an hour later.

Before the round, I revised:

• Introduction
• STAR-based situations
• Behavioral discussions

Managerial Discussion

This round was mostly non-technical.

The manager asked about:

• My family
• What they do
• Why I was interested in the role
• My thought process when joining B.Tech
• Agile methodologies and its component

They also asked about methodologies used in my current company.

I explained that my current company did not strictly follow Agile or Waterfall. Usually, we were given a demo application or website reference and asked to build similar functionality.

They also asked:

How many people are there in your company?

I answered:

• Around 10 people
• 2 people working on a demo project

Role Understanding Discussion

They asked me what I understood about the role and how tools are owned internally.

Then they counter-questioned me:

What exactly did you understand about this role?

I answered based on:

• The Job Description
• The previous two interviews

But the answer was not fully satisfactory.

Then they explained:

• Team vision
• Responsibilities
• Expectations
• Contribution areas

I noted everything carefully.

Ambiguous Situation Question

They also asked me about a situation where I had to work in an ambiguous environment.

I explained one such situation from my experience.

Then the interview ended.

Final Result

The allocated time was 45 minutes, but the discussion extended to around 1 hour.

I was not fully prepared for non-technical managerial discussions.

By the end of the process, I already felt that I had made some irreversible mistakes during the interviews, especially in:

• High-Level Design
• DevOps depth
• Communication during the Manager Round

The next day, I received a rejection mail.

Final Thoughts

Overall, the interview experience was good and interviewers were helpful.

The process tested multiple areas:

• DSA
• DevOps
• System Design
• SQL
• Communication
• Behavioral Understanding

One thing I learned clearly is that knowing concepts is not enough. Being able to communicate them clearly under pressure matters equally.

I have less than 1 year of experience an graduated in 2025, to fill the gap and to be stable I was desperate and joined this company but I am now seeing that it is not aligning with my future and goals and I am not able to save anything as all is being spent on travel and stay. So a better advice is don’t be desperate while choosing a career but don’t b too late.