Conductor Software Developer reviews

I waited a while to write this review because I did not want to say something in the heat of the moment. The engineering department lacks direction and structure. The CTO is very nice but is too focused on the business side of things and not enough on the technical side. A strong VP of Engineering could alleviate that problem but there wasn't one and still isn't as far as I know. There are no architects either so every development team kind of does what they want and figuring out the right way to do something depends on finding someone with a strong opinion. As a result, microservices don't seem to follow any conventions. There is a DevOps team that seems to operate independently of development which doesn't make any sense. There is a legacy monolith that runs on an antique version of Java that I thankfully did not have to deal with. The office itself is kind of run down and a large part of it is populated by sales folks who make so much noise that I often had trouble concentrating. There are regular "all hands" meetings that feel like their only purpose is so some of the senior leadership can hear themselves talk. The CEO is a nice enough guy who seems like he hasn't realized that Conductor has become a much larger company than when he started it. He will also just start talking to you while you're in the bathroom which is more than a little awkward.

Work can get intense at times.