READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 121 of 153
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — A Trie Backtracking Bug I Never Fixed
First round: the interviewer — I really feel bad, she kept trying to help me the whole time, but in the end I still didn't get the bug fixed within the hour. The input is a string array: [California, California/San Francisco, California/San Francisco/7th Street], etc. The other input is an array of the nodes to delete, e.g. [California/San Francisco], and the return should be [California]. LeetCo…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — A Vague Distributed Tree Counting Design Problem
Phone Screen 1 The interviewer gave me a distributed tree counting problem that took me a while to even understand. There was no starter code or example — he just said to imagine tree nodes distributed across different places on a network, and my job was to design a class to accomplish that. The problem was way too vague at the start, and we spent a long time discussing what exactly he wanted. I…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Binary Search on Error Logs, Then a Graph BFS/DFS Follow-up
A classic problem in application-question form. Binary Search The input is a log history. There are three kinds of logs: Info, Warn, and Error, and each log starts with its own type — for example, an Info-type log looks like "[Info] ...". The log history follows two patterns: Once an Error shows up, the service is down, and every log after that is also Error. The first Error is always preceded by…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Log Binary Search With Two Graph Follow-ups
A classic problem in applied-problem form. Binary Search The input is a log history. There are three types of logs: Info, Warn, and Error, and each log line starts with its own type — for example an Info log looks like "[Info] ...". The log history follows two patterns: Once an Error shows up, the service goes down, and every log after that is Error The log right before the first Error is always…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Onsite Coding and Job Scheduler System Design, No Offer
Coding: this was an OO design problem I hadn't seen anywhere on the forum before, implementing two functions. One function is addTask(taskId, priority, timestamp) — the same task can be added multiple times at different timestamps. The other is executeTask(), which is the tricky part — you first sort by priority, and if a task has already been executed, you skip it. System design: job scheduler.…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Rate Limiter and N-ary Tree Rounds, No DP Allowed
3 YOE, mid-level. After talking with the HM, there were two phone screens, and they were still pretty hard. Coding 1 Design a rate limiter. Just one rule Multiple rules Is it thread-safe, and how would you make it thread-safe (lock) If the request handler throws an exception for a given request, that request shouldn't be counted Don't drop the other rate-limited requests — when there's spare capa…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Rate Limiter in CoderPad, Ran Out of Time Before the Distributed Follow-up
Snowflake phone screen, one hour, writing Python in CoderPad, and I was allowed to use AI. The recruiter said this round looks at how you ask about requirements, how you test, and how you debug. [Question] Build a rate limiting service. Different clients can have different rate limit tiers, for example free, pro and enterprise. The limits for each tier can be updated at runtime without restarting…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Tree Deletions and Four-in-a-Row Detection
The author reports two Snowflake coding interviews, each lasting about an hour in an executable editor without AI assistance. The sessions included introductions or project discussion, technical work, and time for questions. The first round examined a multi-child tree where deleting a node promotes its children rather than removing its entire subtree. The initial task asked for the resulting heig…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Two Coding Phone Screens and a Quick Rejection
Both rounds of my coding phone screens were with interviewers from the company's tagged LeetCode question set. I'd recommend grinding more LeetCode before you go in. The first round was LC 210 style — directed graph topological sort. Not much to say about the problem itself, except I had to write my own test cases. The interviewer for this round didn't seem to be feeling well — she was coughing a…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Two Coding Rounds and Four Problems
IC1 phone screen, with two coding rounds. The interviewers were all very nice. I hope they will show mercy and let me pass. 🙏 Here is the timeline as well: 8/3: Referral 8/4: Scheduled the HR call 8/7: HR call, then the interview was scheduled that same day 9/3: Virtual onsite with two rounds First round: Question 1: Throne Inheritance. The only difference was that init did not provide the king.…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Two Onsite Coding Rounds, Rejected Over a Tricky Input Assumption
Two onsite rounds, mid-level, both coding. Both rounds were repeat questions I'd seen before, but they happened to be from the few I hadn't practiced. A bit unlucky. Overall the interview experience was fine — the interviewers were all nice, and they asked me a lot about how I use AI in my day-to-day developing cycle. Wiki Hopper — basically a webpage has multiple links that let you jump to other…
Interview experiences · Snowflake
Snowflake Software Engineer Interview Experience — Two Phone Screens, DAG Coding and a Control Plane Design
Two phone screens, one coding and one system design. The coding question was a "privilege" problem that is already on the forum (the DAG allow/disallow letters one). The difference in the requirements was that each node passes down its own final state to its children, instead of passing allow and disallow separately. I propagated in topological order, and at each step every node computes its late…
Interview experiences · Société Générale
Société Générale Software Engineer Interview Experience: concurrency and the Saga pattern
The interview focused on technical questions about concurrency and reliability. The interviewer asked about multithreading, including deadlock and livelock, then pushed me to reason through how I would resolve several multithreading exercises. The conversation also covered microservices, particularly the Saga pattern and fault tolerance. It was more about working through system behavior than reme…
Interview experiences · Société Générale
Société Générale Software Engineer Interview Experience: Git, Java, and Spring Boot scenarios
The interview began like other technical discussions. I introduced myself, explained the domain I had worked in, and talked about projects I wanted to showcase. The interviewer then moved to scenario-based questions tied to engineering foundations. The questions covered Git, Java, and Spring Boot. They stayed grounded in practical work instead of only theory. The difficulty was average, and it di…
Interview experiences · Société Générale
Société Générale Software Engineer Interview Experience: PHP and Angular technical rounds
My process opened with a recruiter-style conversation where I introduced myself and talked through my background. Then I had two technical rounds, a first and second level, focused on my projects and problem solving, with a strong emphasis on PHP and Angular. The interviewers also asked about APIs, databases, and application architecture. In the first technical round, I started with an introducti…
Interview experiences · Société Générale
Société Générale Software Engineer interview with WinForms mismatch
I went through a short, fast-moving process centered on a hiring-manager discussion and a coding session. The manager round covered my past experience, then I had an objective-oriented coding exercise rather than a usual LeetCode-style problem. There was also an HR call afterward that felt separate from the main loop. What stayed with me was the gap between the technical conversation and my expec…
Interview experiences · Socure
Socure Software Engineer Interview Experience — Designing Twitter for Timeline Scale and High Availability
Interview question: Design Twitter. This was a system design question, and the overall task was simply to design Twitter/X. They first asked about the basic functional requirements: Create an account Let users post tweets Follow and unfollow users View the home timeline Like and retweet Comment View trending or popular tweets Then they asked me to draw the overall architecture and the core entiti…
Interview experiences · Socure
Socure Software Engineer Interview Experience — Payment Queue Visibility Timeouts and Concurrency Races
Backend/SDE Coding I recently interviewed for a Backend/SDE role. The coding problem leaned toward backend work and concurrency. The problem was to implement an in-memory payment queue providing submit, receive, and ack. Requirements: submit adds a message. receive gets the next message. After a message is received, other consumers cannot get it during the visibility timeout. ack deletes it. If t…
Interview experiences · SoFi
SoFi Full Stack Engineer panel interview experience
I started with a standard recruiter phone screen that moved quickly. A third-party technical screen focused on JavaScript, and I entered the main interviews expecting coding and role-relevant evaluation. The next step was a packed panel. It included Algorithms and Data Structures, a React frontend discussion, and system design. I also met with a hiring manager to discuss how I worked and approach…
Interview experiences · SoFi
SoFi Software Engineer Interview Experience — Four Rounds, Rejected on the Second Attempt
This was my second time trying to get into SoFi. This time I interviewed with the Invest team. I thought the conversations went well, but I still got rejected. The market really is brutal right now. There were 4 rounds total: a phone screen plus three virtual onsite (VO) rounds. Phone screen: OOD principles, and implementing a multi-threaded task executor. I was given a class TaskExecutor that im…
Interview experiences · SoFi
SoFi Software Engineer interview experience: graph traversal and backtracking
The process felt smooth from the start. The coding screen included a graph-traversal-style question, followed by technical rounds built around familiar problem-solving patterns. One involved generating permutations with backtracking; another asked me to rearrange an array for a prefix-sum-style objective. The rounds were practical and direct. I had room to explain my thinking instead of dealing w…
Interview experiences · SoFi
SoFi Software Engineer Interview Experience — Positive Feedback, Then Strung Along
Let me start with the outcome: I interviewed at SoFi in June, and everything from the phone screen to the onsite moved very fast. In the end the recruiter even said it was positive — and then they started stringing me along. The onsite had 3 rounds: React: write a standard CRUD table System Design: design a suggestion system The HM round covered my past experience, debugging, and a random API des…
Interview experiences · Softtek
Softtek Software Engineer interview: explaining a program and its requirements
The interview felt focused and demanding. The interviewer had a long professional background and seemed interested in how I reasoned through the problem. I was asked to explain a written program in detail and show how I'd understood the prompt. I needed to break down what was happening, why the approach made sense and how I interpreted the requirements. The level of detail made the conversation d…
Interview experiences · AMD
Software Engineer at AMD: computer architecture and UVM questions
I went through a technical-focused interview that leaned heavily into computer architecture and verification. I was asked about UART, SPI, and I2C, including how those topics connect to the bigger picture. We also covered object-oriented programming and verification languages and concepts such as UVM. The discussion then moved to bus protocols including APB, AHB, and AXI, followed by coverage, as…