Pros: There was a free lunch, good culture, and good comp.

Cons: Too much work, Too many things going and the pressure and burn out finally catches you.

Pros: Sigma has a 3% voluntary attrition rate, which is incredible compared to the industry standard of 18%. People love it here. From an engineering standpoint, there is no shortage of interesting problems to solve. I genuinely enjoy my work (well, 90% of days--I mean, it's still a job). My coworkers are thoughtful, respectful, brilliant people. I really enjoy working with them, learning from them, and just hanging out with them. I've also found awesome mentors who have been instrumental in my growth as an engineer. Work-life balance is great, especially for a startup. The pace of work is fast enough to keep things interesting and facilitate career growth, but it's not so fast that I get burned out. We're strongly encouraged to take our unlimited PTO, which is typically very flexible. I love working at Sigma, and I don't plan to leave soon. Highly recommend you come join us!!

Cons: There aren't any cons for me.

Pros: I'm extremely proud and happy to work with all of my coworkers, and I've learned plenty from them. I'm also very excited about what Sigma is doing: enabling non-technical folks (aka most of the people in the world) to explore and gain insights on large datasets. The technology we work with is also super interesting, and there are countless open-ended problems, related to systems, compilers, UX, and everything in between, which we work on. I have confidence in the management team, and there's a strong focus to have an open and welcoming culture for folks of all different backgrounds, and to make sure people aren't burning out, especially in the time of COVID. There is so much work to be done, there is ample opportunity for people to join and take ownership of both existing components, and to build new components.

Cons: It should go without saying that Sigma is a startup, so there are certainly some rough edges -- certain processes we as developers have in place are probably more manual than we'd like them to be, and also some sections of the code (a minority) are not as clean as they could be. Sometimes planning sprints can be a bit hectic, with all the priorities we're managing. But we're constantly working on smoothing things out, and the issues are well-known.