READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 47 of 153
Interview experiences · Charta Health
Charta Health Software Engineer Interview Experience — Phone Screen and Four Onsite Rounds
Technical Phone Screen Rate limiter. Onsite Round 1: Coding Given a node, find its in-order successor. The description of the successor was the node with the smallest value among all nodes whose values are greater than the given node's value. Round 2: System Design Design a system that generates the corresponding output for a given input. Similar inputs should also be able to generate the same ou…
Interview experiences · Checkout
Checkout Software Engineer interview with system design and values
I had a smooth sequence of rounds that felt more like conversation than a test. The stages moved quickly, and everyone I met was especially friendly. The route was HR first, then a hiring-manager discussion about my background and experience. After that came a system design interview and a values interview. The overall difficulty felt average, while the tone made it easier to explain my thinking…
Interview experiences · Chicago Trading Company
Chicago Software Engineer Interview Experience — Three Rounds Ending in a Deep C++ Concurrency Grill
Round 1: Dual Behavioral Interview — Communication & Continuous Improvement Round 2: C++ Data Structures & Algorithms Question 1 Simple Moving Average (Sliding Window) Implement a class that computes the Simple Moving Average (SMA) over a fixed-size sliding window. The class should support the following APIs: Requirements: The constructor takes the window size N. Calling add(int sample) inserts a…
Interview experiences · Chime
Chime Data Scientist Interview Experience — A Schema-less SQL Retention Question in the HM Screen
The first round was just a recruiter screen — they asked roughly about what I'd worked on before. The second round was the HM screen. They changed the process this year: the first round is now a one-hour session split into two parts, 30 minutes chatting about my background and 30 minutes writing SQL. Their SQL question was a format I hadn't run into before — they only gave two tables: users and t…
Interview experiences · Chime
Chime Data Scientist Interview Experience — SQL and a Business Case in One Technical Screen
This round is split into two parts: one hour of SQL and one hour of a case study. SQL: They give you a transaction table and a user table. If you're fast you'll probably get through 5-6 questions. The time field is a timestamp, so you need to use date_trunc to handle it. The first few questions are pretty basic and you can knock them out with a few CTEs. It involves several window functions like…
Interview experiences · Chime
Chime Product Manager interview: five rounds with case panels
I remember this process as an intense stretch. I spoke with a lot of people, and every round took real mental effort. It included a recruiter screen, a hiring manager conversation, and two full rounds of panel interviews, for five rounds altogether. The panels were demanding, with case-focused sessions in each one, and the final step was a conversation at the CPO level. The hiring manager experie…
Interview experiences · Chime
Chime Product Manager interview: intensive loop and missing recruiter follow-up
I started with a recruiter screen that felt fast and responsive. After meeting the hiring manager, the pace stayed high. I was moved into the next round on such a tight timeline that they wanted me to begin the technical interview before I had much chance to prepare. After that second round, the process went quiet. I followed up, got no reply from the recruiter, then received a standard rejection…
Interview experiences · Chime
Chime Product Manager interview: organizational structure, emerging technologies, and case study
Round 1 set the tone quickly with three interviews. I started with a conversation about organizational structure, then worked through an emerging technologies prompt that required me to generate many ideas and prioritize them. The third part was a case study that felt designed to test how I’d turn my thinking into decisions. The part I remember most is how concentrated and targeted that first sta…
Interview experiences · Chime
Chime Product Manager interview with two panels and a 90-minute PRD exercise
My process moved quickly once it started, but the bar felt high and a few details didn't land the way I expected. I went through a recruiter screen, then a hiring director conversation, followed by two panel interviews. The first panel went reasonably well, and I got good feedback. The second was rougher for me. There was also a PRD writing exercise that took about 90 minutes, although it sounded…
Interview experiences · Chime
Chime Software Engineer interview: basic SQL without window functions
I interviewed for a data engineering-oriented SDE role where the questions were unusually basic. They focused on my past work and simpler algorithm and SQL knowledge. The recruiter screen covered my background and how it matched the role. The technical portion covered SQL and algorithms. The SQL questions were very basic and explicitly did not include window functions. The algorithm problems lean…
Interview experiences · Chime
Chime Software Engineer Interview Experience — Two Back-to-Back Phone Screens, Rejected for Pipeline Fit
A recruiter reached out. I looked up the company online and felt the culture seemed okay, so I went ahead and interviewed. The recruiter call was just casual chatting, and we quickly landed on an interview time. I hadn't grinded LeetCode in a long time so I was a little worried, so I scheduled the phone screen slot for two weeks out and started grinding through interview experience posts. In the…
Interview experiences · Chime
Chime Software Engineer interview: React and JavaScript component task
I faced a front-end-focused technical challenge centered on building React/JavaScript components and implementing the data logic behind them. In the first round, I worked in a shared virtual environment to create components in a React/JS app. The components had to render data, and I had to implement the logic that processed the data before rendering. The UI scaffold was already provided. The diff…
Interview experiences · Chime
Chime Software Engineer interview with a complex game-design question
I had a difficult start when a phone screen turned into an extremely complex game-design question that I couldn't get clear enough to understand. The recruiter call came first. During the technical phone screen, I was asked to design a game with complicated rules. The interviewer struggled to explain how the game worked, and the prompt felt unrealistic without prior knowledge. I didn't make it to…
Interview experiences · Chime
Chime Software Engineer interview with coding, system design, and manager rounds
I went through a fairly standard Software Engineer process at Chime, with a recruiter conversation followed by coding, system design, manager, and product-style rounds. The difficulty was mostly average, although I had mixed feelings about how clearly some interviewers ran their sessions. The recruiter screen was a phone call about my background, the role, and expectations. The technical intervie…
Interview experiences · CIBC
CIBC Software Engineer interview experience
I first spoke on Microsoft Teams with the recruiter and a senior manager. That conversation felt straightforward. I then had an in-person round in downtown Toronto, including whiteboard work where I used simple if statements to talk through the logic and how I would approach the problems. I was surprised that there was no live coding. The emphasis was on laying out my thinking clearly in front of…
Interview experiences · Circle Internet Financial
Circle Internet Financial Frontend Engineer interview with CodeSignal, system design, and Go
I went through an assessment-heavy process with several technical stages, but I didn't move forward. One path involved a small take-home assessment with two questions. I didn't proceed after that initial stage. Another included a CodeSignal test, followed by a roughly 30-minute recruiter call covering Circle, culture, and crypto-related knowledge. That path continued with a system-design discussi…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer: CodeSignal, 5 to 7 hour take-home, and final interviews
I went through a harder, test-heavy process for a Software Engineer role involving CodeSignal and longer take-home work. It ultimately didn't lead to an offer. The online assessment was proctored through CodeSignal and consisted of timed questions. In one case, I had to complete it within a fixed window and received a rejection shortly afterward. I also encountered take-home coding work described…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer, CodeSignal and Flask booking app
I went through a multi-stage technical process that felt difficult, and one version was held back by the quality of the interviews. I was told the pipeline included an online assessment, an HR interview, technical interviews with an engineering manager and senior engineer, another engineering manager interview from a different office, and finally a VP interview. Another account described a CodeSi…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer: CodeSignal verification and timing problems
I went through several coding-gated processes where logistics, timing, or platform trust issues affected my candidacy. One take-home CodeSignal evaluation had four steps, and I completed most of it. CodeSignal invalidated the assessment because of suspected copying or screen-sharing behavior. After receiving an online assessment invitation in another process, I waited weeks to hear from a recruit…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer interview ending after CodeSignal
I interviewed for Software Engineer and went through only part of the process. The early assessments were the main focus, followed by either silence or no further interviews. The first step was an Online Assessment through CodeSignal. It was timed, and in one case there was an additional assessment. The questions weren’t strictly classic LeetCode-style. After the assessment, I either spoke briefl…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer interview: six-week wait after an OA
I ran into a long process where timing and recruiter follow-through became the deciding factors. I completed an online technical assessment that took more than an hour, then waited about six weeks before a recruiter reached out. The recruiter mainly focused on why I wanted to work at Circle. After another two weeks, I received a generic rejection email, even though I had scored 100% on the coding…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer interview: stalled after coding screens
I applied for the Software Engineer role and got caught in a mid-process cycle of one or two online coding assessments, sometimes followed by a conversation, without a consistent path to later interviews. I was sent one or more timed coding challenges through CodeSignal and/or HackerRank, including HackerRank-style tasks. In a few cases, I had a recruiter conversation after the assessment, but it…
Interview experiences · Circle Internet Financial
Circle Internet Financial Software Engineer: pairing directions wasted time
I went through a recruiter and assessment process followed by design, coding, pairing, and behavioral interviews. In the pair-programming portion, I felt the interviewer gave partially incorrect directions, which wasted a large part of the time. After CodeSignal, I had a behavioral and fit round. We discussed what interested me in Circle, my projects, and how I acted under pressure rather than te…
Interview experiences · Circle
Circle Online Assessment Interview Experience — A Recipe Storage CRUD Question with Rules Hidden in the Test Cases
I got unlucky — I'd spent a long time studying the bank system and file system problems, and then a brand new question showed up. The question was to design a recipe storage system. Each recipe has a name, a list of ingredients, and a list of steps. First question (I didn't even pass this one, so this is all I have): design the four CRUD methods for this system. The main thing was that the test c…