READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 119 of 153
Interview experiences · SIG
SIG Software Engineer Interview Experience — Nailed Every Onsite Question, Still Got Rejected
In May, someone from SIG reached out, so I figured I'd give it a shot and set up a recruiter call, which quickly turned into a phone interview. The phone interview was the classic "movie search" problem — basically you're given a CSV-format list of movies and asked to design a class that supports fast filtering, like pulling movies from year xx to year yy. Also, the constructor's time complexity…
Interview experiences · Sigmoid Analytics
Sigmoid Analytics Software Engineer Interview Experience: two incompatible reported accounts
This source describes two different experiences and does not present them as one combined story. One reportedly ended badly during culture fit, with negative HR feedback and unclear hiring status. The other was a four-round process involving Java, Spring Boot, multithreading, and managerial project discussion. The source expressly says the feel and content are too different to synthesize into a s…
Interview experiences · Sii Group Italy
Sii Group Italy Software Engineer interview: a fast client-project process
The process was fast and strongly oriented around the assignment. I started with a conversation with a business manager or sales representative. The next day I had a technical interview, followed immediately by another step that moved very quickly. The format surprised me because it was so conventional: direct questions centered on the role. The role was tied to a client project, but I did not ha…
Interview experiences · Sii Group Italy
Sii Group Italy Software Engineer interview: client preparation
A recruiter contacted me on LinkedIn, and the first steps moved quickly. After an HR interview, I spoke with several business managers who handled group work for different clients. The conversations helped me understand the assignments and what they expected. I then had a client-side technical interview after preparing with a business manager who knew the client's way of working. That preparation…
Interview experiences · Sii Netherlands
Sii Netherlands Software Engineer interview: prepared client discussion
A LinkedIn recruiter contacted me, and the first conversations moved quickly. After the HR interview, I met several business managers who each covered SII activity with different clients. The technical conversation happened on the client side. A business manager who knew the environment and client prepared me for it, which took away the feeling that I would have to improvise and let me feel comfo…
Interview experiences · Sii Netherlands
Sii Netherlands Software Engineer interview: technical interview and quick offer
I had a very fast hiring process. First came an interview with a sales representative or business manager. The next day I had a technical interview, and by the day after that I already had an offer. The content itself was fairly conventional. What surprised me was that the role was for an external-client project, so I did not have to complete the client interview that often appears in these proce…
Interview experiences · Silicon Labs
Silicon Labs Software Engineer interview: three online technical rounds
My biggest frustration was the way HR handled scheduling and communication. The follow-up felt ego-driven, and they kept pushing me to drop my application instead of giving a clear, consistent process. I learned that the second interview would take a long continuous block, around three hours with multiple hiring managers. The plan kept changing, and I was only called for the interview after a mon…
Interview experiences · Silicon Labs
Silicon Labs Software Engineer interview: unstable connection and scheduling breakdowns
My experience started with a scheduling mess and became an uncomfortable call. I told HR in advance that I would be overseas and might have an unstable connection because I would need a VPN. The first part of the interview was choppy, although it eventually stabilized. I could not shake how the hiring manager reacted. They seemed visibly impatient and annoyed throughout, and when I asked question…
Interview experiences · Nutanix
Site Reliability Engineer interview at Nutanix: interview experience
The technical interview was grounded in SRE essentials. I was asked about Linux commands, virtualization, operating-system and computer-network concepts, as well as my resume and projects. The questions kept returning to core computing knowledge rather than anything flashy. The overall difficulty felt average, but it still tested whether my knowledge was solid. I made some mistakes because I was…
Interview experiences · SIXT
SIXT Software Engineer interview: campus DSA cutoff
The campus drive began with an online assessment containing two medium LeetCode-style coding questions. About 20 of roughly 150 students were shortlisted for interviews. My first technical round covered time and space complexity and a medium dynamic-programming LeetCode problem. I did not make it past that first technical interview. Candidates who did move on had a second interview, and a smaller…
Interview experiences · Skechers
Skechers Account Executive interview: pen pitch and shoe role-play
The online group interview was about sales and presentation. We took turns answering questions about the company and product, and I had to sell a product in front of the group. One prompt asked for a quick pitch, about half a minute, to sell a pen. I also did a role-play as a customer and sales associate to sell a shoe, plus a sheet of situation questions. The content was not hard, but being put…
Interview experiences · Skechers USA
Skechers USA Account Executive interview: group product discussion
My interview was online and uncomplicated. I was in a group with four other people, and we talked about the company and how to sell a product. It was practical and did not feel technical. The only preparation that seemed useful was getting a quick sense of the company background before the conversation. Everyone followed the same general format, which made it easy to understand. I did not find it…
Interview experiences · Slalom
Slalom Consultant interview: friend referral and quick conversational process
My first conversation with Slalom came through a friend connection, so it started informally and felt friendly. They were flexible about my availability, and that tone carried into scheduling. It took less than a week to move from outreach to a real meeting, and the recruiter followed up at the exact time we had agreed on. The interviews were conversational rather than interrogation-style. They m…
Interview experiences · Slalom
Slalom Consultant interview: respectful salary mismatch
After the recruiter contact, I had a technical and consulting-oriented screen about my prior work, difficulties I had faced, and how I handled them. The questions were standard for consulting, but the recruiter clearly connected them to the role's technical side and to how candidates fit different pay bands. The process respected my time. After the technical conversation, it became clear that the…
Interview experiences · Slalom
Slalom Software Engineer interview: senior role, design and in-person behavioral round
I started with a 30-minute Microsoft Teams recruiter call about my background and fit for a Senior Software Engineer role. It was straightforward and warm. The technical interview then covered my experience, projects, and technical decisions. The next stage was system design, where I designed a solution, did hands-on coding and modeling, and discussed trade-offs. The final stage was an in-person…
Interview experiences · SLB
SLB Full Stack Engineer interview: puzzle, project discussion, DSA, and design
My process opened with a general HR-style introduction and then moved into technical rounds. The first technical round was light, with a basic puzzle that felt more like a check on how I think than a demand for deep mastery. A project discussion followed and became a standard conversation about explaining my work clearly. The next technical round shifted to medium-level DSA with basic system desi…
Interview experiences · SLB
SLB Software Engineer interview experience: English exam and engineer interview
The process opened with an English exam and a basic logic and math check on a platform. Everything in the test was in English. Passing it was a clear gate, after which the process became an interview rather than another assessment. I then had about a half-hour interview with an engineer. I only learned whether I would move to the second round after that conversation, so there was little room to r…
Interview experiences · SLB
SLB Software Engineer interview: fit discussion and portal English evaluation
After a recruiter-style conversation, I met with HR and then a manager or mentor. The process felt friendly and focused on the material I had already shared against the job description, especially whether my experience fit what they needed. I also completed an English evaluation through a portal, so it did not really test speaking. The role was in Digital and Integration, which was described as a…
Interview experiences · SLB
SLB Software Engineer interview: Java concepts and linked lists
The technical interview focused on Java concepts and data-structures fundamentals. I was asked about OOP, including the idea behind an "oops" concept and what variables to declare when creating an object. There were also linked-list questions. The questions were not presented as tricks. They tested whether my everyday Java knowledge and core data-structures understanding were really there. The qu…
Interview experiences · Smartsheet
Smartsheet Account Executive: dry, transactional recruiter meeting
I went into the recruiter-stage meeting expecting something more thoughtful, but it was oddly dry and transactional. It felt like someone was just ticking boxes. There wasn't much back-and-forth or emotional engagement, and I didn't feel like the interviewer was listening so much as running through a script. That gave me a pretty negative impression from the start. As I thought more about what I'…
Interview experiences · Smartsheet
Smartsheet Account Executive interview: concern about being "a thread"
My process started with an interview with the line manager. I then met with an EMEA sales manager and sat down with a colleague. The early rounds felt straightforward, and I got the sense they were trying to understand my experience and whether I'd fit the team. The tone was casual, with more discussion about where I'd worked and what I'd done than any kind of tricky assessment. The colleague rou…
Interview experiences · Smartsheet
Smartsheet Software Engineer: 15-minute HR screen on high-traffic systems
My first step was a short HR screening that lasted about 15 minutes. It came through a referral, and the conversation stayed focused on my background rather than puzzles. I talked about what I was doing on my current project, the technology stack I'd used, and how I handled scale and high-traffic situations. The questions were straightforward: what I was responsible for day to day, which tools an…
Interview experiences · Smartsheet
Smartsheet Software Engineer interview: Roman-to-integer coding and outage-detector design
After the recruiter reached out through LinkedIn, the timeline was straightforward. I was scheduled for a coding round and a design round as part of the Senior Software Engineer process, and I completed them back-to-back. The recruiter arranged the calls and kept the scheduling moving. For coding, I solved a Roman-to-integer style problem. The design question was an outage detector modeled after…
Interview experiences · Smartsheet
Smartsheet Software Engineer interview: two live coding sessions and an engineer loop
Recruiter outreach led to a drawn-out process with three interviews over about a month and a half. The overall mood stayed relaxed, which helped because the process still involved several stages. I first had an HR-related screening call, then two live coding sessions. Those coding sessions were the main technical hurdle before I could move forward. After I cleared them, I was invited to a loop in…