Microsoft's open-source culture is still in its infancy. A lot of the company's time is wasted reinventing the wheel due to the lack of a proper culture for reusing what is already available as a third-party library. Hopefully, this will get better over time, but at a slow pace.
It is harder to make your contribution visible due to the nature of big companies.
If you end up working in old product teams (e.g., Office), you may end up maintaining old code that you inherit, and so you won't learn many new technologies.
Standard intro to CS material, algorithms analysis, and rough systems design. A lot of interview questions will test your CS fundamentals for intro-level jobs. There's nothing about big system design or architecture except in rare cases. Know your
The process includes a phone interview, followed by an in-person Interview Loop. The duration of the in-person interview is on average about 6 hours. It covers: * Algorithmic skills * OO design * Data Structures * Unit Testing
- Phone interview: Explained my background for about 10 minutes. Then the interviewer asked one coding question. Coding was done using a shared editor. The problem was about a simple tree manipulation algorithm. - Onsite Interview: Five rounds plus
Standard intro to CS material, algorithms analysis, and rough systems design. A lot of interview questions will test your CS fundamentals for intro-level jobs. There's nothing about big system design or architecture except in rare cases. Know your
The process includes a phone interview, followed by an in-person Interview Loop. The duration of the in-person interview is on average about 6 hours. It covers: * Algorithmic skills * OO design * Data Structures * Unit Testing
- Phone interview: Explained my background for about 10 minutes. Then the interviewer asked one coding question. Coding was done using a shared editor. The problem was about a simple tree manipulation algorithm. - Onsite Interview: Five rounds plus