READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 138 of 153
Interview experiences · Toast
Toast Software Engineer Interview Experience — Coding Screen, Four-Round Virtual Onsite, Rejected
First was a coding round. It didn't seem too hard, basically one map and one loop, and it was a question I'd seen on the forum. After that came the long, stinky virtual onsite. System design: this was also on the forum. It's basically designing a restaurant seat reservation system. I'd suggest looking at Alex Xu's book, which has something similar, and then summarizing it yourself. This round was…
Interview experiences · Total Wine & More
Total Wine & More Frontend Engineer interview experience: store tour followed by silence
I first interviewed with the store manager, and it went very well. A couple of weeks later I met with the district manager, and that conversation also felt positive. Afterward, the district manager had an assistant manager show me around the store. I could see how the work ran day to day, ask questions, and shadow him as he went through his routine. I was there for almost two hours in total. Ever…
Interview experiences · TotalEnergies
TotalEnergies Software Engineer interview: assessment centre with group discussion and essay
My process was an assessment-centre-style loop rather than a single interview. After initial contact, I had a multi-part day with several sections, structured as a full evaluation instead of a casual conversation. The centerpiece was a competency-based interview about how I handled past situations and fit the role. There was also a group discussion and a short written essay on a given topic. It f…
Interview experiences · TotalEnergies
TotalEnergies Software Engineer interview: four-step process
The hiring process felt organized from the beginning and had four steps. I started with an HR conversation about my background, motivation, and whether I matched what the company wanted. That was followed by two technical interviews intended to assess my skills in a more hands-on way. The final conversation was with a Product Manager. We moved to the functional side of the role: their expectation…
Interview experiences · TotalEnergies
TotalEnergies Software Engineer interview: technical rounds and communication assessment
The process had several interviews, each with a fairly clear purpose. I began with HR, discussing my background and motivation. Technical interviews with the hiring team came next, followed later by leadership-level conversations. The atmosphere stayed professional and constructive, and I never felt dismissed. There was also an online soft-skills assessment. The in-person rounds combined technica…
Interview experiences · Tower Research Capital
Tower Research Capital Quantitative Analyst interview experience: five rounds across systems and probability
I went through a high-friction process with five rounds that tested breadth as well as depth. The subjects ranged across probability, puzzle-style questions, computer architecture, networks, and operating systems. Most prompts were open ended, with more emphasis on how I reasoned than on one correct answer. The lack of a clear right path was mentally exhausting at times. I had to keep my logic or…
Interview experiences · Tradedesk
Tradedesk Software Engineer Interview Experience — A Four-Level In-Memory Database Assessment
It was no longer the recipe problem, but there were still four levels, and the general idea and direction had not changed much. Level 1: Given a key, field, and value, write the value into the database and implement insert, delete, and update operations. This can be done with one nested map or two maps. Level 2: There were two search operations. The first search uses the key and field to list all…
Interview experiences · TransPerfect
TransPerfect Account Executive interview: assessment, negative-behavior questions, and no follow-up
The experience began smoothly with an introductory call about the role. I received an email link for assessment questions and heard quickly about what came next. When more rounds were mentioned, I expected a normal progression into deeper interviews. Instead, I was filtered out around the middle. After a screen, I completed a Criteria cognitive and personal-style test, then communication stopped.…
Interview experiences · TransPerfect
TransPerfect Project Manager Interview Experience: proofreading test and friendly interviews
I applied and moved through the process from July 13 to August 6. It stayed friendly throughout. After a recruiter call of about 20 minutes, I took a written proofreading test that lasted around two hours. Then I had a 50-minute online interview with the hiring manager and a department lead. The questions were relatively easy and aligned with the role. The final step was a roughly 40-minute in-pe…
Interview experiences · Transport for London
Transport for London Project Manager Interview Experience: No closure after two stages
The TfL process was a short two-stage setup that did not feel very structured. The interviewers were pleasant, but I had little room for meaningful back-and-forth or to show how I worked. I had prepared one scenario in a more experience-led format, but the questions arrived differently than expected. Another round was rushed and constrained, too brief to ask much. About a month after the intervie…
Interview experiences · Tredence
Tredence Data Engineer interview: PySpark, Spark architecture and SQL
After an initial recruiter-style conversation, I had a focused technical screen that lasted about 30 minutes. We discussed PySpark, SQL and how I worked with Azure Databricks. The panel's tone felt positive. The questions covered data engineering fundamentals. I explained Spark architecture in detail, talked through ways to parse JSON and, toward the end, wrote a SQL query to find three consecuti…
Interview experiences · Tredence
Tredence Data Scientist interview: NLP and GenAI gap
About a week after a recruiter call, I had one technical round. It began with my current project and resume, so the discussion initially felt grounded in my background. Then it shifted to NLP and GenAI, including transformers. I had not worked hands-on in that exact area. When I could not speak confidently about what they wanted, the energy dropped quickly and the interview effectively ended soon…
Interview experiences · Tredence
Tredence Software Engineer interview: React, Node.js, SQL, and scenarios
After a recruiter touchpoint, I had a technical screen about a week later. The process included three technical discussions and another technical round at their office. The difficulty was easy to medium, and the recurring topics were React, Node.js, and SQL. They combined basic DSA questions with scenarios about common web-app problems. The final in-person round stayed with the same themes instea…
Interview experiences · Trexquant Investment
Trexquant Investment Data Scientist interview with ML, DSA, and onsite superday
My interview process started when HR reached out. I then completed an online assessment covering ML and DSA style material, followed by a technical question round with one or two LeetCode problems in the medium to hard range. I expected more direct data science or machine learning questions, but those topics didn't really come up beyond the assessment. The next stage was an onsite superday. It we…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview: Hangman ML project
I started with the Hangman project, which was also mentioned as one of the stages other people had gone through for this company. It was a take-home coding challenge focused on improving the model's guessing performance. Later, the interviewer asked me directly how I'd make it better. After that, I discussed the project with an interviewer. The conversation was strongly focused on machine learnin…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview: LeetCode, statistics, and Stamford final round
The process began with a recruiter screen covering my background and previous work. Then I had a technical interview that combined a resume review, a medium LeetCode problem, and statistics questions. Later, I reached an in-person final round at the Stamford site. Those interviews focused on models and techniques connected to the work on my resume. The pace was fast from the beginning, and a lot…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview: one-month process ending with a CEO round
I first spoke with a recruiter about my background and general fit. That was followed by an online technical interview with a quant researcher focused on my analytical and quantitative skills. After that, I attended an onsite superday with several back-to-back interviews with different team members. The final stage was an interview with the CEO. The process took around a month. The recurring topi…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview: week-long Python assessment
My first step was a week-long Python coding assessment. It was essentially one algorithmic problem that I had to solve in code. Compared with the effort people often describe for roles like this, it felt one-dimensional. Honestly, it seemed to test little beyond whether I could get through the task quickly. After that, I reached what felt like the real interview stage and eventually had a convers…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview with a Markov-chain problem
The process started with an HR call about my background and fit. I then had a technical interview with a quant researcher. It included a LeetCode medium question, then shifted into a more research-oriented problem involving a Markov chain and expected steps using a cube-like setup. What I remember most is that they followed up on the mathematics and also wanted an efficient way to simulate the id…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview with hangman take-home
I started with a coding-focused hangman take-home assignment. It came with performance expectations: clearing a minimum level would earn an invitation to the superday. The assignment included a hangman strategy described as a baseline, along with typical win rates and the expectation that I beat it. After I finished, I had a round focused on my solution and my Python implementation choices, inclu…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst interview with one Python challenge
The interview process felt streamlined and medium in difficulty. Much of it focused on my background. They asked many questions about my resume and went deeper into what I’d done. The main technical step was one Python coding challenge. It wasn’t a multi-week ordeal, just a single challenge, and it didn’t feel unusually hard. My impression was that they wanted to see whether I could connect my re…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst medium coding round
I started with an HR call and then moved straight into a first technical round with a senior researcher. We discussed my resume, including follow-up questions, and then I was given a LeetCode medium problem. Depending on what came up from my experience, there was also room for probability or statistics questions. The coding portion felt like a direct test of fundamentals: arrays, clean implementa…
Interview experiences · Trexquant Investment
Trexquant Investment Quantitative Analyst, medium LeetCode-style technical screen
About a week after the recruiter call, I had a technical screen. We went through my resume, then I solved a medium LeetCode-style coding problem. It felt like a straightforward test of whether I could turn my background into clean, working code. I eventually reached the next step, which sounded like it was leading toward a superday. I hadn't completed the onsite portion yet, so the process stoppe…
Interview experiences · Trexquant
Trexquant Software Engineer Interview Experience — Strong Onsite Undone by a Brutal CEO Call
This is a niche quant firm. I interviewed for the software engineer role, which required strong C++ — after this point, all the coding rounds were C++ only. Recruiter chat: besides the usual questions, they threw in some C++ trivia on the spot, things like what default constructors a class can have. PM chat: I talked with their Lead PM, a very sharp guy. He mostly asked about my resume, and a lot…