Facebook's "move fast and break things" culture avoids assigning blame for reasonable mistakes, which is a wonderful thing. Teams actively avoid separating creation and responsibility, so you are actually responsible for code that you wrote. The engineers that I get to work with are amazingly skilled and good coworkers.
Tools and APIs change, and old systems are deprecated and removed. Part of the process of moving forward goes toward staying in place.
Get product and infrastructure teams in the same room with food and drinks more often.
The interview process was fun and exciting. There were many LeetCode-style questions that I enjoyed. There are so many interesting things to learn here at this interview.
The first part involved solving a timed coding challenge from the InterviewStreet website. After that, I received a phone call to schedule a phone interview. This interview consisted of three algorithmic problems to be solved in a shared text editor
The phone coding interview was super fast and nice. It was a positive experience. However, the onsite interview was different. I felt that some of the four interviewers seemed entitled, which is something I've never experienced in any other coding i
The interview process was fun and exciting. There were many LeetCode-style questions that I enjoyed. There are so many interesting things to learn here at this interview.
The first part involved solving a timed coding challenge from the InterviewStreet website. After that, I received a phone call to schedule a phone interview. This interview consisted of three algorithmic problems to be solved in a shared text editor
The phone coding interview was super fast and nice. It was a positive experience. However, the onsite interview was different. I felt that some of the four interviewers seemed entitled, which is something I've never experienced in any other coding i