READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 143 of 153
Interview experiences · UiPath
UiPath Machine Learning Engineer Interview Experience — LLM Agent Q&A, a LeetCode 837 Variant, and a Coding Reject
Role and interview process The role is an MLE position related to Agents. A recruiter reached out to me, and there were three rounds of interviews in total. Round 1: Recruiter call (30 minutes) We talked about my background, my current job search status, what direction I want to go in, and my timeline. The recruiter was very friendly and gave a detailed introduction to the company, but said the s…
Interview experiences · UiPath
UiPath Senior Frontend Engineer Interview Experience — Four Onsite Rounds, Two Left Unfinished
Their process was actually pretty fast. Overall it felt pretty average — the questions weren't especially hard, but between chatting about my resume and reading through the problems, I didn't finish several of them. Debugging round: I found a bug in the table sort, which was pretty simple. After that we spent most of the time talking about my experience with AI and harness engineering. Another de…
Interview experiences · UiPath
UiPath Software Engineer interview: positive live feedback followed by rejection
After a recruiter resume screen, I had about an hour for a medium LeetCode-style technical round. The interviewer first asked questions tied directly to my resume, then moved into coding. It felt like a straightforward session about how I think, not a puzzle-only test. I got positive feedback during the live problem-solving portion. A week later, I received a canned rejection saying I lacked the…
Interview experiences · Uline
Uline Software Engineer interview: campus assessments in JavaScript and DSA
At an in-person campus recruiting interview, I completed a cognitive assessment along with JavaScript and DSA questions. The interviewer was nice, and the questions weren't exceptionally difficult. Still, I hadn't prepared enough for how much I needed to handle on the spot. The material felt manageable, and I left thinking more review would have helped me feel comfortable. I didn't move forward a…
Interview experiences · Uline
Uline Software Engineer interview: sales aptitude tests and unclear role expectations
Before I reached an interview, I completed several assessments that felt unrelated to software engineering. One was a sales aptitude test full of sales terminology. When I questioned it, I was told it measured speed and agility. That explanation still didn't connect it to my day-to-day work. There were more timed assessments during the interview, and nobody could clearly explain how their results…
Interview experiences · United Auto Credit
United Auto Credit Software Engineer interview: canceled London round
My second-round interview became one of the worst interview experiences I have had. I was asked to come to the London office and paid more than £100 for the train. Communication already felt broken: nobody in the office had my email, and the person responsible for updates went on holiday, so I could not reach anyone for about a week before the interview. They called about an hour before the sched…
Interview experiences · United Technologies & Information Services
United Technologies & Information Services Software Engineer Interview Experience: two quick offer paths
I applied online, then a recruiter contacted me by email and scheduling moved quickly. I spoke with two people on Microsoft Teams. It was a straightforward conversation, and they finished by saying they would send a write-up to the hiring manager. Later that same day, I heard they wanted to send an offer letter. I also had a similar experience in a separate run. That time, there was just one 30-m…
Interview experiences · University College London
University College London Research Analyst interview: research presentation panel
This interview felt heavier than the others because it added a short presentation to a formal panel. Before the main discussion, I prepared and gave a 5 to 10 minute talk on my previous research, then proposed a protocol or approach for a technique used in the lab. The panel moved straight from that presentation into probing questions. Each panel member asked background and competency questions,…
Interview experiences · Upstart
Upstart Data Scientist Interview Experience — One Tech Screen, a Two-Round Virtual Onsite, and an Offer a Week Later
Overall the experience was quite good — the HR person and the several interviewers I dealt with were all very supportive, and none of them looked down on international candidates. There was no HR screen; I went straight into the first technical round. The interviewer didn't ask about my resume at all at first — just had me do a quick self-introduction and then went straight into questions. The qu…
Interview experiences · Upstart
Upstart Data Scientist Interview Experience — SQL Screen Then a Four-Round Onsite Full of Case Studies
Three SQL questions, no need to actually run the query. There's a marketing table (by marketing_touch), and another one is a conversion table. The first question is to calculate avg count by month. The second is to find the last touch before conversion, by company (or by month, I don't quite remember). The third is: conversion and last touch both happened in some particular month, and how many co…
Interview experiences · Upstart
Upstart Data Scientist interview: fast-paced statistics and probability questions
After the recruiter screen, I was told the hiring-manager interview would be a straightforward conversation with one technical question at the end. Instead, brief introductions led into deep theoretical statistics and difficult mental math. The interviewer moved extremely fast. When I was unsure or interpreted something differently, I didn't feel I received enough clarification to get back on tra…
Interview experiences · Upstart
Upstart Intern Data Scientist Interview Experience — Same Questions Recycled Between Rounds
Overall, the experience was pretty good. The HR person and the few interviewers I dealt with were all really supportive — nobody looked down on international candidates. There was no HR screen — I went straight into the first-round tech interview. The interviewer didn't even ask about my resume; we did a quick self-introduction and then went straight into the questions. The questions were: An ato…
Interview experiences · Upstart Network
Upstart Network Data Scientist Interview Experience: Stats-heavy manager round
After a straightforward recruiter screen, I was told the hiring-manager conversation would last about forty-five minutes and end with one A/B-testing question. Instead, it became mostly deep theoretical statistics, delivered very quickly with little clarification when I was unsure or interpreted something differently. Earlier questions also had a statistics-first tone rather than ordinary resume…
Interview experiences · Upstart
Upstart Senior+ Data Scientist Interview Experience — A Hardcore Stats Screen With the Hiring Manager
In Q4 2024 a recruiter reached out to me on LinkedIn about a staff DS role at their company. After a quick chat we scheduled a one-hour screen with the Hiring Manager (the ML Applications Director). After a short self-introduction we got into the first part. He asked me to walk him through a project at work where I needed to measure impact but couldn't launch an experiment. I gave him the backgro…
Interview experiences · Upstart
Upstart Senior+ Data Scientist Interview Experience — Two Interviews Years Apart, Same Clash With the Interviewer
I applied to this company years ago, right after graduation, and it felt like neither I nor the phone-screen interviewer were really into each other. Fast forward many years, and this time the HR screen and phone screen actually went well at first — but the virtual onsite took me right back to those days. I ran into another interviewer where, again, neither of us was really into the other. That s…
Interview experiences · Upstart
Upstart Software Engineer Interview Experience — Four OA Problems, Not Enough Time
Time was way too tight, the problems were super long and wrapped in scenarios, so I spent forever just reading through them. I didn't pass all the test cases on questions 3 and 4, so I definitely failed this one. Let me vent for a second too. I was job hunting around this same time last year, and it clearly feels way harder this year. Can people actually get all 4 of these problems bug-free withi…
Interview experiences · Upstart
Upstart Software Engineer Interview Experience — Recalling All 5 Online Assessment Questions
All 5 real questions, fully recalled. Question 1: Sum of multiples of 3, 5, 7 less than a given number For example, if the given number is 12, the multiples of 3 below it are 3, 6, and 9; the multiples of 5 are 5 and 10; and the multiple of 7 is 7 — so sum = 3 + 6 + 9 + 5 + 10 + 7 = 40 (12 itself, although a multiple of 3, is not included). Note: the original post's formatting here was garbled (s…
Interview experiences · Upstart
Upstart Software Engineer Interview Experience — Six OA Questions Buried in Walls of Text
Very easy, 6 questions. The biggest challenge was that most of the questions were way too long — it took more than 2 minutes just to read and understand each one, and if you didn't pass on the first try, debugging got really stressful. For example, the first question (8 minute time limit) opened with a long paragraph about someone in medieval times who wrote a manuscript... two minutes later... t…
Interview experiences · Upstart
Upstart Software Engineer Interview Experience — Three OA Questions, Stuck on a Grid-Search Timeout
There were three questions in total, and two of them hadn't shown up in any interview reports before. Given a list of coordinates (x, y), find the min x, min y, max_x - min_x, and max_y - min_y. The problem statement was basically: filter out (name, score) pairs where the score is above a threshold, keep everything below the threshold, then find the max score among what's left and return its name…
Interview experiences · Upstart
Upstart Staff Data Scientist Interview Experience — A Statistics-Heavy Hiring Manager Screen
In Q4 2024, a recruiter reached out to me on LinkedIn about a staff DS role at their company. After a short conversation, we scheduled a one-hour phone screen with the hiring manager (an ML Applications Director). After a brief self-introduction, we moved into the first part. He asked me to walk him through a project where I needed to measure impact but couldn't launch an experiment. I described…
Interview experiences · UST Global
UST Global Software Engineer interview: a rescheduled panel and basic coding
I expected a normal technical process and first got an HR invitation. I cleared the first technical round, but in the next round the panel said, only minutes after introductions, that it needed to be rescheduled. That made the process feel abrupt and hard to treat as a clean evaluation. A later attempt felt easier and more casual, with resume questions and basic array and hashmap coding. I felt t…
Interview experiences · UST Global
UST Global Software Engineer Interview Experience: Four rounds and HR ghosting
This was my most frustrating process because of what happened after I invested so much time. I completed four interview rounds, including a face-to-face interview, and spent real effort and money on every stage expecting at least a clear update at the end. Instead, the HR team stopped responding. Calls and emails went silent after the final round. There was no rejection message and no outcome com…
Interview experiences · UST
UST Software Engineer Interview Experience: Multiple rounds followed by silence
My experience began with virtual interviews and turned into a frustrating stretch of silence. I had a video technical interview with a technical lead and team members, with HR and resources human involved in the same interview. I expected follow-up calls afterward, but contact was intermittent and eventually stopped. I never received a clear acceptance or rejection update, even after spending sub…
Interview experiences · Valeo
Valeo Software Engineer Interview Experience: Academic projects, C fundamentals, and ECE questions
My first round was a written test that felt easier. Then we discussed projects I had completed during my academics, with a strong focus on C basics. The interviewers cared most about my project, so I had to explain every block and why I chose each component. They followed up with "why" and "what if" questions. They also tested C fundamentals directly: pointers, arrays, strings, functions, structu…