READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 125 of 153
Interview experiences · Sonata
Software Engineer interview at Sonata: interview experience
After a recruiter call through Risebird, I went through two rounds that felt disconnected from the client and the actual role. Neither interviewer seemed to know much about what the project needed, and the second round repeated the same problem. The interviewer also appeared unaware of what had been covered before, and I could not get a clear explanation of how the interviews related to the clien…
Interview experiences · Sonata Software
Software Engineer interview at Sonata Software: interview experience
The process started with a recruiter-managed Risebird setup, but the early technical discussion did not seem connected to the actual project. Both rounds were led by people who did not appear closely tied to the client or role details. The second repeated the same pattern, and the interviewer did not seem to know what had already been discussed. Communication became the larger problem. I made mul…
Interview experiences · Spacex
Software Engineer interview at Spacex: interview experience
I got far enough to face technically intense screens that seemed built to test end-to-end understanding. Even when a question was posed as a hypothetical, it did not feel like a formula-memory exercise. It felt as though they wanted hands-on reasoning and confidence with fundamentals across the chain. The hardest part was a run of very pointed hypotheticals that seemed only loosely connected to m…
Interview experiences · Starr Companies
Software Engineer interview at Starr Companies: interview experience
After I applied, about a month passed before I heard anything. I was then sent a HireVue link for video responses and a coding challenge. After another wait, a technical recruiter scheduled a short 30-minute call to explain the role and next steps. About a week later, I was invited to schedule time with the hiring manager. That conversation mixed behavioral and technical topics, including Spring…
Interview experiences · Steven Douglas Associates
Software Engineer interview at Steven Douglas Associates: interview experience
The process felt standard and not especially punishing. After an initial HireVue-style step, I had a couple of live conversations that were more about how I thought than about trick questions. The technical round was framed as a fit check against the team’s stack, so it tested background knowledge without becoming a coding contest. The live rounds were welcoming. I discussed my resume, answered S…
Interview experiences · Super Micro Computer
Software Engineer interview at Super Micro Computer: coding loop
The loop had a predictable shape, even though I was not selected. It began with three medium LeetCode-style coding rounds, continued to system design, and ended with a cultural-fit conversation. The interviewers were pleasant and the atmosphere stayed positive. What bothered me was the format more than any particular prompt. The coding rounds felt dated and close to traditional LeetCode preparati…
Interview experiences · Supermicro
Software Engineer interview at Supermicro: virtual loop
I started with a recruiter screen, then completed an online assessment before a virtual loop with several interviewers. Each conversation blended technical material with Amazon Leadership Principles. The coding was DSA-heavy: I had to contrast brute-force and optimal approaches, explain time and space complexity, and work through a sliding-window problem systematically instead of rushing to code.…
Interview experiences · Swiggy
Software Engineer interview at Swiggy
My process began with one very quick technical screen. I was asked only the Two Sum problem, which I solved in roughly five minutes, so the interview itself did not feel stressful or complicated. After that, the process went quiet. There were no follow-up rounds and no meaningful updates or timeline. Months passed without closure, which felt unprofessional, especially after such a clean first ste…
Interview experiences · Systems Planning and Analysis
Software Engineer interview at Systems Planning and Analysis
This process was much heavier than I expected. It began with a recruiter phone call, then an HR phone interview, followed by a video meeting with the manager. Later I attended an in-person meeting with both the manager and HR, and completed an English test. The process took time and offered little clarity between steps. It ended in rejection, communicated through automated-looking emails that did…
Interview experiences · Tesla
Software Engineer interview at Tesla: gasket tolerance
Before the interview, I completed and submitted a take-home test. The interview then opened with a problem that sounded simple, involving a gasket and an L bracket compressing that gasket. The interviewer treated it as straightforward, but I overthought the calculation and missed the correct tolerance limit. The subject itself was not complicated. The precision of the calculation was what mattere…
Interview experiences · Thales
Software Engineer interview at Thales
A phone conversation led quickly to a one-hour video call. The recruiter mainly checked whether I was still seeking a role and could relocate if necessary. The video call combined motivation questions with technical discussion. It was not a hands-on exercise; it was a conversation about my reasoning and the way I described my background. The difficulty was average for me, neither impossible nor p…
Interview experiences · The Walt Disney
Software Engineer interview at The Walt Disney
The recruiter first discussed my interests and location fit. I understood that some versions of the role might have two rounds, one easy-to-medium LeetCode problem and a hiring-manager round, but my own path was recruiter first and then a technical-and-fit discussion with an engineer or hiring manager. I had a recruiter video screen, a hiring-manager video interview, an in-person office technical…
Interview experiences · Tiger Analytics
Software Engineer interview at Tiger Analytics
The technical questions leaned toward data engineering. I had two technical rounds on Python and PySpark coding, moderate-difficulty DSA, and Azure Data Factory, so I had to discuss data workflows as well as algorithms. The questioning sometimes moved quickly and felt argument-driven. I did not feel I had much time to write or iterate on query-like work, which made it harder to show the backend d…
Interview experiences · TikTok
Software Engineer interview at TikTok
The recruiter gave me a broad sense of the role and scheduled the interviews, but I could not get much detail about the topics or how many stages remained. HR replied quickly, yet the process structure stayed unclear. The first technical stage was a LeetCode question. A later combined stage included technical discussion plus another LeetCode problem. Once interviewing started, things moved along,…
Interview experiences · TSMC
Software Engineer interview at TSMC: presentation follow-ups
I began with a self-introduction presentation of about ten minutes. My supervisor asked questions from what I presented and sometimes interrupted, so I had to respond in real time rather than treat the presentation as a formality. The team then explained its work and responsibilities, and I was able to ask questions. The process felt structured and respectful. Its main challenge was handling acti…
Interview experiences · Visa
Software Engineer interview at Visa
Visa began in a standard way with an OA and then technical rounds. In CodeSignal Round 1, I had a medium array problem, a deep resume discussion, Docker and Kubernetes questions, and basic database-query material. Round 2 was more coding-heavy and asked me to implement an LRU cache. I got working LRU-cache code, but the interview ended around the 50-minute mark, leaving expected material uncovere…
Interview experiences · Volkswagen Group Italia
Software Engineer interview at Volkswagen Group Italia
My Software Engineer process had three rounds: HR first, then an account manager associated with the client, followed by a client-side interview panel. The final panel was the last checkpoint before the process wrapped up. The sequence was smooth and simple. I never found it chaotic or overly complicated, and each step followed naturally from the last. I cannot speak to how other roles work, but…
Interview experiences · Volkswagen Group Italia
Software Engineer interview at Volkswagen Group Italia: offer timeline
My process had several stages and moved more slowly than I expected. I went through two technical discussions, then final document verification and a salary conversation. It eventually became an offer-acceptance process, and I received an offer letter. The surprising part was timing. More than three weeks passed before I joined the organization after accepting. The paperwork did move forward, but…
Interview experiences · Zensar Technologies
Software Engineer interview at Zensar Technologies: unexpected technical round
The first technical interview was professional and covered .NET fundamentals and cloud basics. A later round was described as casual and HR-like but arrived as an unannounced technical-heavy interview. The interviewer felt rude and impatient, and the questions seemed limited to that person's own expertise rather than a fair view of what I could contribute. HR later ended communication by saying t…
Interview experiences · ZF Group
Software Engineer interview at ZF Group: behavioral manager discussion
I first had a recruiter phone screen focused on my background and whether I was genuinely aligned with the role. It was more about getting to know me than technical grilling. The manager interview used STAR-style behavioral questions, with a couple of light technical trivia questions as a change of pace. The experience was smooth, and I received an offer. The format suited the role because it put…
Interview experiences
Software Engineer Interview Experience — AI-Assisted Coding and a Task-Scheduler Design
The report covers three consecutive onsite sessions: AI-assisted coding, behavioral discussion, and system design. The coding task involved a worker consuming queued jobs, retrying failures with increasing delays, and diverting repeatedly unsuccessful jobs. Although the author considered the underlying problem simple, they struggled to understand the interviewer’s expectations. The interviewer ex…
Interview experiences
Software Engineer Interview Experience — Reassessing AI-Assisted Debugging After Rejection
The author reflects on rejection after a five-round onsite, following an earlier interview. Recruiter feedback identified shortcomings in both design and AI coding. The account concentrates on a 45-minute CoderPad session using a codebase of several hundred lines, with tasks revealed sequentially. Remembered work included filtering logs by severity, writing unit tests, and batching logs over five…
Interview experiences
Software Engineer Interview Experience — Reported Spreadsheet Variants Across Ten Companies
The author brings together 31 interview reports involving ten companies, including OpenAI and Harvey, to compare spreadsheet implementation questions. The compilation covers basic cell access, formulas, dependency updates, circular references, and the choice between calculating values during reads or maintaining cached results during writes. It attributes different extensions to different employe…
Interview experiences · Sogeti
Sogeti Consultant interview: coaching calls and an impersonal panel
After I applied, the recruiter contacted me quickly and sounded genuinely excited, almost surprised that no one had hired me already. We covered my MSP background and my mail-migration work, including how I ran projects from kickoff through implementation and the post-implementation survey. A week later I followed up because nothing had arrived, and soon after that a panel interview was scheduled…