READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 63 of 153
Interview experiences · FIRSTNET GLOBAL
FIRSTNET GLOBAL Account Executive interview experience: sell-a-simple-item prompt
The interview was direct, and I appreciated that. They asked about my best and worst scenarios at work: how I got into each situation, what I did to handle the challenge, and what I did next once things improved. They also asked me to show sales skill in a practical way. I was put on the spot and asked to sell a simple item. They wanted specifics about the pitch and how I would talk through it as…
Interview experiences · FIRSTNET GLOBAL
FIRSTNET GLOBAL Software Engineer Interview: Project work and behavioral questions
I applied online and then completed a pre-employment assessment. The next steps included a phone screen, a technical round, and a behavioral round. The process kept returning to my project work: what I built, the challenges I ran into, and the people side of teamwork. The behavioral questions covered teamwork, conflict, and communication under pressure. The difficulty did not feel extreme. It see…
Interview experiences · Fivetran
Fivetran Software Engineer Interview Experience — dbt Labs Team, Stumped by a SQL Engine Disk-Write Question
Fivetran acquired dbt Labs, and this position is under dbt Labs. HR call, pretty standard, just collecting background - 30 min HM call, introduced how the team is set up, standard behavioral questions - 1 hour System design: design a simplified version of WhatsApp. I felt the interviewer's level was just so-so — he was still getting stuck on RDBMS vs NoSQL differences, that kind of old-school que…
Interview experiences · Flatiron Health
Flatiron Health Data Analyst Interview Experience — Passed Coding, Cut on the Final Case Round
Let me share a DA interview. I signed an NDA so I won't go into detail. From what I've seen on the forum, it feels like nobody has ever gotten an offer from this one... so I didn't have very high hopes going in, and sure enough, that's how it went. First was the Karat screen: they tested SQL, R, and some statistics knowledge. A week later I got the invite for the first round. Round 1: they asked…
Interview experiences · Flexport
Flexport Software Engineer Interview Experience — Onsite Word-Guessing Algorithm Question, No Offer
This year, all the onsite questions were new ones -- job hunting is really tough this year. Hoping this helps other people who are also job hunting. Phone screen: an algorithm question. Given a bunch of meeting start and end times, output the total time spent, counting any overlaps only once. Follow-up: if there's overlap, you'd need multiple meeting rooms -- find the minimum number of meeting ro…
Interview experiences · FNZ
FNZ Business Analyst interview: promised offer and lost follow-through
My experience with FNZ felt less like a clean interview and more like a process that drifted after I had already done the work. I made it through multiple rounds, technical and HR, and the recruiter collected documents and told me that an offer letter would be released. It looked as if things were moving forward. Then communication disappeared. I waited, followed up, and did not get the transpare…
Interview experiences · Fora Travel
Fora Travel Software Engineer Interview Experience — Coding, System Design, and API Design in One Technical Screen
Coding The question was pretty simple: Q: Given two unsorted integer arrays a and b, where a has enough placeholder positions at the end to hold all elements of b, merge b into a and sort the final array in ascending order. Example: Additional constraints: Both a and b are unsorted a has enough placeholder positions at the end to hold b The final result needs to be placed in a There was no explic…
Interview experiences · Ford Hospital and Research center
Ford Hospital and Research center Software Engineer interview: a long timeline
The hardest part was the timeline. About three months passed between my application and the rejection email, and the process kept changing as it went. I started with a recruiter discussion and then a brief meeting with the hiring manager. Next came a panel with the hiring manager and two engineers. They later brought me in person for another interview, returned to my resume, and had me solve prob…
Interview experiences · Ford Hospital and Research center
Ford Hospital and Research center Software Engineer Interview Experience: one virtual panel with decision-making follow-ups
The process was direct: a short recruiter call followed by a single virtual panel interview lasting about an hour. The panel mixed technical questions about work I had done with behavioral prompts. They seemed especially interested in how I made decisions, rather than only in what I had done. The experience was structured and not overly drawn out. The depth came through follow-up questions. When…
Interview experiences · Palantir
Forward-Deployed Engineer interview at Palantir: collaborative debugging
After I applied, a recruiter reached out and the process moved quickly into a technical conversation. I expected the recruiter to conduct the early screen, but an engineer joined instead. The exchange felt collaborative: I could ask questions, explain my thinking, and offer different approaches. The technical work was mostly coding and problem solving. One session was a straightforward LeetCode-l…
Interview experiences · Fragomen
Fragomen Consultant interview: written assessment and same-day offer
I began with a friendly HR call about logistics and my background. Soon after, I completed a written assessment with plenty of time, so it felt more like a check than a trap. I then had two interviews with team staff. They were relaxed but role-related, and the interviewers kept even the challenging parts supportive. I felt they were trying to understand how I would work rather than score points.…
Interview experiences · Freddie Mac
Freddie Mac Interview Experience — Four Rounds and a Hiring Freeze at the Finish Line
Giving back to the forum with a (relatively) fresh interview report for what feels like a cushy, stable place to ride out a career — Freddie Mac. The process dragged out for a while, four rounds total (not counting the HR call, otherwise it's five)... In the end, because Trump took office and FHFA got completely reshuffled, the whole thing got swept off the table and I got the pleasure of a hirin…
Interview experiences
Frontend Engineer Interview Experience — A Multi-Company Search Ending in a Profound Offer
The author relays a friend’s 2026 frontend interview search across multiple companies. Reported exercises included notification systems, live comments, typeahead interfaces, forms, file editing, and collaborative documents. The account contrasts companies’ emphasis on visual fidelity, full-stack knowledge, project management, and system design. The friend found Databricks slow to schedule, apprec…
Interview experiences · Act Digital
Full Stack Engineer interview at Act Digital: quick start and no closure
The process began with a relaxed HR conversation about my background and resume. Since the role was tied to a client through a third party, the early focus was fit and logistics rather than deep technical questions. The technical stage covered a framework and my experience. Scheduling from recruiter to client moved quickly, but after the client interview I received no meaningful feedback despite…
Interview experiences · Further AI
Further AI Staff Applied AI Engineer Interview Experience — AI-Assisted Coding Round and a Four-Session Onsite
Further AI is a Series A startup that automates insurance underwriting. I interviewed for Staff Applied AI Engineer. The whole process was 3 rounds. Round 1: HM phone screen (15 minutes), mainly to see if there's a fit. We talked about projects I had done before, and they asked about my experience with and interest in using AI. Pretty relaxed overall. Round 2: Two 45-minute coding sessions. Merge…
Interview experiences · Garmin
Garmin Intern Software Engineer Interview Experience — In-Person Technical Test With Eight Mixed Problems
First round was a technical test that was held at the company. There were simple questions about OOP and DSA, logic and SQL. There were 8 problems. 2 of them asked me to describe the OOP principles and to identify which ones are relevant for a described situation. Then there were 2 coding problems about a square matrix (n x n). It was a circular matrix that started the indexing from the middle of…
Interview experiences · Garmin
Garmin Software Engineer interview: career-fair concepts and electronics checks
I interviewed in formats that felt less like a traditional software interview and more like career-fair conversations or quick technical assessments. Some sessions were brief but focused heavily on concepts. At the career fair, I had a general conversation about my resume followed by technical concept questions. The interviewer asked whether I knew specific ideas. After that initial discussion, I…
Interview experiences · Garmin
Garmin Software Engineer interview focused on HR, compensation, and fit
I interviewed for a Software Engineer role at Garmin. The first round was mostly about HR, compensation, and fit, and it ended quickly. The HR phone screen covered my resume and behavioral questions, with a strong focus on motivation and discipline. There was no offer. In one case, the salary discussion didn’t align, and in the other, I didn’t continue after the early HR fit check. Location: Olat…
Interview experiences · Garmin
Garmin Software Engineer interview with DSA and project discussions
I went through a fairly standard, multi-round software and DSA process over a couple of weeks. It included mostly resume and project discussion, along with one or more light to moderate technical assessments. The recruiter screen lasted about 20 to 45 minutes and focused on my background, why I wanted to work at Garmin, and a few behavioral prompts. In the remote technical interview, which took p…
Interview experiences · Garmin
Garmin Software Engineer interview with two engineers coding
I interviewed for a Software Engineer role at Garmin through a fairly lightweight, two-step process that took place over a few weeks. The recruiter phone screen covered my background and included behavioral questions about how I work. In the technical interview, two engineers watched me code a solution to a problem and discuss my approach. The process felt straightforward, but I didn't advance be…
Interview experiences · Garmin
Garmin Software Engineer interview with two-hour theory-heavy onsite
I interviewed for a mid-level .NET and Software Engineer type role at Garmin, and I felt the process didn't match my seniority level or the time I put into it. The in-person technical interview lasted two hours and focused heavily on theory rather than problem solving. I missed a few questions but otherwise did okay. Afterward, I was told they really wanted someone senior for a mid-level position…
Interview experiences · Garner Health
Garner Health Software Engineer Interview Experience — Scaling an Appointment Booking System
My Garner Health interview was a system design round. The first question was to design an appointment booking system where patients could search for doctors and book appointments. I discussed the core Patient, Doctor, and Appointment data models; how to query a doctor's available time slots; and how to book or cancel an appointment. The design also needed to prevent multiple patients from booking…
Interview experiences · Garrett Advancing Motion
Garrett Advancing Motion Software Engineer interview: demanding and supportive
The process felt professional and candidate-friendly. It combined technical and HR conversations, and the interviewers stayed supportive and open even when questions were difficult. I could explain my thinking without feeling rushed or shut down. The technical discussions assessed mechanical-engineering fundamentals, problem-solving, communication, and general aptitude. I felt tested on both know…
Interview experiences · Gatik
Gatik Machine Learning Engineer Interview Experience — A Point Cloud Config Design Question, Not LeetCode
A recruiter reached out to me on LinkedIn first. I talked to the company's HR, and they told me the company currently has fewer than 500 people, builds mid-range self-driving trucks, and just closed a Series D round, so they're hiring more. Then I talked to the CTO. I mostly talked about what I'm currently working on, and my earlier PhD research direction matched what they do pretty well. Then th…