Pros
* Good salary and comp. package for my experience level * Learned a lot about my team's domain * Good company values * Presence of a lot of people who had done really well for themselves at the company and were good to be around
Cons
I think the preview of coming attractions was immediate for me- in the few weeks between interviewing and starting, two engineers were leaving the company and a third was moving to another team. So from the start it was kind of clear that this team was a place where Salesloft careers go to end. The mix of personalities on the team clearly just didn't work. I think too many people had tried to get off this team already because nobody was really allowed to switch to a different team. There was basically no trust and very little communication among team members. Things were often tense in meetings and a manager would ask "Who can volunteer to do this?" and we'd all sit in silence for prolonged periods of time. It was sad and pretty immature but nobody wanted to feel taken advantage of. I think the philosophy was generally that the engineers should be left to themselves to figure things out without a project manager. After one of the rounds of layoffs that affected a manager and two of the developers, there a new manager who came in and could immediately tell things weren't right after sitting in a few meetings. I think this was around the time of the annual employee survey where we all answered that we would move to a different job if offered the same salary. They decided having an in-person sync week might fix things. It was actually really nice to meet in person and I had a nice time, but afterwards things were just back to normal. I felt bad because clearly the manager had to get the budget to do all that when it was already kind of a lost cause with most of us having a foot out the door. And also in an alternate universe where we all lived in Atlanta and came into the office together, maybe it could have worked. Relations with other teams could also be pretty rough. At one point we needed help with some database task, and someone on the database team wrote us a script that would accomplish it over time. Great! We kept them updated on progress. A couple months later it blew up in our faces and they came back and asked why on earth we would even consider doing such a thing. There was also an on-call requirement that was a real pain. (Though I found out about it after I started; it was never mentioned during the interview process.) I never got any training or guidance on it, nor sought any out, hoping it would never come up. Typically it was something like a queue getting overloaded, and after the regular engineers played hot potato for an hour or two, one of the People Who Knew things would eventually get on the incident zoom and be able to fix it. One of the reasons the People Who Knew things were so effective was that they had so much social capital with the company and had been there since before covid made everything go remote. So they could risk messing things up by accident and they would have been forgiven. I never felt like I got to that point. Also, unfortunately a lot of my education here was (mostly trying and failing at) figuring out how to navigate the company and was not really transferrable in any way.