Salesforce

Great company culture.

Good work-life balance.

Smart developers with good problem-solving skills.

Great career growth opportunities.

Planning of work is better than most other companies that I have come across.

Hybrid engineering has pros and cons. However, in Indy, the strategy for hybrid transition is causing a significant loss in engineering productivity.

Pros:

1. Hybrid engineering has brought more focus on using contemporary tools for automated testing.
2. This helps in improving system reliability and makes developers better at their jobs, since testing is not considered an afterthought anymore.
3. Huge investment in automated testing upfront is a good overall strategy that will help in system scalability and reduce buggy software releases.

Cons:

1. The idea of depending more on automated testing than on manual testing has translated into demanding all manual/semi-manual QA testers to learn how to code.
2. This is the strategy that has not panned out at all. While self-help tools like online courses, mentoring resources, and in-team guidance have been a proactive, ongoing effort, this approach is taking massive hits on productivity for developers as well as for testers all around.
3. You can find developers on any given day spending quite a bit of time (hours at times) going over basic, step-by-step processes (over and over again) with the testers to resolve minority, non-mission-critical bugs.
4. Testers, especially those who are not from a programming background or haven't coded in a while, are overwhelmed and stressed out about the tickets they have to complete each sprint.
5. For a company that champions engineering productivity and no interruption time for developers, developers are spending less time on quality features/innovative/disruptive work and more time getting bogged down by the process, manual testing, and incremental work. Don't get me wrong, the notion of "ohana" is embedded deep in the organization, and engineers are glad to help their peers anytime. However, this is a massive hit on productivity.

A hybrid transition is not the best way going forward. Investment and focus on automated testing is a win. However, switching job responsibilities and the notion of a 'know-it-all' hybrid engineer is not.

Sooner or later, you will find this becomes a more prominent and glaring problem. Fixing this situation now will prevent you from losing time and quality resources to a corporate process (hybrid engineering) that sounds good on paper but is too good to be true.