2 days ago
COMMUNICATION: Whenever there are issues, you need to communicate clearly with management / rest of the engineering team. You should be thinking about scaling at all times and how to prevent similar problems for other engineers in the future.
SELF-SUFFICIENT: When we give you a task, it will just get done. You're not scared of any complicated technical issues -- you'll just dive straight into it and find a solutions. You have good technical opinions based on experience. You’ll speak up immediately when there’s any issues you can foresee based on past experiences for any processes or new technical decisions being made.
PROACTIVE: You’ll constantly be thinking about the overall health of the organization, and making sure we are tackling the right priorities first. If you feel like we aren’t, you should be bringing this up to the director of engineering and making sure we add tasks that reflect what needs to get done.
ATTENTION TO DETAIL: When you submit pull requests, you thoroughly test to make sure that you’ve covered all edge cases, instead of just solving for the most common one. When you review other people’s PRs, you don’t let anything slip through the cracks.