READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 39 of 153
Interview experiences · BHP
BHP Software Engineer Interview Experience: Graduate aptitude and mining motivation
I applied for a graduate Software Engineer role, and the timeline moved quickly: about four months from applying to receiving the contract. It began with a general aptitude test that relied heavily on maths, pattern-recognition questions, and game-like tasks. Next came an online graduate interview focused on behavior and motivation, including why I wanted to join BHP and what drew me to mining. T…
Interview experiences · BHP
BHP Software Engineer interview: graduate role motivation and mining fit
I interviewed online for a graduate Software Engineer role. The discussion centered on personality and motivation for BHP. I was asked why I wanted to join, what drew me to mining, and why I thought the role would be a good fit. The process was focused on how I think and why I was interested rather than deep technical specifics. I came away feeling that fit and motivation were being evaluated fir…
Interview experiences · BHP
BHP Software Engineer interview with timed recorded STAR responses
My first screening step was an online recorded interview with timed responses. The prompts mixed behavioral themes and scenarios, and I had a short preparation window before recording each answer. They covered teamwork, decision making, safety, and problem solving, and felt closely aligned with the company’s values. The questions were short and direct, but the timing made it hard to think calmly.…
Interview experiences · Bilt Rewards
Bilt Rewards Software Engineer Interview Experience — Passed Every Unit Test, Still Rejected
A recruiter from this company reached out to me directly on LinkedIn — not a staffing agency. After the recruiter call, we scheduled a phone screen. Side rant: I actually have this credit card myself, and the Android app is painfully slow. They basically survive by hoodwinking Wells Fargo and their investors. Anyway, after replying on LinkedIn we set up an intro call, and this recruiter also emai…
Interview experiences · Bilt Rewards
Bilt Software Engineer Interview Experience — Codespace-Based, No LeetCode, AI-Assisted Design Task
A recruiter reached out and went straight to scheduling a technical interview. Their interview process was pretty confusing — they used a GitHub Codespace, zero LeetCode, and it was split into two main parts. Part one: fix failing unit tests. The project was structured similarly to a Spring MVC app, and it also tested SQL. I had to fix a few SQL queries and write the logic for determining reward…
Interview experiences · Black & Veatch
Black & Veatch Software Engineer Interview Experience: hostile manager meeting
I started with an easy, straightforward recruiter conversation. After I followed up, I was scheduled for a second round with two managers in one session. It was mostly a get-to-know-me conversation about my background and projects, and it initially felt like a normal fit discussion. One manager's tone was hostile for no clear reason. It threw me off enough that I withdrew immediately after the in…
Interview experiences · BlackRock
BlackRock Data Engineer Interview Experience — A HackerRank Screen With No SQL at All
After I got unlucky and was laid off from my previous company, I wiped my tears and quickly opened up LinkedIn. Turns out I should have done LeetCode before opening LinkedIn. 🐶 This company was really strange. At first a recruiter reached out to me about an interview, but when I applied on the company website I got instantly rejected. The next day the recruiter called me and said it was just a lo…
Interview experiences · Block (Cash App)
Block (Cash App) Staff Software Engineer Interview Experience — Two Same-Day Screens Then Silence
Giving back to the forum. I interviewed for a Staff SWE role at Cash App — two technical screens back to back on the same day (one coding, one called an "AI Native" screen), then a separate HM phone screen later. All three were remote. Coding: 60 min, CoderPad AI Native: 30 min HM phone screen: 30 min It's been almost two weeks since I finished and I haven't heard anything — I'm guessing the posi…
Interview experiences · Block
Block Software Engineer Interview Experience — Passed the Screen, Then Lost the Headcount
It seems like at this company the hiring manager only looks at your resume after you pass the phone screen. First I talked with the recruiter, and then right there on that call they said they'd schedule the phone screen — a one-hour coding round. The interviewer didn't waste any time either. After about 5 minutes of introducing ourselves, we went straight into the problem. It was written on Coder…
Interview experiences · Bloomberg
Bloomberg New Grad Software Engineer Interview Experience — A GHC Resume Pickup Ends in a Failed First Virtual Onsite
Application timeline: 9/26/2025: Found a referral and applied for the 2026 Software Engineer - New York role. The position isn't open to the public — you can only apply through a referral. 11/2025: Went to GHC'25, talked to a Bloomberg engineer, dropped off a paper resume, and saw them mark it up. 11/13/2025: Unexpectedly got the schedule-VO (virtual onsite) email — must have been picked up throu…
Interview experiences · Bloomberg
Bloomberg New Grad Software Engineer Interview Experience — Rejected After a Van Eck Sequence Question
Painful memory from an interview I did last year, around September-October. I was in a funk for a month after it. Bloomberg's bar is basically two medium-to-hard questions, and you're expected to get the optimal solution. It was a virtual interview, and the interviewer showed up 10 minutes late. I sat in the meeting watching her keep logging in and out, and when she finally turned her camera on,…
Interview experiences · Bloomberg
Bloomberg Product Manager Interview Experience — Efficient Process, Rejected the Next Day
Fresh rejection from Bloomberg. A recruiter reached out on LinkedIn. They quickly scheduled the first round, an HR sync, about 30 minutes. They asked about my general work experience, whether I owned the roadmap, whether I had experience launching products globally, how I worked with cross-functional teams, and what the product I owned was like. They walked me through the overall interview proces…
Interview experiences · Bloomberg
Bloomberg Senior Data Engineer Interview Experience — SQL String Ops and a 20-Minute OOD Screen
The role was Senior Software Engineer - Data Engineering. I couldn't really find much interview experience for this role online, so let me contribute one here. The interviewer was a woman, not very enthusiastic. 40 minutes, 2 questions — the first was SQL, the second felt more like OOD. The first SQL question wasn't too hard logically, the hard part was that it tested string operations. I roughly…
Interview experiences · Bloomberg
Bloomberg Senior Software Engineer, Data Engineering Interview Experience — Recruiter Promised Easy-Medium, Got String-Heavy SQL and Rushed OOD Coding
I couldn't find much interview experience for this specific role online, so I'm contributing mine here. The role was Senior Software Engineer - Data Engineering. The interviewer wasn't very enthusiastic. 40 minutes, two questions — the first was SQL, the second felt more like an OOD (object-oriented design) question. The logic in the first SQL question wasn't actually that hard — what was hard wa…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Detecting Fraudulent Transactions Within 60 Minutes
Coding Interview | Fraud Transactions I recently interviewed with a coding problem about fraudulent transactions, so I am recording it here. The problem roughly gave me a transaction list: I had to find the fraudulent transactions under two rules: A single transaction with an amount greater than $2,000 is immediately considered fraudulent. Transactions from the same account within 60 minutes are…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Final Round Focused Entirely on My Solo Full-Stack Project
Hey, sharing my interview experience from Bloomberg's final round today. We did about 2 minutes of small talk to open, then the HM went straight in: "I'm particularly interested in this full stack project you did for a real client. Let's focus mostly on that, I'd like to understand how you work." As soon as I heard that I knew this round wasn't about how strong my technical skills were, it was ab…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Phone Screen, Super Day, and EM Round to Offer
I've been reading everyone's interview reports here on the forum, so now that I've got an offer, I wanted to give back with my own. 11.12 — Phone Screen It was a question from a coding-practice site — I don't remember the specifics. Follow-up: if you keep inserting numbers that are bigger than the last one at the end, how do you update it? And what if you insert random numbers regardless of size,…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Simplified Grep, Friend-Request Math, and a BQ Round
Round 1: implement a simplified version of grep — find lines in a file containing a specific string, and also account for extensibility to flags. I just honestly clarified requirements first, then wrote the parsing plus the string matching. The focus of this problem isn't really the algorithm, it's whether you can write clean, extensible code. Round 2: given an array of ages, compute the total nu…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Three Onsite Rounds in One Day
This week's onsite report — all three rounds happened on the same day, and I probably failed. In the third round, the manager didn't ask me anything at all, he just told me straight up to ask him any questions I had. I stayed calm and asked a few things, it took about half an hour, then he said I could ask one last question and that was it. Round 1: coding Round 2: SD, with the team lead Round 3:…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Top K Frequent Elements Phone Screen
The first round was a standard phone technical screen — coding only, no behavioral questions. The difficulty is generally on the higher end of LeetCode medium, and the focus is on whether your data structure choice is reasonable and whether your code is clean. The question I got was to design a data structure that supports insert, delete, and returning the current Top K most frequent elements. Th…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Two Passed Screens, Filled Openings, and a Virtual Onsite
At Bloomberg, you can move forward with at most two teams at the same time, and each team's phone screen is independent. Basically, one job posting corresponds to one opening, and those openings fill pretty quickly. I passed both phone screens, but both openings had been filled. The recruiter helped forward my resume to a sister team of one of those teams that was hiring, so I didn't need another…
Interview experiences · Bloomberg
Bloomberg Software Engineer Interview Experience — Two Rough Phone Screens and a Cryptic Tree Puzzle
The interview experience itself was actually pretty good in one sense — just spray and pray, blindly mass-applying with your eyes closed, and there's a decent chance you'll land some phone screens. I landed four HR calls total: one slot already got filled, another is still waiting to be scheduled, so right now I've actually done two phone screens. But honestly, the experience itself was not great…
Interview experiences · BNSF
BNSF Software Engineer Interview Experience — One-Hour Technical Screen, Coding Then Design
The technical interview was one hour, split into two parts: the first half was writing a program, the second half was design. The problem was provided through a markdown file. It was a requirements doc for a REST API, roughly a price quote (rate inquiry) endpoint for some kind of railway freight, with other dependent services and database access operations involved. I was asked to write a sample…
Interview experiences · Bobyard
Bobyard Software Engineer Interview Experience — Five Rounds From a Take-Home to a Four-Person Panel Onsite
Five rounds total. Round 1 is about your resume and experience. They have a technical recruiter who asks about some tech details. They asked a few common coding questions: if you find the frontend is loading slowly, how do you fix it? If you find a prod bug, how do you handle it? Round 2 is a take-home project. They ask you to design the frontend, backend, and DB for a comment system, satisfying…