Cracking Salesforce AMTS (Off-Campus 2026): My Complete Interview Experience, Preparation Strategy & Lessons Learned
A few days ago, I received one of the most exciting emails of my career:
“Congratulations | Salesforce — AMTS Offer”
As a final-year engineering student, seeing Salesforce in my inbox felt surreal.
In this article, I’ll share my complete Salesforce AMTS (Associate Member of Technical Staff) off-campus interview experience, what each round was like and the lessons I learned throughout the process.
If you’re preparing for Salesforce or any top product company, I hope this gives you a realistic picture of what the journey actually looks like.
How It All Started
Everything started when I came across the Salesforce AMTS hiring opportunity for 2026 graduates.
Before applying, I spent some time tailoring my resume according to the role and highlighting the projects, internship experience, and skills that were most relevant.
I also reached out to a Salesforce employee and requested a referral.
For off-campus opportunities, I strongly recommend trying to apply through referrals whenever possible. A referral doesn’t guarantee an interview, but it definitely helps your application get more visibility. Off-campus hiring is extremely competitive, and every small advantage matters..
Timeline
- Applied: March 26
- Received Online Assessment: April 1
- Online Assessment: April 3
- Technical Round 1: April 30
- Onsite Interviews: May 15
- Offer Received: May 18
Online Assessment
The Online Assessment consisted of 3 coding questions in 90 minutes, with each question noticeably harder than the previous one.
The questions followed an increasing difficulty pattern.
- Question 1: Arrays, Sorting, and Greedy Observation.
- Question 2: HashMaps, Frequency Counting, Custom Sorting, and Comparator-based Ordering.
- Question 3 : was significantly harder and required simulation of a real-world system with multiple constraints.
I was able to solve the first two completely. For the third question, I passed most of the test cases but missed a couple of edge cases.
When the assessment ended, I genuinely wasn’t sure whether my score would be enough to get shortlisted. So when I received the interview call later, it was a pleasant surprise.
Technical Interview Round 1 (Virtual)
On April 21st, I received a call from HR informing me that I had been shortlisted for the first technical interview.
The round was conducted virtually by a Senior Member of Technical Staff (SMTS) and was a live coding interview on HackerRank CodePair.
After a brief introduction, the interviewer shared the first problem.
The first question was based on palindrome strings and dynamic programming. I started by discussing the brute-force approach, explained why it would not work within the given constraints, and then gradually arrived at the optimized solution which was the dynamic programming solution
I spent around 25 minutes on this question and coded it out and eventually passed all 15/15 test cases.
The second question was significantly harder. It involved dynamic programming and wasn’t one of the standard problems that frequently appear in interview preparation sheets.
I first explained why a greedy approach wouldn’t work and then gradually built the solution using recursion and memoization.
This question took another 25–30 minutes for coding and debugging and after a few iterations I managed to pass all 15/15 test cases.
By the end of the round, both questions were completed successfully.
Before ending the interview, I asked a few questions about Agentforce and how AI-powered products were being built inside Salesforce.
A small tip here: always prepare thoughtful questions for the interviewer. It is one of the easiest ways to demonstrate genuine interest in the company.
Later that day, I received confirmation that I had cleared the round and would be moving to the onsite interviews.
Onsite Interviews at Salesforce Bangalore
Soon after, HR reached out and asked me to submit my location preferences and travel details.
Salesforce sponsored the entire trip, including flights and accommodation. My onsite interview was scheduled for 15 May at the Salesforce Bangalore office.
Walking into the Salesforce office for the first time felt exciting because this was no longer just another interview. It felt like I was getting closer to something I had been working towards for months.
Technical Interview Round 2
The second technical round was conducted by another Senior Member of Technical Staff (SMTS).
The conversation started with introductions.
The interviewer introduced himself, spoke about his team, and shared some details about the projects he was currently working on. We then discussed my internship experience and a few projects from my resume before moving into coding questions.
The first question was a dynamic programming problem. It reminded me of a well-known DP pattern but with a twist.
Instead of jumping directly to the final solution, I explained:
- Why brute force would be expensive
- Why greedy wouldn’t always work
- How dynamic programming helps avoid repeated computation
The interviewer seemed more interested in the reasoning than the answer itself. Unlike the virtual round, this was paper coding, so I had to write the complete solution manually and perform a dry run.
The second problem involved graphs. I was required to write the entire solution on paper and explain each step of the approach.
Again, communication mattered as much as correctness.
One thing I consistently noticed throughout the Salesforce interviews was that interviewers wanted to understand how you think, not just whether you knew the answer.
Towards the end, I was asked a behavioural question:
Get Anush Revankar’s stories in your inbox
Join Medium for free to get updates from this writer.
“If a colleague asks for your help, and helping them could potentially result in them getting promoted instead of you, would you still help them?”
My answer was straightforward.
“The goal should always be to maximize the success of the team and the company rather than optimize purely for individual outcomes.”
Then the interviewer asked if I had any questions. This time, I had prepared even more thoroughly.
I had gone through Salesforce engineering blogs, Agentforce documentation, recent AI announcements, and various engineering articles.
What started as a simple Q&A turned into a deep technical discussion.
We spent nearly 20–25 minutes discussing Agentforce, AI systems, engineering challenges, and Salesforce’s future direction.
The interviewer seemed genuinely interested in the discussion, and by the end it felt less like an interview and more like a conversation between engineers.
The round lasted well over an hour.
A little later, HR informed me that the feedback from the interviewer was positive and that I would be moving to the final round.
Hiring Manager Round
After a short break, I had my final round with an HiringManager.
This round was very different from the previous two.
There was almost no DSA innstead, the focus shifted towards projects, architecture, decision-making, and communication.
We spent a significant amount of time discussing the work I had done during my internship. I was asked questions like:
- Why did you choose this architecture?
- What trade-offs did you consider?
- What limitations did the system have?
- If you had to rebuild it today, what would you change?
We also discussed one of my AI projects in detail, including how I had built a RAG-based system and the design decisions involved.
The Offer
A few days later, I received an email with the subject:
“Congratulations | Salesforce — AMTS Offer”
That was probably one of the happiest moments of my college journey.
Months of preparation, solving problems, giving mock interviews, improving projects, and learning from failures had finally paid off.
My Preparation Strategy
If I had to summarize my preparation in a few points:
1. Build Strong DSA Fundamentals
Salesforce places a significant emphasis on problem-solving. The OA and both technical rounds heavily tested DSA concepts.
I primarily used:
- LeetCode
- Striver A2Z Sheet
- Mock Interviews
2. Learn How To Present Solutions
Many candidates know the solution but fewer candidates can explain how they arrived at it.
My usual approach was:
- Start with brute force
- Discuss limitations
- Analyze complexity
- Move towards optimization
- Then implement
This demonstrates problem-solving ability much better than immediately jumping to the optimal solution.
3. Know Your Resume Thoroughly
Every project, technology, and internship experience on your resume is fair game.
If it’s on your resume, assume you can be questioned on it.
Final Advice
If you’re preparing for Salesforce AMTS interviews:
- Build strong DSA fundamentals.
- Practice communicating your thought process.
- Know every line on your resume.
- Build projects that solve real problems.
- Prepare thoughtful questions for interviewers.
Most importantly, remember that interviews are conversations, not interrogations.
The candidates who perform best are often the ones who can combine technical skills with clear communication and genuine curiosity.
I hope this experience helps future candidates.
All the best !!
