About Ceresti Ceresti is on a mission to reduce avoidable hospitalizations and improve care for people living with dementia while improving the lives of their families and caregivers. We envision a world in which family caregivers of people living with dementia are supported and have the knowledge, skills, and confidence to provide the best possible care for their loved ones. Ceresti is a tech-enabled dementia care provider with a differentiated model of care that improves outcomes and delivers guaranteed cost savings by including family caregivers in the care team. We offer health plans and accountable care organizations a turnkey solution for engaging a population that has limited participation in traditional clinical programs. Our culture is rooted in agility, innovation, and collaboration. We believe every idea—no matter how small—can spark a meaningful improvement. Together, we create solutions that make a lasting impact on the healthcare ecosystem, enabling more compassionate and cost-effective care for those who need it most. The Role Ceresti's engineering team is writing a lot of code. This role makes sure it is safe: threat modeled, risk evaluated, dependency-checked, and tested by someone who knows how an attacker would approach it. The Security Engineer is the bridge between the CISO's office and Engineering. You will sit with developers, read their code, and write your own: security utility tools, automation, logging and parsing scripts, and the integrations that turn raw signal into smarter controls. Security has a front end, a back end, and a lot of scripts, and most of the work is integrating systems and automating the tooling developers already use. You will also break things on purpose. We want someone who builds attack simulations (using AI and the tools we already run) and uses Dev, QA, and Test as a sandbox to prove where the real gaps are rather than arguing about them in the abstract. Your main working partner is Engineering. You will occasionally build something IT runs in Microsoft 365 for example, and IT is often the end user of those tools. What You Will Do Secure the code Engineering writes • Build and maintain threat models for new and existing systems and features, and keep them current as architecture changes. • Read checked-in code and assess its security. This role reviews code; it does not only review reports about code. • Own Snyk and Docker Scout: thresholds, findings, and driving remediation with the owning teams. • Review the software bill of materials for outdated or vulnerable components and push fixes through to closure. • Review SAST and DAST output, prioritize what matters, and work the remediation with engineers directly. Write security tooling and automation • Build security utility tools and automation that Engineering and the wider company use. • Write scripts for logging, data parsing, and signal enrichment that make controls smarter rather than noisier. • Integrate security systems with developer tooling so the safe path is the convenient one. • Build and tune detection logic and automation that the Security Analyst operates day to day. Prove the gaps are real • Build penetration tests and attack simulations using AI and the tools we already run, and use Dev, QA, and Test as a test bed to demonstrate real exposure. • Feed results from Pentest-Tools and internal testing back into what you build next. • Scope, coordinate, and manage the independent third-party penetration test required for SOC 2 and HITRUST, and track findings to closure. Shape the architecture • Contribute to security architecture and standards, as well as detection logic. • Represent security in engineering initiatives including the mobile app, tablet software, the data lake, and AI and machine-learning work. • Help secure the production cloud environment (AWS via Aptible) as part of Engineering's platform, as code wherever possible. What Success Looks Like In the first year, we would expect to see: • Threat models exist for the major systems and stay current as architecture changes. • Dependency and container findings from Snyk and Docker Scout are triaged accurately and driven to closure, not just reported. • Engineering consults you early on mobile, tablet, data lake, and AI work. • Security tooling you wrote is in day-to-day use, and detections reach the Security Analyst with low noise. • Attack simulations have surfaced at least one real gap that nobody had argued for on paper. • The annual third-party penetration test is scoped, scheduled, and tracked to closure. What You Bring Required • Five to seven years in software or security engineering. Not a first engineering job. • You write code comfortably and would be at home on a development team. Python, Go, or similar. • Hands-on application security: threat modeling, dependency and container scanning, and reading code for security flaws. • Working knowledge of cloud security in AWS, and of...