Real, anonymous reports from people who interviewed for Software Engineer at Foursquare, newest first and distilled into what to expect across the loop.
Get your personalized Foursquare Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with a recruiter conversation and then, about a week later, jumped into a live coding technical screen that ran for roughly an hour. It felt pretty standard: a hands-on coding task with space to think, and a focus on role-relevant skills rather than anything contrived. I remember it being fairly smooth overall, and afterward the process moved forward with additional conversations rather than getting stuck on logistics.
From there, the next steps were presented as a sequence of technical and discussion rounds. I had a system design discussion, then a technical interview with an engineering manager, and later I met additional team members. Some of the rounds were discussion-based with optional whiteboarding, but the coding part was definitely the centerpiece. Interviewers were friendly and genuinely receptive, and the topics felt closely tied to what the job actually involved.
> 1 year
Average Positive San Francisco, CA
My process started with a recruiter call, and then I went into technical screens that were pretty LeetCode-style. The scheduling and flow felt straightforward, and I remember someone being very nice and making it easy to stay on track. In my timeline, I ended up with multiple technical phone rounds before the loop even got to later stages.
When I reached the onsite, the structure became clearer: a mix of coding and design with multiple rounds. One path I experienced included four onsite interviews total, with two LeetCode coding rounds, a system design round, and a behavioral/culture-fit style discussion. The onsite itself was split across two days, with rounds around an hour each, and the day pacing felt like it was intentionally compartmentalized.
> 1 year
Average Positive Bahrain
After a hiring-manager style intro and a team-member screening, I got placed into a virtual onsite with four rounds. The format was simple and standar…
> 1 year
Average Neutral Seattle, WA
I had a pretty intense, schedule-heavy experience. It began with a conversation with a director, followed by a technical phone screen where I got a co…
> 1 year
Average Positive United States
My interview kicked off with an easy, supportive recruiter touchpoint and then moved quickly into the technical parts. I spoke with an engineering man…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter and Initial Screening
The interview process typically begins with a recruiter call, which is described as friendly and supportive, followed by a technical screen that may include coding tasks or take-home assignments. Candidates appreciated the clarity and professionalism during this initial phase.
Recruiter callTechnical screenSupportive
Technical Coding Rounds
Candidates can expect multiple technical coding rounds, often focused on data structures and algorithms, with some interviews resembling LeetCode-style problems. The coding tasks are generally hands-on, allowing candidates to demonstrate their thought processes.
Coding roundsData structuresLeetCode
System Design Discussions
Some candidates experienced system design discussions during the onsite interviews, although the expectations varied significantly across interviewers, with some preferring high-level discussions and others seeking detailed implementations. This inconsistency can lead to confusion.
System designExpectationsInconsistency
Onsite Interview Structure
The onsite interviews are structured into multiple rounds, typically lasting around an hour each, and may include a mix of coding, design, and behavioral questions. Some candidates noted that the pacing felt rushed or lacked breaks, impacting their performance.
Onsite structureMultiple roundsPacing
Behavioral and Cultural Fit
Behavioral interviews are included in the process, focusing on cultural fit and past experiences, which are generally conducted in a non-confrontational manner. Candidates appreciated the opportunity to engage in discussions about the company culture.
BehavioralCultural fitEngagement
Communication and Feedback
Candidates expressed concerns about communication throughout the process, particularly regarding delays and lack of feedback after submissions or interviews. Some reported feeling ghosted or receiving vague responses, which detracted from the overall experience.