#!process Bloomberg Offer

1 messages · Page 1 of 1 (latest)

woeful wave
#

Not accepting DM's. I'll respond here

glad sky
#

Timeline?

woeful wave
#

Offer: 3/10
Email after EM: 3/7
EM: 2/27
Superday: 2/5
vo: 1/13
Applied in like September

neon locust
woeful wave
#

No

nocturne creek
#

Did you have all tech rounds on the same day?

#

Also, could you please say if the dsa questions were from LC tagged list?

woeful wave
#

Yeah 2 tech 1 behav all same day

#

No tagged questions, however, most were similar to
Design Underground System (52 times): https://leetcode.com/problems/design-underground-system/
In that you're presented a realistic situation, must come up with a Class to handle multiple operations, and have multiple levels of optimizations / follow ups

urban hazel
#

how was ur em round?

woeful wave
#

Very good. I went really in depth into how a distributed database to hit a certain usecase would be implemented, and I could tell they were impressed.

urban hazel
#

nice was that just part of your resume overview?

woeful wave
#

Sort of. We talked about my last internship, technical decisions I made, and how I think certain parts of the infrastructure that I used but didn't directly implement likely worked.

nocturne creek
#

How did you prepare for your tech rounds?

#

Also what would you recommend to focus for tech rounds?

woeful wave
#

Technicals: BB tagged (didn't directly help but any practice is good)

Behavioral/EM: I just think about what I've done and lessons I've learned

#

Due to the nature of the problems (mentioned 4 messages prior), you should know your language primitives for making objects well. I think I impressed them during technical with my knowledge of python dunder methods and how several are implemented

eg. How would you implement:
for element in reversed(iterator)):

What is the pitfall of just implementing the iterator protocol and not _reversed_?

#

Basically, don't just solve a problem, flaunt a little. Talk about what you could do, know the language well, discuss tradeoffs you're making, etc

nocturne creek
#

Got it! Thanks a lot

abstract kindle
#

does the EM round not include a technical?

woeful wave
#

It’s technical yapping

gray sapphire
#

what does vo and em mean?

just got this email and dunno which stage this is

image.png
woeful wave
#

VO: virtual onsite (the one you have)
EM: Engineering manager (final round chat with an EM)

gray sapphire
#

thanks!!

how was VO for you? any recommendations on what to prep?

woeful wave
#

Be comfortable applying data structures to problems. General leetcode stuff ykyk

gray sapphire
#

i also see that people prev had multiple VOs

that's not what you experienced right?

gray sapphire
woeful wave
#

Superday is 2 vo (technical interviews) and 1 behavioral

long river
#

@woeful wave how did u prep for em?

woeful wave
#

I think about what I've done, what I've learned. I also brushed up on my distributed systems knowledge by reading some seminal papers.

lapis epoch
#

Can I ask TC + breakdown? Recruiter says I should expect a phone call soon...

lapis epoch
#

@woeful wave

woeful wave
vital locust
#

how was your first round vo?

woeful wave
#

Similar idea to my other VO's. I had one design a class problem, one basic arrays problem.

Guy was chill and we vibed.

He asked if I could optimize any more. It was already most optimal so I proposed running on multiple machines and dispatching requests using a circular hash.

I know it wasn't necessary but as I previous stated, flaunt a bit. It was a good opportunity to do so.

undone oar
woeful wave