Anonymous Software Development Engineer (SDE) interview questions
based on 77 ratings - Updated Jun 20, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
69%
Campus Recruiting
Campus Recruiting
31%
Applied online
Applied online
Interview search
77 interviews
Viewing 11 - 15 of 77 Interviews
Anonymous interviews FAQs
Software Development Engineer (SDE) applicants have rated the interview process at Anonymous with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 69.1% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 3 days. I interviewed at Anonymous (Noida) in Jul 2025
Interview
It was poor the interviewer asked me about my project and then said he is not aware about the tech stack so will not go into technicalities . And was continously interepting
Interview questions [1]
Question 1
asked me about the product i made in project? tell us why anyone should use it and how its better than competitors ? do a pitch of the product
Online coding round tested DSA and logic, then two technical interviews focused on problem-solving, basic OOP, and projects. HR round covered motivation, teamwork, and communication. Friendly experience, moderate difficulty. But i was not able to clear
Interview questions [1]
Question 1
They asked me aptitude questions ad puzzle in intervoew
I applied online. The process took 1 week. I interviewed at Anonymous (Chennai) in Feb 2024
Interview
The interview process started with an HR screening, followed by multiple technical rounds that focused on JavaScript, React, problem-solving, and coding challenges. It concluded with a culture-fit and salary discussion.
Interview questions [1]
Question 1
One key question they asked me was, "How does JavaScript's this keyword behave differently in arrow functions vs regular functions?" — to test my deep understanding of execution context.