Fragen in Vorstellungsgesprächen bei Bloomberg L.P. für Senior Software Engineer | Glassdoor.de

Fragen in Vorstellungsgesprächen bei Bloomberg L.P. für Senior Software Engineer

Vorstellungsgespräche bei Bloomberg L.P.

151 Bewertungen von Vorstellungsgesprächen

Erfahrung

Erfahrung
49%
21%
30%

Einladung zum Vorstellungsgespräch

Einladung zum Vorstellungsgespräch
44%
39%
12%
4
1

Schwierigkeit

3,3
Durchschnittl.

Schwierigkeit

Schwer
Durchschnittl.
Leicht

Hilfreich (1)  

Senior Software Engineer-Vorstellungsgespräch

Anonymer Bewerber im Vorstellungsgespräch
Kein Angebot
Neutrale Erfahrung
Durchschnittl. Gespräch

Bewerbung

Ich habe mich über einen Personalvermittler beworben. Vorstellungsgespräch absolviert bei Bloomberg L.P..

Vorstellungsgespräch

I was approached by recruiter for the position. I have been thinking to switch jobs, so decided to give it a shot. Definitely one should revise data structures, algorithms and their runtimes and traditional problems like knapsack producer consumers etc. Phone screen was easy leetcode style question. I was able to solve and write code for the first problem. For second problem we were short on time, hence I explained the approach with pseudo code. Interviewer was satisfied.
Afterward virtual onsite was scheduled for whole day. I logged in in the morning, recruiter explained process and what to expect. First hour was with two engineers. After initial introduction, I was asked to solve the problem. I suggested two solutions which we discussed. I explained runtime for both approaches. I did mix up runtimes but corrected while explaining the solution. Second interview was also with two engineers. Within few mins I had this feeling that one of the interviewer is going to be challenging. For any clarification questions he kept saying basic trivial design or I don’t care. But in the end he wasn’t satisfied with the solution. You know not all interviewer wants you to succeed. Some of them are really trying to pull you down. Second interviewer also asked another problem to solve. I suggested two solutions, explained whole thing including runtime. I implemented most of it. He kept adding complexity to the question and I was giving solutions. After 2 hours we took a break of 15 mins. After 15 mins I was told it’s done for the day. Recruiter will contact me further. I knew this is the end.
Pros: I was interviewing for any position after looong. So yes I am rusty with academics, but I was good with problem solving. I know where to focus.
Cons: Interviewer should be explicit about problem being represented. Conveying solve it in simple terms sends mixed signal. Recruiter could have been more professional to give follow up call/email to tell me that I don’t meet their criteria.

Fragen im Vorstellungsgespräch

  • Remove element from linked list with matching value?
    Pick k elements from list which sums to a number provided?   Frage beantworten

Andere Bewertungen von Vorstellungsgesprächen für Bloomberg L.P.

  1.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 2 Monate. Vorstellungsgespräch absolviert im Juli 2020 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    The first round was a technical phone screen in a shared coding environment on hacker rank. It involved two leetcode easy problems: determine if two BSTs are equal and calculate how much tax a person would need to pay for the year. It went well and I got along with the interviewer so I was scheduled for a virtual onsite which I was told could take up to half the day if I do well on the technical portion.

    Before the interview I had a call with the recruiter where he gave me a very high level break down of what to expect and some tips. Bloomberg likes to keep things flexible so they can move interviewers around if needed so he couldn't give me any detailed information like what I would be tested on or who would be interviewing me. This ended up working against me because from other glassdoor reviews for this role (as well as other technical interviews in general), it seemed I would be getting leetcode style algorithm questions in the technical portion and potentially a system design question in the non-technical portion. So I focused the majority of my time practicing algorithms and brushing up a bit on system design only to be given two questions which were a hybrid of design and coding. I was unprepared but I worked through the first round. Then in the second, my nerves got the best of me and I froze up on a trivial detail. After I got through it, one of the two interviewers cut the interview short and I got the impression he felt this was a waste of his time.

    From my conversation with the recruiter I knew if I didn't do well in the technical portion the day would get cut short so I was glad to meet another engineer in the third round but it quickly became clear he was just talking to me as a courtesy as he didn't present a problem and simply asked if I had questions about Bloomberg. To be fair, asking him questions and hearing about his experience at the company was useful and made me interested in the company but he was also candid about the downsides which I appreciated. After two business days I received the rejection email and I haven't heard from the main recruiter I had been in contact with since.

    Fragen im Vorstellungsgespräch

    • Determine if two BSTs are equal.   Frage beantworten
    • Calculate how much income tax a person would need to pay for the year.   Frage beantworten
    • Design and implement a way to split payments across a collection of bonds which had balances. The split is determined by payment rules such as prorata or sequential and rules could be nested in one another.   Frage beantworten
    • Design and implement a 401k savings calculator which returns the balance given the number of years, interest, and contribution amount as parameters.   Frage beantworten

  2. Hilfreich (4)  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch
    Kein Angebot
    Negative Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Juni 2020 bei Bloomberg L.P..

    Vorstellungsgespräch

    I applied online on May 7th. I heard back the next day that they wanted to do a phone screen with HR. I setup that call and all went well. This was when I first noticed that the recruiter (maybe just HR person) was rude and cold. They were not like the other recruiters I've worked with in my job search process. I didn't think much of it at the time. From there I did the tech phone screen on June 3rd. I heard back on June 7th that'd I'd be moving on to the virtual onsite. I scheduled my onsite for June 17th. They were very vague about the onsite and said I could schedule a call with the person I first talked to (hr/recruiter?) to learn more. I setup the call for June 11th. They never called... this should have really been a red flag for me but I still continued... When I logged into the virtual onsite I was greeted by 2 disinterested engineers that immediately just started talking without even greeting me. Throughout the interview they just seemed disinterested in what I had to say and many times they were silent after I was done speaking. The next interview was better but one of the engineers had a bad internet connection and so I barely could understand them. At the end of that interview they said I could take a 20 minute break and that someone would join the call after that. So I take a quick break and get on the call again. I wait 5 minutes, no one showed, 15 minutes, still no one... I wait 30 minutes and still no one joined the call. I emailed the only contact I had and luckily they got back and said "Oh I'm sorry (the recruiter/hr) person was supposed to join the call but got pulled into a meeting last minute. I think you already talked to her today though so you're done for the day". I had in fact NOT talked to her yet AND she failed to show up AGAIN. So unprofessional and completely rude. I was really thinking I'd like Bloomberg as a place to work but after this experience I will never apply again. This was such an awful experience as a candidate and I think they should really look into the HR/recruiter person I was working with. I heard back 2 days after the onsite that I was rejected.

    Fragen im Vorstellungsgespräch

  3. Hilfreich (1)  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Neutrale Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im April 2020 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    In general, the interview process was smooth. Experienced interviewers were nice , patient, polite and helpful. However, other interviewers (with less experience), who thought themselves to be smart were aggressive and impatient. Usually these people have learned few things recently and would do everything to show their knowledge and smartness by catching small errors. If I were given the opportunity to work with them, I would have a second thought.

    Fragen im Vorstellungsgespräch


  4.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch
    Kein Angebot
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich auf Empfehlung eines Mitarbeiters beworben. Vorstellungsgespräch absolviert im April 2020 bei Bloomberg L.P..

    Vorstellungsgespräch

    1 coderpad and 2 virtual onsite with 2 engineers in each round. Both the virtual onsite rounds were DS and Algo questions. No system design. Rejected after a week

    Fragen im Vorstellungsgespräch

    • Coderpad - 1 Leetcode easy and 1 leetcode medium.

      Virtual Onsite:

      Round 1-
      Interviewer 1 :1 LC easy + follow up to create a package of this solution.
      Interviewer 2: 1 LC medium (asked to code in python, my choice was java for all questions).

      Round 2 -

      Interviewer 1: 1 LC medium
      Interviewer 2: 1 LC medium (only discussion, no time to finish).   Frage beantworten

  5.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Neutrale Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte 2 Wochen. Vorstellungsgespräch absolviert im Oktober 2019 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    Phone interview on hackerrank, a pretty good one. The interviewer was very nice and professional. Then onsite in New York. Two rounds with two members each. The first one was pretty good, both interviewers were nice and leading you to solve the problem step by step. Second round was system design. Messed up some silly but medium difficult problem (shame on it). One of the interviewers made me nervous. Felt not good, no following interview. Got rejected next day

    Fragen im Vorstellungsgespräch


  6.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Vorstellungsgespräch absolviert im Oktober 2019 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    Coder pad test
    Phone interview
    Most questions were on computer science fundamentals such as trees, hashing, sorting etc.

    Time complexity analysis, data structures and algorithms

    Language specific questions were limited. Although coder pad covers actual program implementation and test cases.

    Fragen im Vorstellungsgespräch


  7.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte 1 Tag. Vorstellungsgespräch absolviert im Juli 2019 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    Interview process was pretty standard. First you go through hacker rank and then onsite. I found the hacker rank interview little on the difficult side, i think it often depends on the interviewer though.

    Fragen im Vorstellungsgespräch

    • Design of a regular expression parser to match the repeating characters and algorithm based on binary search.   Frage beantworten
  8.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in New York, NY (Vereinigte Staaten von Amerika)
    Kein Angebot
    Neutrale Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im November 2018 bei Bloomberg L.P. (New York, NY (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    I was put through two live online coding screen interviews. I was surprised to encounter a second screen, instead of either stopping or proceeding to real interviews. I am guessing candidates without referrals are usually put through one screen, but an additional screen is used when the first interview result did not result in a clear success.

    The problems were not that difficult, but there was a lot of time wasted in writing boilerplate code for the problem. I would either prepare that boilerplate code for the interviewer beforehand or remove some of the unnecessary detail from the problems. I felt like most of the interview I spent typing code that provided the interviewer no more insight into my ability to problem solve or program.

    Overall, the format felt kind of trite. The interviewers were generally smart, polite, and interesting. The phone connections were pretty bad in both interviews. The way the problems were stated and tested, it felt like the interviewer had one solution they were referring to, and they were waiting to see if you matched the solution, rather than a more fluid conversation. I used to have interviews like this years ago, but most processes have evolved since then.

    Overall, I am sure designing an interview process is hard and the steps in this process were pretty good. But they made the company look a little dated, with an old fashioned one way, adversarial approach. I would also reconsider whether phone screens are useful. They generally come off as half committing to interviewing someone.


  9.  

    Senior Software Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch
    Kein Angebot
    Negative Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Vorstellungsgespräch absolviert bei Bloomberg L.P..

    Vorstellungsgespräch

    I was working with an _internal_ recruiter who, I don't know if she typically recruits for this type of role but her knowledge of what it was and what the interview process was was minimal at best. She was very nice, though, and found two roles with groups who were interested in interviewing me; both roles seemed like good fits. She described the process as: (1) a one-hour programming/get-to-know-the-role interview, then (2) half-a-day on-site.

    So for the first round, both interviewers asked pretty similar programming questions but left different amounts of time for my questions about the role, which was fine, honestly, since (a) I figured I could probably ask more when on-site and (b) _neither_ of them were with _either_ of the groups I was interviewing for. So I could really only get a high-level understanding at best. That aside, Bloomberg uses this site called Hacker Rank which gives you and the interviewer a collaborative programming environment, which is pretty neat.

    One of the groups decided to bring me on-site and all I was told was that it would be half a day. _That is it._

    Now part of this is definitely my fault because I assumed that the on-site interview would be like most other companies' on-site interviews: meet with someone in HR, talk about the role a lot (like what I could bring to it, what the team needs, _what the team even works on exactly_), meet members of the team, do some problem-solving at a high level, maybe one more programming question and/or brain-teaser.

    Nothing could have been further from the truth. First off, and this is probably what I'm the most upset about, is that _none_ of the four guys I interviewed with on-site were in my group. None! I don't even think they even interacted with my group. How can someone take a job without knowing anything about who or what they'd be working with?

    I should also mention that Bloomberg's policy is not to send out an agenda prior to the interview since they want to allow for "flexibility" for their employees. But really, you can't even send out a high-level overview in the form of a bulleted list?

    Then, the interview was not half a day but it was two hours. When I arrived, the person I was supposed to meet was out that day--fine, it happens--and the person who was his stand-in was very nice and offered me lunch, which was not on the "agenda". I'm not sure how I was supposed to arrive to an interview hungry at 1pm and eat lunch while doing an interview, but alright, nice enough gesture. Then we went into a small meeting room and were joined by another member of his team, and then I was given _yet another programming question_, just like the ones I had done over the phone. So not only was I not prepared to be asked more generic programming questions, but this one was on something I hadn't even thought about in like ten years. The other guy decided to use the experience to teach me about the concept of divide-and-conquer like I was born yesterday.

    Awkward enough but it gets better. They left and I met two more guys, one from the same team as the first two and one from some totally different team. One of them spent about thirty minutes asking me the kinds of high-level, how-would-you-approach-this-problem questions I had been expecting, so it was nice to talk to him and think about those kinds of solutions that would actually be relevant to the job I may or may not have been interviewing for. Then, the other guy gives me _YET ANOTHER_ programming question, and the best part is that it was the same one as what the first guys asked me!

    It's clear that no one talks to each other at this company, even when they're sitting in the same tiny open-floor-plan room eight hours a day. And what kind of recruiter lacks a standardized e-mail they can send around to all candidates with some kind of "what to expect at your interview" description?

    The day-to-day at Bloomberg might be fine, but if their interview process is any indication, run fast and far in the other direction.

    Fragen im Vorstellungsgespräch

    • Breadth First Search. Both on-site interviews asked me to implement breadth first search. Is this like a burning dire need at this company? Can't anyone over there just look it up and implement it in five minutes like I would?   Frage beantworten

Verpassen Sie nicht Ihren Traumjob
Laden Sie Ihren Lebenslauf hoch, um sich schnell und einfach für Jobs zu bewerben. Bewerben leicht gemacht!