Quality is number 1. If there is a bug, that gets fixed over new code. Refactoring is encouraged.
Manager BS is basically non-existent. Agile is not forced on us, and teams / individuals operate independently (ironically more agile than SCRUM or whatever). Engineering managers are hired only from within, so managers are all talented software engineers.
Internal review process is algorithmic, and managers don't get to play favorites (at least, compared to other companies).
The CTO Ken Duda is really great. The engineering org, and largely the company as a whole, is dependent on his great vision and his devotion to quality.
In general, the work is not demanding. It's a best effort kind of place. Those who want to excel can, but there is no constant drive to improve.
Customer support is first class - TAC are a joy to work with.
Growing pains have led to less focused management and a more chaotic environment. A lack of product managers means direction is sometimes not clear.
While the review process is algorithmic, it's still very opaque. Specifically, pay scales are non-existent, and the diversity of compensation seems wide.
Four-year RSU vesting is infrequent, and it means that they don't dollar-cost average the total compensation. This can vary a lot.
Very little attention is paid to external benefits. Paternity leave, for example, is the legal minimum. Compensation is great and all, but there is more to life than dollars in the bank. The HR department does not make active attempts to improve things; all improvements I know of come from the engineering organization pushing for them.
Leadership, excluding engineering, seems to make decisions that are at odds with the company "values," like "Do the right thing." They often dodge difficult questions.
Improve benefits, including maternity/paternity leave. Offer 4-day work week options.
Be more transparent, particularly around compensation and RSUs.
The interview was one hour long and focused on experience and challenges. Following that, the interviewer provided a laptop for a programming exercise. The questions primarily involved memory and data structure concepts. Participants were expected t
My live coding round was the first round. I was asked to solve: * Two Sum * Find a missing number in an array I was free to choose between C or C++.
I had applied through the university website, and it was an on-campus interview revolving around writing, debugging, and compiling programs in a Linux environment. We were 19 of us. Questions were about linked lists and string manipulation.
The interview was one hour long and focused on experience and challenges. Following that, the interviewer provided a laptop for a programming exercise. The questions primarily involved memory and data structure concepts. Participants were expected t
My live coding round was the first round. I was asked to solve: * Two Sum * Find a missing number in an array I was free to choose between C or C++.
I had applied through the university website, and it was an on-campus interview revolving around writing, debugging, and compiling programs in a Linux environment. We were 19 of us. Questions were about linked lists and string manipulation.