READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 55 of 153
Interview experiences · Discord
Discord Senior Data Scientist Interview Experience — Hiring Manager and Python Phone Screen Passed
I've recently been interviewing for a Senior DS role at Discord. I just passed the hiring manager and technical phone interviews and am preparing for the virtual onsite. HM: Introduce yourself. Behavioral question: Tell me about a time you used causal inference to solve a business issue. What was the challenge, and what would you do if you did this project again? At the end there was a small case…
Interview experiences · Discord
Discord Senior Software Engineer Interview Experience — A Data-Platform System Design Screen With No Feedback
If you get an interview with this team, first of all, congratulations, you're in for some bad luck. During the interview, the interviewer won't give you any feedback, and communication is pretty rough — I'd guess the interviewer himself hadn't really read the problem carefully. By the middle of the interview I had already implemented about half of a solution, but the interviewer eventually decide…
Interview experiences · Discord
Discord Senior+ Backend Engineer Interview Experience — A Redis Curveball on the Etcd Round
Sharing a Discord interview experience — I interviewed for a senior backend position. I really like Discord, I use it pretty much every day for gaming, so I do have a soft spot for this company. Overall impression The interviewers had mostly been at the company for 6-10+ years, very professional, technically strong, and the interview experience was great — it basically felt like solving a problem…
Interview experiences · Discord
Discord Software Engineer interview building a multi-client socket chat server
I was evaluated on building a chat server over sockets. The process felt practical and hands-on, even though I didn't move forward. During the recruiter and setup stage, I was told to prepare for a chat app using TCP clients and sockets. I practiced with the resources provided. In the live coding interview, I implemented a server that could handle multiple clients. I was allowed to look up docume…
Interview experiences · Discord
Discord Software Engineer interview: chat-server coding and virtual onsite
I interviewed for a Software Engineer role through a recruiter screen, a technical screen, and a virtual onsite. Overall, it felt like a standard process with mixed outcomes and a few awkward moments. During the recruiter screen, we discussed my experience and fit, including behavioral questions. In one case, I was unexpectedly asked to describe a trade-off situation. The technical screen was a l…
Interview experiences · Discord
Discord Software Engineer interview: DS&A coding and virtual onsite
I went through a more traditional data structures and algorithms interview process at Discord. It started with recruiter and initial screens, followed by a coding stage and then an onsite. The technical bar felt more focused on knowledge than on building an application. After the initial conversation, I moved into a coding step. The technical interview focused on data structures and algorithms. I…
Interview experiences · Discord
Discord Software Engineer interview: React component live coding
I interviewed for a Software Engineer role with a front-end-focused live coding component that let me work interactively on screen. The recruiter screen was a short phone call about my background. For the live coding round, I had to design and implement a relatively small React component while sharing my screen. In one case, the interviewer helped keep the expectations clear, and we had a back-an…
Interview experiences · Discord
Discord Software Engineer interview: relaxed recruiter screen
I had a low-stakes, recruiter-first experience for a Software Engineer role, with a quick and mellow timeline. The recruiter screen was a relaxed conversation about my background and why Discord. We also discussed the team and the hiring motivation, and the overall mood was friendly and calm. I didn’t receive an offer. The stage felt easy and conversational, but it didn’t lead to any further move…
Interview experiences · Discord
Discord Software Engineer interview: technical questions in the first screen
I had an early-stage Discord interview that combined recruiter outreach with technical and behavioral questions, but it didn't progress further. After I was emailed to apply, I scheduled a screening call. I answered technical questions along with standard behavioral questions. I didn't receive an offer, and the experience showed me that the first screen could include hands-on technical checking r…
Interview experiences · Discord
Discord Software Engineer interview: technical screen felt pointless
I had a Discord interview where I followed the instructions closely but still didn't progress, which left me frustrated with the technical screen. The recruiter screen involved slow scheduling and initial coordination. During the technical screen, I solved and handled what the interviewer asked, but the conversation felt "pointless," with little discussion or flexibility. Although I had a good te…
Interview experiences · Discord
Discord Software Engineer interview with socket and chat server coding
I went through an uneven Discord process. The technical experience felt rushed, poorly explained, or overly constrained, and it didn't end in an offer. The recruiter and hiring manager lead-in was relatively smooth in tone, although expectations weren't always communicated well. In the technical screen and live coding round, I worked on socket or chat server style problems under time pressure, wi…
Interview experiences · Disney
Disney Senior Data Analyst Interview Experience — Four Rounds, Lost Out to a Candidate with More Product Experience
There aren't many Disney/Hulu-related posts on this forum. A few months ago I interviewed for a Senior Data Analyst, Product role. I applied in early July this year. Their hiring process is four rounds. The recruiter scheduled my HR screen in the second week after I applied. It was mainly: 1) introduce myself, 2) why I wanted to switch jobs, 3) they walked through the interview process. Overall i…
Interview experiences · Disney
Disney Senior+ Lead Software Engineer Interview Experience — Four-Part Onsite With a Code Review and Whiteboard System Design
The Mouse House onsite! They've started doing in-person onsites now, so the last two interviews were at the Seattle office. I was interviewing for Lead Software Engineer (Frontend). The second round had four parts total. The first part was a half-hour chat with a Senior TPM, mainly to get a sense of your working style and see your collaboration style. The second part was a code review with a Prin…
Interview experiences · Disney
Disney Software Engineer Interview Experience — A Set Problem in Java, a Surprise Streaming Question, and a Reject
This was a practice interview at the start of my job search. They started off with a "most impactful project" question, and I just answered it off the cuff — I hadn't prepped for behavioral questions. Then: write a set, but at first they only let me use Java. I used to write Java, but algorithm interviews these days want you to write so much code that I've been prepping everything in Python. This…
Interview experiences · Disney+HotStar
Disney+HotStar Software Engineer interview: AI fluency and high-level design
Recruiter coordination was a little difficult, but I thought the interviewers were good once the interviews began. I went through two rounds: AI fluency, then high-level design. I didn't receive an offer. In the AI fluency round, I had a system-design problem about where AI could be useful. It felt much broader than a typical high-level design question. I had to decide how the proposed system wou…
Interview experiences · Distyl
Distyl Senior+ AI Engineer Interview Experience — A Whisper Streaming Take-home, Then System Design and a Deploy Deep Dive
I interviewed for AI Engineer + Backend. First was the recruiter, who asked a lot about customer and user experience, because Distyl does a lot of custom solutions for traditional companies building AI-related products, so it mostly revolved around development experience working with clients — kind of felt like interviewing for an FDE role. I applied for AI Engineer, and the recruiter said the wh…
Interview experiences · Docusign
Docusign Account Executive interview focused on a predefined career path
I went through an Account Executive process where the hardest part was the team's consistent focus on specific career-path assumptions and alignment with its sales narrative. In the recruiter screen, I discussed my background and career goals, but the recruiter's expectations were closely tied to a predefined SDR to MDR to AE storyline. In later conversations with managers and leads, I discussed…
Interview experiences · Docusign
Docusign Account Executive interview with multiple presentations
I went through an Account Executive hiring process that felt average to difficult. It dragged on for months, with several rounds, shifting timelines, and a lot of work for the candidate. The early recruiter conversations seemed promising. I then had additional interviews with hiring managers, followed by separate presentations that I had to prepare and deliver. Those presentations took substantia…
Interview experiences · Docusign
Docusign Software Engineer interview: API script and HackerRank-style exercises
My process was shorter and heavily front-loaded. It began with a quick recruiter screen, then moved into a panel-style technical evaluation. The questions covered coding and system design, and nothing felt wildly unexpected. They were standard areas they wanted to see me handle calmly. The process continued in a way that felt somewhat drawn out but still organized. I had four interviews in total,…
Interview experiences · Docusign
Docusign Software Engineer interview: hour-long whole-team coding rounds
I had a team-manager kickoff and then moved into a whole-team round with several people interviewing me back-to-back. The scheduling details suggested that each team member would take about 30 minutes, but in practice each conversation lasted closer to an hour. That changed the pacing of the day. The technical conversations focused mainly on coding. Because they ran long, I had fewer natural brea…
Interview experiences · Docusign
Docusign Software Engineer interview with a behavioral-only session
I had a lightweight, behavioral-focused experience for a software engineer internship track. Before anything technical happened, the recruiter arranged the process and checked what scheduling worked for me. The logistics felt fairly smooth, and I appreciated that the recruiter stayed in contact and helped map out the timing. When the interview took place, it stayed entirely behavioral. There were…
Interview experiences · Docusign
Docusign Software Engineer interview with three LeetCode-style rounds
My process started with a recruiter call about my background, the role, and the team I was targeting. After that, I had three LeetCode-style coding rounds, each lasting about an hour, along with a behavioral interview. The timeline stretched over several weeks, and I waited around three weeks after the final round to hear back. The technical difficulty wasn't the main issue for me. One round felt…
Interview experiences · Docusign
Docusign Software Engineer interview with timed DSA and DBMS problems
My process quickly became an assessment-style experience. I completed two closely related DSA problems in a timed format. One seemed to rely on graph-style reasoning. There was also a DBMS question that was trickier than the coding problems. It involved joins and aggregate-style thinking, so I had to slow down and pay close attention to what the question was asking. Recruiting coordination was an…
Interview experiences · DoorDash
DoorDash Analytics Engineer Interview Experience — Rejected After a Four-Round Virtual Onsite
I couldn't find a single interview review for the analytics engineering role on the forum, so I'm contributing one. Tech round: one LC medium question, not sure if it's an original/repeat question, pretty simple but exhausting — window sum, find the max sum. I'd seen it before in DoorDash's DE interview reviews. Then four SQL questions — he said getting three done was actually fine. I wrote the f…