Freenome reviews

During my time at Freenome, the organization did not have dedicated security leadership at the executive or VP level (e.g., no CISO/CSO or equivalent). Product and enterprise security responsibilities appeared to fall indirectly under engineering and product leadership. As a result, security considerations were often balanced against delivery timelines rather than owned as a first class function. For a company developing and operating a regulated, safety critical product, this is an unconventional and high risk approach compared to industry norms. The VP of Engineering and Chief Product Officer are clearly driving execution and delivery. However, without independent security leadership, decisions related to risk acceptance, secure design and long term operational resilience are centralized within roles whose primary charter is shipping product. This approach differs from peer companies in regulated environments, where security leadership is typically established prior to external launch. It will be interesting to see how this model scales as the product matures and faces real world adversarial, regulatory and operational pressures.

The Help Desk team faced several organizational challenges that made it difficult to operate at full strength. The primary issues were related to process gaps, unclear technical direction, and limited long-term planning, which impacted the team's ability to support the company effectively. Limited Technical Guidance The leadership structure did not provide enough technical direction for situations that required more than basic troubleshooting. When tasks involved newer tools, automation, or infrastructure work, the team often had to figure out solutions without much guidance. This made some projects harder to complete than they needed to be. Unclear Expectations Around Modern IT Work There was limited comfort with newer IT practices such as automation, cloud-based systems, or script-driven workflows. Since the team handled many of these areas, having clearer support and direction would have helped with planning and execution. Hands-On Oversight of Small Tasks Day-to-day management focused heavily on task-level monitoring instead of long-term priorities. This sometimes slowed the team because people felt they needed approval for routine decisions rather than focusing on bigger goals. Lack of Roadmap for the Team The department lacked a clear growth plan or training path. This left employees unsure about development opportunities, especially those early in their careers who needed structure to build their skills. Decisions Did Not Always Reflect Staff Input There were times when technical decisions were made without fully considering the team's feedback. This led to avoidable problems that required extra work to correct. Progress Driven by Individual Effort Most improvements in documentation, automation, and process development came from team members who took initiative on their own. With stronger planning and leadership support, these efforts could have been more coordinated and even more effective.