READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 134 of 153
Interview experiences · TCS
TCS Software Engineer interview: numeric aptitude questions instead of engineering discussion
My TCS AI interview felt more like a broad numeric and aptitude round than a technical conversation. The mock-test setup mixed numeric and aptitude questions. I kept thinking about the mismatch between what I had prepared from my experience and why so much time went to the numeric part. The questions were straightforward enough, but the flow did not feel connected to actual engineering work. Ever…
Interview experiences · TCS
TCS Systems Engineer interview: priority NQT and Java-focused Prime interview
I went through an on-campus priority NQT process. I had to solve two coding questions before reaching the Prime interview, so the NQT felt like a gatekeeper. The technical interview focused mostly on Java, especially Java OOP, Spring Boot, and SQL. There was also an expectation that I could code through multiple test cases. The process did not rely only on theory. It put weight on solving enough…
Interview experiences · TD
TD Software Engineer interview: in-person L1 and L2 process
I interviewed in person, which made the process feel more immediate than a remote screen. The timeline described L1 and L2 followed by a managerial or HR round. In L1, I had a Python coding question, discussed my current project in detail, and answered questions about AWS Cloud knowledge. The prompts tested both execution and context: code alongside how I had applied it. Managing timing was a lit…
Interview experiences · Teledyne Technologies
Teledyne Technologies Software Engineer interview: C++ and SLAM questions
I started with an HR round of about 15 minutes. Soon after, I had a technical interview with a technical leader, focused on C++ coding and problem-solving around vision. The technical discussion covered SLAM, including bundle adjustment, filtering, and state estimation. It felt like they wanted to know whether I could connect the parts of a pipeline, not just answer isolated trivia. The content m…
Interview experiences · Teledyne Technologies
Teledyne Technologies Software Engineer Interview Experience: confrontational technical interview
The interview looked standard on paper, with technical and behavioral questions. I understood what they were looking for until one interviewer became confrontational, arguing, raising their voice, and pushing in a way that felt intended to put me down. I stayed as calm and professional as I could, but the exchange felt hostile and humiliating. I initially thought the pressure might be an intentio…
Interview experiences · Teledyne Technologies
Teledyne Technologies Systems Engineer interview: an intimidating first impression
From the start, I wondered whether I was the kind of candidate they wanted. The hiring manager's tone felt intimidating, and I began second-guessing my answers during the conversation. I expected the process might stop there, so I was surprised when they invited me to a second interview. I had to put the first conversation behind me and continue. The difficulty itself was average. What stood out…
Interview experiences · Telefónica
Telefónica Software Engineer interview: mobile architecture and offer
After I sent my CV, they called to ask about my experience and studies. I then went to a personal interview at the office. They told me there that I had been selected, so I did not have to wait or chase an answer. That part was quick and direct. In another part of the process, I first had an introductory interview, then an aptitude check and an English test. I later met the team to discuss the ro…
Interview experiences · TELUS Digital -
TELUS Digital - Account Executive interview: concerns about fairness
I did not find the process fair, and I left discouraged. I felt I was not given the same opportunity to show my skills and experience as other candidates, which made the experience feel uneven. As the interview progressed, I got the impression that I was being treated differently. That changed how I felt during it. Instead of feeling able to present my strengths clearly, I kept wondering whether…
Interview experiences · Temu
Temu North America Interview Experience — Five Rounds, Light on Coding, Heavy on Cross-Checking
Giving back to the forum. After getting hit with a layoff at the end of the year, I interviewed with Temu's North America team early this year. The whole process was 3 rounds of coding + 1 round of behavioral questions with a director/VP + 1 round with HRBP: Round 1: 496. Next Greater Element I Round 2 I don't remember clearly, but it was also a fairly standard LeetCode medium. Round 3 gave a lis…
Interview experiences · Pinduoduo
Temu Senior Software Engineer Interview Experience — A Two-and-a-Half-Hour Second Round
The difficulty shot up in this second round, though that was mainly because my technical skills were weak. I felt like I'd failed. I saw a report from someone who also had a second round in July, probably with the same interviewer: a strong manager vibe, and basically the same behavioral questions. The embarrassing part is that I only read that report in full after my interview. Anyways. This rou…
Interview experiences · Temu
Temu Software Engineer Interview Experience — LinkedIn Screen with a Twitter Feed Min-Heap Question
A recruiter reached out to me on LinkedIn, and that's how the interview got set up. Headquarters is in Boston, but all the hiring is remote. Every role interviewed under the title "software engineer," and the package gets negotiated after based on how you do in the interview. The first round was 60 minutes of coding, and here's how it went: Self-introduction, then they asked about my projects in…
Interview experiences · Temu
Temu Software Engineer Interview Experience — Technical Round Skipped, Final Round Is Just HR and Salary Talk
Last time I mentioned that after a 2.5-hour second round I felt like I'd failed, but I actually hadn't. The second-round interviewer (the dept lead) decided to skip the third-round technical round entirely, so my third round ended up being the final round too — just a chat with HR. A bit about my background, some basic behavioral questions, and then talking about what it's like working there and…
Interview experiences · Tencent
Tencent Data Scientist Interview Experience — Ghosted After a Marketing-Email Design Question
The interview was conducted in Chinese. My interviewer was a staff data scientist on Tencent's North America team. Their team works on games — they even asked me what games I've played. The team covers both product DS work and modeling DS work. They started by asking about the projects on my resume, then followed up with a few more questions about them. After that, they asked me this question: Sa…
Interview experiences · Tencent
Tencent Software Engineer interview: three fast rounds and an offer in about 20 days
After applying online, I went through three quick rounds: a technical interview, a second interview that leaned behavioral for me, and an HR interview. The sequence moved fast enough that I essentially learned where I stood the same day. From application to offer took about 20 days. Each step moved forward without much waiting, and the process felt streamlined compared with other hiring loops I h…
Interview experiences · Teoresi S.p.A.
Teoresi S.p.A. Software Engineer interview: transparent recruitment process
After initial recruiting contact, I had a phone HR conversation and then an online technical interview on Microsoft Teams. The process seemed orderly and well organized. People were punctual, professional, and willing to clarify questions about the role. Early on, they were trying to understand whether I had the basics for the job and how my experience fit the work. The technical discussion was g…
Interview experiences · Teradyne
Teradyne Software Engineer interview experience: project discussions with engineering manager
The process had several structured rounds that kept returning to my background and projects. It began with an HR call and then moved to conversations about my work experience. In those technical-adjacent discussions, they referred back to my slides, pulled out particular projects, and asked me to explain what I had done and how it related to the role. Meeting the engineering manager was a major p…
Interview experiences · Tesla
Tesla Dojo Software Engineer Interview Experience — No Extra Memory Allowed
I'm finally getting around to keeping a promise — sharing my phone screen experience for Tesla Dojo. The coding difficulty was medium-to-hard, but the bar for detail was very high. Hope this is useful for anyone else interviewing for Dojo. The interviewer showed up a little late, and jumped straight into coding with barely any small talk. Tesla's efficiency is really something. You're given a lis…
Interview experiences · Tesla
Tesla Machine Learning Engineer Interview Experience — Recruiter Changed the Format Without Notice
When I first got this role, the recruiter told me the technical interview would be 70 minutes long, covering Leetcode coding, LangChain, and MLflow. I prepared accordingly — I ground through a good number of Leetcode problems and specifically went and studied a lot of LangChain material. Then I got the official interview email, and the interview had turned into 45 minutes, with no details about t…
Interview experiences · Tesla
Tesla Machine Learning Engineer Interview Experience — Rejected After Two Technical Rounds
The first round was with the interviewer. He gave a quick rundown of his background, then asked how to model other agents in the simulation. The coding part was based on an input of shape [batch, num_waypoint, 2], and I had to compute a suffix sum, with output shape [batch, num_waypoint]. I forget the exact follow-up question after that... let me think about it more. The second round was with the…
Interview experiences · Tesla
Tesla Senior Software Engineer Interview Experience — Seven-Hour Palo Alto Onsite, Failed at a Last-Minute HM Round
A few months ago an HR person from Tesla reached out to me about a senior SDE role on an infra team under Tesla AI. I originally didn't have much interest in Tesla, but HR said their package could go up to twice my current package, which instantly got my attention, so I went and did the whole loop. Tesla hires by team, so the interview process and content are entirely decided by the team. It star…
Interview experiences · Tesla
Tesla Senior+ Backend Engineer Interview Experience — Four Onsite Rounds, All Staff-Level Interviewers
Phone screen, 45 min: design a ticket-master system. We went deep on how to prevent double booking. The interviewer also cared a lot about UX — what the API returns, what seat map the frontend shows once it gets that response, etc. Onsite: each round was 45 min. The email told me who the interviewer was and their title, but not which round would be system design vs. past-experience. It was schedu…
Interview experiences · Tesla
Tesla Software Engineer interview: algorithms, behavior, and system design
After a phone recruiter screen, I had two Tesla rounds. The first was LeetCode-style and focused on algorithms and problem solving. The interviewer cared about whether I could reason through the problem end to end, not simply arrive at an answer. The second round mixed behavioral questions and system design. We discussed how I work, how I would architect a scalable solution, and how I think about…
Interview experiences · Tesla
Tesla Software Engineer interview
Two technical managers interviewed me, and the conversation became intense right away. They asked about my motivation as well as technical and behavioral topics. One technical question concerned a motor module and required more rigor than I expected. The behavioral questions asked how I would handle production-engineering difficulties, when problems stack up and work still has to ship. I found th…
Interview experiences · Tesla
Tesla Software Engineer Interview Experience — A 15-Minute AI Recruiter Screen at 1.5x Speed
Recruiter round — they sent me an AI link, about 15 minutes. Going in, it was an AI with a really fast speaking speed, roughly like watching a normal video at 1.5x. This position wasn't really a match for my direction, so I answered kind of randomly. This position requires using Go, Java, Spark, Elasticsearch to build distributed systems — talk about your project experience with these How do you…