Constantly working on bleeding-edge software with large budgets to support projects.
Ability to grow knowledge of various technological disciplines.
Tons of office politics. Since the reviews are based on a popularity contest, if you are not everyone's best friend, you get constantly screwed.
Get rid of the personal review system. Base it off the team's progress and the individual's contribution to the team's success or failure.
A recruiter contacted me and asked some basic questions (e.g., "Why do you want to work on this team?"). This was followed by a technical phone screening. I was told they wanted to fly me out to Seattle the same day. Had a full day of on-site interv
1. String Operations: StrCmp() 2. Reverse the words in a string. 3. Binary Search Trees: Least Common Ancestor, Binary Search Delete operation. 4. Dictionary problem. 5. How do you design Malloc()? 6. More on previous projects (about Windbg & Ke
Two interviews, back to back, each one hour long. The first interview featured a LeetCode-style question. The second interview focused on coding basics, requiring a pseudocode walkthrough rather than running the code. Both interviews included beha
A recruiter contacted me and asked some basic questions (e.g., "Why do you want to work on this team?"). This was followed by a technical phone screening. I was told they wanted to fly me out to Seattle the same day. Had a full day of on-site interv
1. String Operations: StrCmp() 2. Reverse the words in a string. 3. Binary Search Trees: Least Common Ancestor, Binary Search Delete operation. 4. Dictionary problem. 5. How do you design Malloc()? 6. More on previous projects (about Windbg & Ke
Two interviews, back to back, each one hour long. The first interview featured a LeetCode-style question. The second interview focused on coding basics, requiring a pseudocode walkthrough rather than running the code. Both interviews included beha