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 about whether I could independently drive things forward and communicate like a real engineer.

— Project background (roughly what I told the HM)

I talked about a full-stack project I built on my own, helping a small team manage their daily workflow:

• They used to manage tasks with Excel + WhatsApp, and info kept getting lost
• I built a web app from scratch: React frontend + backend API + Postgres
• The key part: I did everything myself, from requirements interviews, roadmap planning, and trade-offs, all the way through delivery and maintenance

That was the part the HM was most interested in. He didn't care much about my internships or anything like that.

— The HM's deep-dive questions (recapping how I answered)

Q1: "How did this project actually begin?"

He didn't care about the tech stack at all, he wanted to see how you kick things off first.

The key points of my answer:

• Instead of asking "what features do you want?", I had them walk me through what their actual day looked like
• I mapped out their workflow and found that 80% of the pain points were concentrated around task tracking
• I proposed an MVP scope: "just doing A, B, and C would already make your life a lot better"

He pushed further: "Did you just take notes, or did you challenge anything they said?"

I said I would ask them: "If you already had this feature, would it really change how you work tomorrow?"

When he heard that he said right away: "That's a very product-minded way of working." (I feel like that line earned me a bit of a bonus.)

— Q2: How do you handle vague requirements / scope creep?

I gave a real example: the client suddenly wanted "a feature that auto-generates a PDF and emails it to the customer."

My approach:

• First I asked about the motivation: they just wanted to look "professional and on top of things"
• I proposed a smaller version: just a progress page plus a CSV export, with the email sent manually
• At the same time I wrote up a "Phase 2 backlog" and put the more complex feature they wanted into it

The point I was trying to get across:

• I didn't just say no outright, I laid the trade-offs out and let them choose
• Get a first version out that solves the everyday pain, and only then build on it

The HM's response was something like "saying no politely while still moving forward, very good" — I forget exactly what he said, but that was roughly the gist. Another point, I think.

— Q3: How do you make sure you understood the other side correctly?

I said I have a small habit: after every discussion I write up a summary and send it to them: "Here's what I understood from today's talk. Please correct me if anything is off." Sometimes I also draw a simple prototype or flow chart and screen-share it for them to look at.

The HM followed up: "Did they ever say 'That's not what I meant'?"

I gave an example: I originally only had 3 task statuses, but they said I had to add "Waiting for client." I updated the flowchart on the spot, and also explained that too many statuses would make the UI messy. In the end we both agreed to keep that status.

I completely forgot what the HM said in response, but from his reaction I feel like it earned me maybe half a point — not sure if something wasn't clear enough or what.

— Q4: What happens if you suddenly disappeared?

This one was a bit of a curveball. I hadn't prepared for it, but I improvised okay.

My answer:

• The code structure and DB schema are documented
• The README has environment setup instructions
• I recorded a short video walking through the system architecture
• "If I disappeared, they'd be annoyed, but they wouldn't be completely stuck."

The HM laughed, said "good," and then let me ask him questions.

And that was it. Two days later I got the feedback, and an offer.