Incredible employee benefits, including:
If you're a Software Engineer looking to learn new technologies, create innovative technical solutions, or grow your career, I cannot stress to you enough to RUN AWAY from any opportunities at Salesforce Indy.
The company culture would have you believe that Security/Trust trumps everything. Development machines are tightly locked down, and access to new technologies requires a multi-level approval process that can take months. While Security teams claim to "partner" with engineering teams, they impose security restrictions without any input from engineering and require layers of "evidence" as to why a restriction should be lifted (we're talking simple things like installing Docker).
I was once told that "Powershell is banned, access to it is completely forbidden".
Furthermore, the company claims to be Agile and is anything but. This is typical for large companies with internal software teams, but frankly I expected more from a company like Salesforce. User stories and bugs are tied back to epics that are "committed" to specific releases. They require stories that tie back outlining the project from start to finish, and individual stories are broken down further into "tasks" that really just lead to a tedious "check the box" workflow for most projects. If for some reason the project doesn't make it in the committed epic, prepare to be asked by multiple layers of management as to why it was dropped/delayed.
If you're a developer looking for a 9-5 gig with the best benefits in town and an easy-going atmosphere, this might be for you. If you're a developer that wants to work with newer technologies and create truly innovative solutions to existing problems, look elsewhere. This job will not help you develop a better skillset, it will not help you work with newer tech, and it certainly won't allow you to come anywhere close to creating innovative solutions.
Stand up for your engineers.
We are all unhappy with the constant blocker of Security. Most of us are not vocal because anyone that disagrees with Security is balked at for not honoring the #Trust value.
If you want productive, competent, innovative engineers, you have to empower them to do their work. Stop locking R&D machines down like Ft. Knox and expecting software magic.
1. Phone screen with HR. 2. Phone screen with the hiring manager. 3. 1.5-hour coding test with 2 questions. 4. 5-hour onsite interview: 4 were 1-on-1, and the last was with a couple of team members.
I received a Java coding test with a single problem to solve. There was a countdown timer for three hours. I don't like coding tests with countdown timers, but the problem was an interesting one to solve, so I didn't mind it this time. The recruite
I applied online for the position. I was contacted by the recruiter and completed a HackerRank assessment. After that, I had a phone interview with one of the engineers. Proceeding that, I had an onsite interview with a mix of behavioral and technica
1. Phone screen with HR. 2. Phone screen with the hiring manager. 3. 1.5-hour coding test with 2 questions. 4. 5-hour onsite interview: 4 were 1-on-1, and the last was with a couple of team members.
I received a Java coding test with a single problem to solve. There was a countdown timer for three hours. I don't like coding tests with countdown timers, but the problem was an interesting one to solve, so I didn't mind it this time. The recruite
I applied online for the position. I was contacted by the recruiter and completed a HackerRank assessment. After that, I had a phone interview with one of the engineers. Proceeding that, I had an onsite interview with a mix of behavioral and technica