Great environment for engineers who enjoy technical challenges. The system continues to grow in both scale and complexity, providing ongoing opportunities to solve meaningful problems.
Highly competent and supportive team. There is a strong culture of collaboration, and it's easy to learn from peers across different areas.
There is continuous improvement across multiple engineering aspects, including security, code reviews, QA processes, and overall productivity.
It is a strong place for career growth. High performers are generally recognized, especially when working on visible initiatives.
There is a presence of technical debt due to legacy systems. While there are ongoing efforts to address it, these initiatives are sometimes deprioritized, causing recurring issues when the debt accumulates.
Meeting load can impact productivity. While the communication is great and necessary, some discussions could be handled more effectively through asynchronous channels.
Long-term strategy is generally clear, but short-term priorities tend to shift frequently, which can affect focus and execution consistency.
We must continue investing in reducing technical debt with more consistent prioritization.
We should encourage more asynchronous communication to improve focus time for engineers.
We need to strive for better stability in short-term priorities to support more predictable execution.
It's probably 4 stages, I forget some of the steps, but some of them are: 1. Coding question 2. Coding interview 3. System design interview 4. Manager interview 5. C-level interview
The interview went very well, got along with the interviewer, answered all of the questions. The interviewer seemed to agree with a lot of the answers. We actually stayed on the call for an extra 30 minutes. Then 4 days later, I got a we decided t
I was referred by a friend, but I didn’t hear back from HR until three weeks later. When the interview was finally scheduled, HR missed the appointment, and it was rescheduled for the following week. Just before the new interview time, HR requested t
It's probably 4 stages, I forget some of the steps, but some of them are: 1. Coding question 2. Coding interview 3. System design interview 4. Manager interview 5. C-level interview
The interview went very well, got along with the interviewer, answered all of the questions. The interviewer seemed to agree with a lot of the answers. We actually stayed on the call for an extra 30 minutes. Then 4 days later, I got a we decided t
I was referred by a friend, but I didn’t hear back from HR until three weeks later. When the interview was finally scheduled, HR missed the appointment, and it was rescheduled for the following week. Just before the new interview time, HR requested t