Avoid if you're an engineer - Software Engineer Edquity Employee Review

Engineering at Edquity (now Beam) is a two-act nightmare. Act I: the ever-shifting product roadmap. Referring to what happened at Beam as a “roadmap” is incredibly generous. About once a month, word would come down (sometimes in passing, by mistake, from a designer asking how engineering was planning to implement a new page) that a new client was coming on board and expecting a feature in 2-4 weeks. Outraged, engineering management would push back, to which the executive team would say something like "This partner is critical to our survival as a company. Please get this up for them. It’s going to open new doors for us." The engineering team would then put their current sprint on pause and work 12-hour days to get the new feature up. After this was complete, the executive team would promise that this would never happen again, and that any future product updates would be communicated well in advance. Then it would happen again the next month. Shoutout to the time it happened in December, and upper management was cagey about whether engineering would be included in the company-wide holiday break. We were, unless "your manager lets you know that you have deliverables due." Act II: constant instability in the engineering and infrastructure teams. I was let go because the executive team decided to lay off all non-senior-level engineers (as well as all of the devops resources) in favor of leveraging overseas contractors. This leaves the small group of senior engineers with the task of nursing the contractors (who, though lovely people, like to pretend that anything past AC 1 is optional) and trying to hold together the company infrastructure. Unless you like being stressed all of the time for below-average pay, I would not recommend joining this engineering team.