> Markdown version of [/jobs/ext/2243177-engineer-in-residence-ai-regulatory-intelligence-operations](https://www.wearedevelopers.com/jobs/ext/2243177-engineer-in-residence-ai-regulatory-intelligence-operations). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Engineer in Residence, AI Regulatory Intelligence & Operations - **Company:** AI Fund - **Location:** Mountain View, CA, United States - **Salary:** $120,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Law Practice Management Software, Graph Database, Management of Software Versions, Enterprise Software Applications, Operational Systems, Data Pipelines - **Published:** August 26, 2026 - **Apply:** https://www.dice.com/job-detail/75f15aea-35c8-44b2-9b37-d72343a13b5f ## About the Role * Strong full-stack or backend engineering across data pipelines, workflows, APIs, and enterprise systems. * Demonstrated experience building GenAI products with retrieval, structured extraction, tool use, evals, citations, and guardrails. * Experience with regulated data, compliance workflows, policy operations, risk systems, or other evidence-sensitive products. * Product judgment for systems where precision, provenance, access control, and human review determine whether users can trust the output. * You know how to use AI coding assistants and modern AI tools to accelerate implementation without weakening engineering judgment. * US work authorization. We are unable to sponsor visas for this role. Helpful But Not Required Experience in energy, infrastructure, financial services, healthcare, legal technology, or another regulated industry. Experience with knowledge graphs, document intelligence, audit systems, or policy-management platforms. Founder or founding engineer experience shipping enterprise software from zero to one. Who This Is For A builder who wants to turn regulatory intelligence into operational decisions and completed work. Someone who understands that citations, controls, and human review are core product features in regulated environments. ## Description Regulated companies receive a constant stream of rules, filings, standards, and guidance, while interpreting changes and proving compliance remains manual. Teams need to know what changed, which obligations are affected, who owns the response, and what evidence will satisfy an audit. This role is to build an AI-native regulatory intelligence and operations system, starting with an AI Fund and AES co-build. What You'll Build * A regulatory-source pipeline with versioning, provenance, citations, and change detection. * An obligation and impact-mapping system connecting changes to policies, controls, assets, and workflows. * An operations workspace that assigns owners, tracks remediation, and collects the evidence needed for review or audit. * A trust layer with human approval, traceable reasoning, access controls, and evaluation of missed or unsupported obligations. What You'll Do * Own the build across ingestion, retrieval, structured extraction, impact mapping, workflow orchestration, and deployment. * Work with AI Fund and domain users to define the first regulatory workflow, pilot scope, success metrics, and MVP cut line. * Design a system that keeps source evidence and uncertainty visible at every important decision point. * Build evals for change detection, obligation extraction, citations, missed requirements, and workflow completion. * Make infrastructure and security choices that support a fast pilot without blocking enterprise scale or auditability., * This is a 12-week, full-time, on-site residency in Mountain View, California. * Not every residency becomes a company. The goal is to pressure-test the idea quickly and honestly with real users and customers. * You will be building an AI Fund idea, not bringing your own startup idea into the program. * The process typically includes a Builder Event or equivalent working conversation, then a 48-hour Builder Challenge, then panel review with AI Fund build leadership. * The compensation is intentionally modest during the residency because the upside, if the idea works, is a founder-level role. ## Related Videos - [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) - [Why and when should we consider Stream Processing frameworks in our solutions](https://www.wearedevelopers.com/videos/1085-why-and-when-should-we-consider-stream-processing-frameworks-in-our-solutions) - [Enterprise Linux as Container Images](https://www.wearedevelopers.com/videos/1610-enterprise-linux-as-container-images) - [Building Products in the era of GenAI](https://www.wearedevelopers.com/videos/827-building-products-in-the-era-of-genai) - [Graphs and RAGs Everywhere... But What Are They? - Andreas Kollegger - Neo4j](https://www.wearedevelopers.com/videos/1311-graphs-and-rags-everywhere-but-what-are-they-andreas-kollegger-neo4j) - [Should we build Generative AI into our existing software?](https://www.wearedevelopers.com/videos/1129-should-we-build-generative-ai-into-our-existing-software) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production) - [Stephan Gillich - Bringing AI Everywhere](https://www.wearedevelopers.com/magazine/489-stephan-gillich-bringing-ai-everywhere) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Should AI be Regulated? The Arguments For and Against](https://www.wearedevelopers.com/magazine/271-should-ai-be-regulated-the-arguments-for-and-against)