Movate Interview Questions
& Process

The whole interview process felt like a formality to reject me, and I suspect the job posting was fake. The interviewer kept her camera off during the virtual Teams meeting. She started by bringing up totally wrong info about my resume, which I think came from bad AI scraping. Then she asked really vague hypothetical questions like 'What would you do if you didn't know what to do?' My answer was basically that I'd figure it out since I'm not stupid. I got rejected almost immediately after, and when I asked for feedback, I got an AI-generated explanation for why I was disqualified for an entry-level job I was overqualified for. Seriously, avoid this place, they treat job seekers terribly and waste your time.

So, my interview experience was pretty cool and I learned a lot. First, we had a communication round, and then a technical interview that was mostly about networking and cloud stuff. In the communication part, they asked me to introduce myself. I did, talking about my background, school, what I'm into technically, and my plans. I mentioned my AWS Cloud Practitioner cert and my project where I used AWS Lambda, API Gateway, DynamoDB, and S3 for a feedback system. I also chatted a bit about school and how it taught me discipline and teamwork, and about my friends, college mentors, and teachers who were supportive. The interviewer seemed to like my communication. Then came the technical round, which was heavy on networking. They started with TCP vs. UDP, and I explained TCP is reliable but UDP is faster. Then we talked about routing tables and how routers pick packet paths. NAT and its types came up, and I explained Static, Dynamic, and PAT. After that, it was DHCP, and I described the Discover, Offer, Request, Acknowledge steps. They also asked about SMTP for emails and DNS for name resolution. We touched on socket programming and ports like 22, 80, 443, 25, 53. Then, AWS NAT Gateways, how they let private instances reach the internet safely. The last part was a troubleshooting scenario: website access issue. I outlined checking ping, IP config, DNS lookups, and firewall/router settings. There were also quick questions on routers, switches, and DNS protocols. The interviewer liked that I understood networking basics and could explain cloud things. It was a good learning experience, and I feel ready for future interviews.

So I applied for a Tech Support role and the job was to work at the client location, which is Google in Hyderabad. The first round was basically to check our communication skills. They did this through a Group Discussion, debate, JAM, and self-introduction. Then, the second round tested my basic networking knowledge. I was asked questions on troubleshooting Wi-Fi and VPN issues, and also about control panel stuff. The last round was with HR, and they asked me why I wanted to join Movate, about my salary expectations, and if I was okay with working in Hyderabad.

The interview process seemed to be structured with a few rounds. Round 2, specifically, was heavily focused on technical concepts. They asked about Linux commands such as top, ps, df -h, grep, chmod, systemctl, and journalctl. SQL queries were also a big part, covering JOIN, GROUP BY, subqueries, and how to find the second highest salary or update/delete records. They presented real-time application support scenarios, like handling high-priority tickets and checking log files using tools like tail and grep. The escalation process was also discussed, along with basic shell scripting (variables, loops, if-else, input reading). Experience with ticketing tools like ServiceNow was explored, focusing on raising and resolving issues. Finally, they inquired about monitoring tools or manual service health checks. There was also an example project scenario presented.