The Role
We are hiring a Security GRC Engineer to build and scale the technical backbone of our security and compliance program. This is not a traditional compliance seat. You will take a control requirement, trace it into the system that implements it, work with Engineering to get it right, and automate the evidence that proves it works.
You will operate across SOC 2, ISO 27001, HIPAA, and AI governance, and you will partner with our ISSM on public-sector and FedRAMP-related work rather than owning it. You will own real systems and processes, not just documents, and you will have real room to decide how the program gets built.
We are small and lean, so we value a bias to action. A working control that ships beats a perfect policy that does not.
What You’ll Do
- Translate requirements from SOC 2, ISO 27001, HIPAA, and customer security assessments into concrete technical and operational controls, then validate that those controls actually work.
- Automate evidence collection and control testing wherever it is practical, so audit readiness is a continuous state rather than an annual scramble.
- Drive audit readiness and work directly with auditors and assessors to produce evidence, resolve questions, and remediate findings.
- Own control mappings, risks, findings, exceptions, and remediation tracking as one coherent system across frameworks.
- Partner directly with Engineering, Infrastructure, IT, and Product to design controls that fit how Eudia actually builds and ships software.
- Support security reviews, due diligence, and the customer trust program for large enterprise customers, including security questionnaires and control documentation.
- Work with vulnerability management to prioritize findings by severity, exploitability, reachability, and business impact, and drive them to closure.
- Support AI governance for our legal-AI products: model inventory, data-handling requirements, and emerging assurance frameworks such as ISO 42001.
- Keep the operational controls healthy: access reviews, change management, logging and monitoring, vendor and third-party risk, and incident response evidence.
- Partner with our ISSM on NIST 800-53 and FedRAMP-related control work as our public-sector footprint grows.
- Turn repeatable compliance work into automation, infrastructure, or product capability wherever you can.
- 4+ years in security, GRC, security engineering, cloud security, or compliance engineering.
- A hands-on understanding of how modern SaaS and cloud environments actually work: identity, cloud infrastructure, networking, logging, CI/CD, application security, data flows.
- Ability to read and reason about Terraform, Kubernetes manifests, CI/CD configuration, IAM policies, and other infrastructure-as-code artifacts.
- Direct experience with at least two of SOC 2, ISO 27001, HIPAA, or NIST CSF / 800-53.
- Able to go from a framework requirement to the technical implementation: inspect relevant configuration, logs, architecture, or code paths; determine whether the control is effective; and work with Engineering to fix it when it is not.
- Experience working shoulder to shoulder with engineers, rather than running GRC as a separate function.
- Hands-on experience using APIs, scripting, SQL, or similar tools to automate evidence collection, control testing, or other security workflows.
- Clear writing. You can explain a control to an engineer, an auditor, a customer, and an executive, and have each of them understand it.
- Strong judgment for separating real security risk from compliance noise.
- Comfort in an early-stage startup where the right move is often to build the process rather than inherit one.
- Azure or AWS security and cloud-native infrastructure, including Kubernetes and container security.
- Identity platforms such as Okta or Auth0.
- SIEM, vulnerability management, SAST/SCA, endpoint, and cloud security tooling.
- Compliance-as-code or automated continuous control monitoring.
- Familiarity with AI/ML systems, LLM applications, or AI governance such as ISO 42001.
- Exposure to FedRAMP or NIST 800-53 environments. Our ISSM leads this work, so depth here is a plus, not a requirement.
- Experience supporting security diligence for Fortune 500 customers.
We do not treat compliance as paperwork. A control should exist because it reduces risk, builds customer trust, or lets the business operate in a market that matters. Wherever we can, controls should be:
Engineered rather than manual.
Continuous rather than point-in-time.
Evidence-based rather than assertion-based.
Risk-driven rather than checkbox-driven.
You will help us build that kind of program.
What Success Looks Like in Your First Year
- Engineering teams understand what controls require, and why.
- Audit evidence is increasingly generated automatically.
- Controls, risks, and exceptions have clear owners and remediation paths.
- SOC 2, ISO 27001, HIPAA, and customer assurance run as one control system, not separate exercises.
- Eudia adds new frameworks and customer requirements without a proportional increase in manual GRC work.
- Auditors and customers receive clear, technically credible answers.
- Compliance becomes an accelerator for enterprise and public-sector growth, not a bottleneck.