READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 116 of 153
Interview experiences · Scale AI
Scale AI Software Engineer Interview Experience — Debug a Real Codebase, Then an LLM API Round
Phone Screen It was the "party" question that's already been posted on the forum, pretty easy. Debug This round felt a bit harder. The question was the "assign project" one that's already on the forum, and the main issue was that time was tight. It's a new codebase with several files, and you need to go back and forth through it a lot (would've been a lot easier if I could've just used AI for thi…
Interview experiences · Scale AI
Scale AI Software Engineer Interview Experience — Impatient Interviewer, Essay-Length Question
I'd looked at this company before and thought about applying, but I never really believed I'd pass an interview here, so I went in with a "just try it" mindset. The whole interview was really contradictory. You'd think a technical interview would be short and to the point, but the interviewer was very impatient the whole way through. He gave only a very brief, shallow rundown of himself and what…
Interview experiences · Scale
Scale Machine Learning Engineer interview: coding round followed by ML theory
After speaking with a recruiter, I went through a compact sequence: a manager screen, a coding round, and a final discussion focused on machine learning theory. The process felt broad and deep at the same time, which made it difficult to approach as one straightforward type of interview. Even when I felt comfortable with the technical parts, the theory discussion kept bringing me back to fundamen…
Interview experiences · Scale
Scale Product Manager interview: AI product cases and fit
After a recruiter call, I entered a product-focused process that lasted several weeks. It combined behavioral questions with product-sense work. The work was AI-focused, and the cases asked for broad thinking with room to shape an approach. The live interviews involved several people and tested different aspects of my thinking. Some conversations were about product sense and design, while others…
Interview experiences · Scale
Scale Software Engineer interview: card-game coding exercise
The recruiting flow felt friendly at first, then the technical work proved unlike a standard LeetCode trick question. The coding prompt used a card-game theme and was more about implementing many conditions than finding an elegant idea. It moved through multiple cases, so I had to track the logic and states carefully. In the live coding round, I needed to work through those conditions quickly. Th…
Interview experiences · Scale
Scale Software Engineer interview with a time-pressured technical screen
My interview process was drawn out. It started well enough, but the ending left a sour feeling. I first had a recruiting call, followed by a technical screen after some preparation from the recruiter. The last part was the most exhausting. The final round was a loop with many interviews, and my experience varied by interviewer. Some seemed distracted or disorganized, which made the day feel longe…
Interview experiences · Scale
Scale Software Engineer interview with many coding rounds and debugging
My process felt like an implementation marathon. I went through many coding-focused rounds, and it eventually became tiring and even boring instead of engaging. There were also behavioral and debugging rounds, and the debugging session was the most excruciating part for me. Some interviewers were good, but others turned off their cameras and stayed silent throughout the coding rounds. That made i…
Interview experiences · Scale
Scale Software Engineer interview with practical frontend work
My interview path followed a fairly classic structure: a recruiter screen, a technical screen, and then meetings that expanded into onsite-style rounds. The technical portion included system design and practical problem-solving that combined algorithmic work with a frontend component, so it was more ambiguous than pure coding. The hardest part for me was figuring out what the interviewers expecte…
Interview experiences · Scale
Scale Software Engineer live coding interview implementing a card game
After I cleared an initial online assessment, my next step was a 60-minute live coding interview. I was surprised that it wasn't a traditional algorithm question. Instead, I had to implement a unique card game with enough rules to turn it into a real build exercise. I had to translate the problem into working code, and the time limit forced me to stay organized. I passed that round and moved into…
Interview experiences · Schneider Electric
Schneider Electric Software Engineer interview: Distribution Center digitization
I met a panel of two managers and an HR representative in a conference room in Athens. After introducing myself, I described projects I'd led during internships and contract work. We then discussed logistics and processes, particularly how I'd digitize work in a Distribution Center. They asked about my strategy for implementing advanced digitization. The questions felt practical, and I appreciate…
Interview experiences · Schneider Electric
Schneider Electric Software Engineer Interview Experience: quick technical and manager process
After a recruiter call, the process moved quickly through two interviews with a hiring manager and a final recruiter conversation about the offer and next steps. The organization made it feel low-stress, and I liked how friendly the panelists were. There was a technical round and a managerial round. I discussed my background, why I applied, and technical questions that did not feel designed as tr…
Interview experiences · Schwab
Schwab Senior+ Java Developer Interview Experience — A Final Onsite with No Break Between Interviews
After I talked with the recruiter, there was no phone interview. They scheduled the final onsite directly. I live locally and the office was not far from my current company, so I took half a day off and drove over for the interview. Interview schedule First, I spent 45 minutes talking with the hiring manager. It was mainly about understanding my background and answering behavioral questions. Next…
Interview experiences · Schweitzer Engineering Laboratories
Schweitzer Engineering Laboratories Software Engineer interview: C and C++ pressure
The interview felt like it went well overall, though there were a couple of genuinely tricky moments that made it sharper than a typical screen. In the behavioral portion, a few questions did not come as easily as I wanted, even though I think I handled most of them. Most of the technical questions came back to coding concepts and problem-solving, with C and C++ as the language focus. That mix of…
Interview experiences · Schweitzer Engineering Laboratories
Schweitzer Engineering Laboratories Software Engineer interview: embedded depth
The questions were described as easy, but the interview was not superficial. It required low-level embedded-system design and programming knowledge, and I felt the details could catch someone who skimmed. I had a good conversation with the panel and felt they were exploring whether I understood the material deeply. Even answers I thought were correct led to follow-ups on important details, which…
Interview experiences · Schweitzer Engineering Laboratories
Schweitzer Engineering Laboratories Software Engineer Interview Experience: a structured three stage loop
My interviews had three stages: an initial HR screen, a technical interview on Microsoft Teams, and an on site day. The HR conversation covered my background, experience, and interest in the role. The Teams interview focused on programming knowledge and problem solving, and I connected my answers to relevant projects. The on site went deeper into engineering conversations with the team. We discus…
Interview experiences · Schweitzer Engineering Laboratories
Schweitzer Engineering Laboratories Software Engineer Interview Experience: Values and networking basics
The process was long and included both an HR screen and an in-person component. The HR conversation focused on values, and the interviewer kept returning to how I think about those fundamentals rather than moving straight into technical questions. The technical side covered computer-science basics and several computer-networking questions. The pace was more intensive than I expected, but the over…
Interview experiences · Scientific Research
Scientific Research Research Scientist interview: prolonged silence after onsite
The process took much longer than I thought it should. After an initial phone screen and an interview with the hiring manager, I eventually had an onsite stage, but the timeline extended beyond three months. While I waited, both the manager and recruiter were essentially unreachable, and it felt as if the process had paused. The interviews themselves were not my main concern. Once I was left in l…
Interview experiences · Scientific Research
Scientific Research Software Engineer interview: CAPA panel
After applying online, I first spoke with a recruiter about the role and my background. That conversation was focused on fit and helped set expectations for what the hiring team cared about. Soon after, I had a panel-style interview that combined technical and situational discussion. Even when the topics became specific, the tone was conversational. The technical discussion centered on my CAPA-st…
Interview experiences · Scientific Research
Scientific Research Software Engineer pressure coding interview experience
My process started with a recruiter call and quickly became structured technical conversations. I was usually asked to walk through my resume and projects, then they dug into what I had actually done. Sometimes the prompts were straightforward about systems; sometimes they were scenarios meant to test how I reasoned. One round combined leadership-style discussion with coding. I had to explain my…
Interview experiences · Scotiabank
Scotiabank Financial Analyst interview: one-hour branch-manager round
After I applied and was shortlisted, I had a preliminary recruiter-style call that felt more like an eligibility and fit check than a deep interview. About a week later, I had the main round with branch managers, including one person who was also the team manager. The conversation lasted roughly an hour, and fortunately there were no further interviews. Most of the discussion was about my backgro…
Interview experiences · Scotiabank
Scotiabank Financial Analyst interview: Superday valuation questions
The process felt more like interview school than a casual screen. The first round combined behavioral and technical questions, and the Superday was a series of short back-to-back conversations. Some interviewers wanted role-specific technical knowledge while others stayed behavioral, but all of it tested whether I understood the market instead of just definitions. I was pushed on a stock pitch, i…
Interview experiences · Scotiabank
Scotiabank Software Engineer interview: late start and unclear Python exercise
I joined the Scotiabank interview five minutes early, but the main interviewer arrived about 20 minutes late. Once it began, I gave detailed answers and explained the business reasons behind choices in my past projects. I felt some answers were judged through assumptions that did not match the context I was trying to clarify. I was also frustrated by the implication that I relied on AI tools, bec…
Interview experiences · Scotiabank
Scotiabank Software Engineer interview: practical SQL and Python discussion
After a recruiter screening phone call, I had a technical round with three interviewers. It felt straightforward and seemed more about getting a read on me than catching me off guard. The conversation included SQL, Python, and other general technical questions. It did not feel like a heavy algorithm gauntlet. The questions stayed grounded in practical language and query knowledge. Overall, it fel…
Interview experiences · Scribd
Scribd Software Engineer Interview Experience — Rejected at Onsite Coding Over Missing Metrics
Interviewed for the content understanding team, mid-level, in June/July. Phone screen Structure: self-intro → why I'm leaving my current company → DB schema + SQL → a small system design question → observability → my questions for them. Schema / SQL: given a many-to-many relationship, design the tables (they wanted a join table with a composite primary key), then write the query. System design: u…