Pex Reviews

Below market pay for sw engineers, equity amount offered via RSO (options) isn’t substantial (and they don't tell people the value, and specifically will not answer this if asked even for a ball park, but once you join you can derive the value from outstanding shares and series a, and anticipated company value over time, it is worth about $20-100k over 4 years assuming best case, range covers about 95% of levels, will likely be illiquid for 10 years or more, and vests 10/20/30/40) No bonuses for performance Culture of not testing business critical software, no urgency on deadlines while at the same time the COO will ridicule a sr engineer, with 5+ years of service, during an all-hands company meeting for taking a vacation. While at the same time ignoring the advice of engineers doing the work to reach deadlines. Code that works vs solves, lots of stubbornness on bad solutions/ideas, standard computer science knowledge isn't commonly known (eg standard data structures, algorithms), passiveness is rewarded, activeness is punished, spending effort on improving just adequate skills wasn't common, lots of "shooting yourself in the foot", too much acceptance of mediocrity Not a great place for senior engineers who are passionate about writing software and honing their craft. Some problems common of ceo/founders exist

- Product direction does not inspire confidence, many initiatives do not seem to align with actual market demand, unsatisfactory explanations of how to get from Point A -> Point B regarding goals, lots of backtracking or discarding of engineered efforts - Burn rate is concerning, as there have been struggles to obtain paying customers - Non-competitive compensation compared to the rest of the US market, no cash bonuses, equity grants are heavily backloaded, salaries are on the lower end outside of the very highest levels - Feels very much like a business/product problem space; engineering work often comes off as artificial and forced due to waiting for product to decide on the correct prioritization of items - Reiterating on the previous point: there are not many interesting problems to solve as an experienced developer, most actual implementation items are basic in nature outside of the ML team - Feels like there is a culture of hiring to fix problems (both technical and overall issues) instead of working internally to resolve them when possible; new hires often end up in seemingly disadvantageous positions, occasionally ending up with no real meaningful work to take on - Promotions do not feel transparent, and it doesn’t seem like effort is always fairly rewarded - Meeting bloat is not unheard of despite an emphasis on agile practices