Salesforce Software Developer reviews

* employees are not valued I was offered a full time position (6 months in advance before the start date) after having completed a 4 months internship but they ended the contract 2 weeks before starting as they decided to relocate the team to another country. Because of that, I need to mention they ended the contract of other 20 people the were working in the team. (all had to look for a new job) They only offered 1 month salary as compensation nothing more. I have already paid for a new accommodation where I was a guarantor for other 2 people. I brought proof. They didn't care. And this is how people end up in the streets (unless you can find a job in one week or own some savings) So much of the OHANA spirit they are so proud of!

Hybrid Engineering has pros and cons. However, in Indy, the strategy for hybrid transition is causing a significant loss in engineering productivity. First, Pros: 1.) Hybrid engineering has brought more focus on using contemporary tools for automated testing. 2.) This helps in improving system reliability and make 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 for 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, the 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 process (over and over again) with the testers to resolve minority non-mission critical bugs. 4.) Testers, especially who are not from a programming background / havent 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+ incremental work . Dont 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.