Low Salary, Strong Mission on Paper, Role Misaligned in Practice
Pros
• Benefits were standard for a mid-sized defense contractor. Medical, dental, 401(k), and PTO structure all fell within industry norms. • Recruiter and HR staff were responsive and courteous throughout the hiring and on-boarding process. • The posted mission (AI/ML enablement, ISR, edge analytics) was inspiring on paper. It aligned with current federal AI modernization goals, even if that never materialized in practice.
Cons
• Compensation fell short of expectations. Compared to peer roles in similar federal-facing data environments, the available pay bands where states require salary transparency (around $115K–145K) felt misaligned with the expertise requested. This was especially noticeable for roles demanding advanced clearances, DevSecOps familiarity, and AI/ML fluency. • The position was terminated quickly. Although on-boarding was completed and work had begun, customer-side funding was withdrawn within months. There was no transition plan, no redeployment support, and no internal alternatives presented. The role ended abruptly following an ominous message to report in person. • Scope creep without structure. During on-boarding, added responsibilities, including stakeholder interfacing and technical coordination were assigned informally. However, there was no change in role title, pay, or authority. In comparable firms, that level of contribution would typically receive formal recognition. • Ambiguity around roles and reporting. Requests for project documentation, KPIs, or clarity were often met with silence. Leadership described the company as one where management hierarchies “don’t really apply,” and where employees are expected to “grow into” leadership roles like in the military. That may work in some contexts, but not in AI/ML environments that depend on structure and clarity. • Tooling was dated relative to the mission. The role was advertised as cloud-native and AI-driven, but in practice, legacy systems and outdated workflows dominated. While listings mentioned TensorFlow, AWS, and agile methods, the reality was spreadsheets and stovepipes. • Exit process lacked structure. Once funding disappeared, so did the job with no formal off-boarding, postmortem, or transition assistance. For a company that emphasizes employee-ownership, it was a missed opportunity to demonstrate internal support. • ESOP value was unclear. In theory, employee-ownership should promote continuity and transparency. In practice, it felt symbolic particularly when organizational disruptions occurred. Compared to other employee-owned firms, the cultural execution felt weak. • Branding didn’t match execution. While the company promotes itself as a modern defense tech firm, the actual day-to-day felt more like a legacy contractor still catching up to current data strategy and transformation demands.