SessionM Reviews

The technology is not very interesting (aging RoR monolith) and therefore don’t think they will be the next HubSpot. I have concerns about their scalability both from a technical perspective and an engineering organization. In addition, I think the company suffers from a lot of churn so the code suffers from lack of ownership and lots of half finished hacks. Finally, the company is dominated by B players.

1. No training. Learn a complex product on the fly. There is no learning path. There is no guidance by management. It would have been beneficial to me to have someone that actually was a mentor, not the "silent" one who I had to prod to get answers from the first couple of months I was there. I was also put in charge of evaluating this person, who had quite a bit of knowledge, but was put in a vise in order to get the product out quickly, resulting in multiple unfound bugs. 2. Open environment . . . no cubicles 3. Noisy environment . . . co-workers were leaving the building to find a quiet place to work and concentrate 4. Management wall - no longer a flat communications model 5. Hair on fire releases, probably because deliveries run behind schedule frequently. One client delivery was 11 months behind 6. Psuedo agile environment - some teams have daily standups. I attended one retrospective where a manager volunteered to take notes. A white board was in the room, but it wasn't used. Mentioned weighing tasks as a team, and was quickly brushed off, being told that product/project management had already discussed it (without QA). 7. Minimal use of JIRA board 8. Pull back on boasting about large projects with short time cycles. Boasting should occur when you have a bug free release and releases are on time, even with large customers 9. Tendency to focus on the younger crowd