Great day-to-day benefits.
Top-notch desks and workstations.
Daily work is entirely dependent upon the individual team. You may have a great one; I had the worst experience of my career of over 20 years.
Technical knowledge is entry-level. Salesforce has combined the roles of testing and development/engineering. The result is testers are now responsible for learning how to program on their own. I had one gentleman ask me, after 3 months of programming, if methods can be called from other methods. Engineers are now responsible for testing. They don't do it and just sign off because they 'looked at the code.' On two different occasions, engineers repeatedly stated that specific features were tested and verified on test servers. Interestingly enough, those test servers had not yet been deployed. The 'testers' never even logged into the server.
Staff compete for jobs unethically. The personal benefits are so good (pay, etc.) that individuals will lie about what has been completed to deflect investigation into other problem areas.
The entry-level management are typically developers who have been moved into management with no training. During meetings, they will remote in while working on their own tasks or actually work on their own tasks at the table, often interrupting a meeting to ask a question or give directions about totally unrelated tasks. When asked why they do this, they will respond, "I wasn't running the meeting; it was for you." This often results in missed info and misdirected teams.
Stop using developers as managers.
Start training teams on a common methodology.
Don't use the term 'stand-up meeting' for an hour-long business analysis discussion.
Be able to determine the quality of work people do.
Don't have people come in at 9:30, leave at 3:00, and not know how to code.
The reason why the Salesforce software is so expensive is because developers don't work 30 hours, never mind 40.
Cross-team communication is horrid. You can have an entire team down for weeks because a single member on another team is too busy drinking his coffee and watching streaming videos.
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