Boring, low morale, low pay, no challenges
Boring, low morale, low pay, no challenges
- Salary is okay.
- People are nice enough.
- Good work/life balance.
- very boring
- no challenges at work
- nobody cares about engineering excellence
- if you try to change anything, people will try to stop you and say all the reasons why things are the way they are
- leadership is overpaid; they do absolutely nothing
- Jack does nothing but loves Bitcoin
- Eng tools and frameworks are ancient, and if you try to change things, people will tell you "it will never happen" and try to stop you
- remote is good for your personal life, but your career growth and engineering skills will completely stagnate
- Fire most of Core.
- Fire Core+1's.
- Fire Core+2's.
- Elevate the 10x engineers and let them make their own roadmaps.
- Make product management sit under engineering, instead of the other way around. Smartest engineers >>> "good" PM's.
Additional Ratings
Was this helpful?
Block Interview Questions
Block Interview Experiences
Software Engineer
The recruiter reached out, and I had a phone screen followed by an onsite interview. The onsite interview consisted of 7-8 individual interviews, where I had to write code on a real computer. There was a separate open section for interviews, making t
Software Engineer
Quick and simple interview process: * Two rounds of one-hour phone interviews. * Then, two back-to-back one-hour onsite interviews with lunch and a tour. Quick rejection and expense reimbursement emails were sent after the onsite interviews.
Software Engineer
An internal recruiter contacted me. I was looking for a new role at the time. (They had contacted me a year earlier, but I wasn't looking then.) The interview process consisted of one phone screen followed by an all-day on-site interview. This includ
Software Engineer
San Francisco, California, United StatesSeptember 1, 2017The recruiter reached out, and I had a phone screen followed by an onsite interview. The onsite interview consisted of 7-8 individual interviews, where I had to write code on a real computer. There was a separate open section for interviews, making t
Software Engineer
San Francisco, California, United StatesJanuary 1, 2016Quick and simple interview process: * Two rounds of one-hour phone interviews. * Then, two back-to-back one-hour onsite interviews with lunch and a tour. Quick rejection and expense reimbursement emails were sent after the onsite interviews.
Software Engineer
San Francisco, California, United StatesAugust 1, 2012An internal recruiter contacted me. I was looking for a new role at the time. (They had contacted me a year earlier, but I wasn't looking then.) The interview process consisted of one phone screen followed by an all-day on-site interview. This includ
