Cares about its company ethics and the example it sets, and listens to employees, though it may disagree. That's a lot better than most tech companies. Our CEO is an SF billionaire, but you can tell he still cares.
Great company perks and events.
Overall, a friendly work environment.
Flexibility with work hours and WFH.
Public about its technology and encourages customers to develop on their own. This means we have pretty detailed public release docs to refer to.
On a company level, employees are encouraged to try new teams and work. 3x a year, there is an opportunity for moving teams (though you'd probably only be able to after about a year on a team).
• Slow to match industry standards for technology frameworks and practices • Delayed long-term plans for the above, or rushed approaches that resulted in a company-wide approach with too many gaps to support many teams' needs • My specific cloud is typically under-resourced, and people often move between teams to fulfill needs • My specific cloud also operates on a slower release schedule (3x a year) • Some management and employees can be quite immature/unprofessional
Invest in long-term plans to meet industry standards.
Just because we don't have competition in the CRM field now doesn't mean we're doing well technology-wise.
Listen to employees and invest in more resources. We seem to have many interviews lined up but few result in offers for my specific cloud. Investigate cloud-specific issues, e.g., how I mentioned that some of my management and coworkers can be pretty unprofessional (in terms of getting along with others and emotional intelligence).
It definitely varies by cloud, but the places where it's an issue should be addressed.
The entire process was straightforward. I had a phone call with an engineer where he asked me how I would design a hash table without any built-in language tools. The second question was how I would optimize for either reads or writes and how I woul
The overall interview process was good. The telephonic interview lasted for about an hour. The interviewer asked me about my background and questions regarding my current projects. This was quickly followed by a programming question. I was asked to
Interviewed with two teams. Recruiter emailed me and scheduled one-hour calls with hiring managers from both teams. Then, I took the three-hour coding assignment and was invited for onsite interviews with both teams after three days of submission.
The entire process was straightforward. I had a phone call with an engineer where he asked me how I would design a hash table without any built-in language tools. The second question was how I would optimize for either reads or writes and how I woul
The overall interview process was good. The telephonic interview lasted for about an hour. The interviewer asked me about my background and questions regarding my current projects. This was quickly followed by a programming question. I was asked to
Interviewed with two teams. Recruiter emailed me and scheduled one-hour calls with hiring managers from both teams. Then, I took the three-hour coding assignment and was invited for onsite interviews with both teams after three days of submission.