Quinn

About iollo iollo was founded by Daniel Gomari (PhD Computational Biology, Stanford) and Prof. Mike Snyder (Stanford Genetics, 900+ publications) after watching pharma companies spend millions and months making R&D decisions that could be computed in days. We built Quinn to fix that. Quinn is an AI scientist that runs autonomous scientific workflows and delivers high-stakes R&D decisions to Fortune 500 pharma companies. The role Own the infrastructure Quinn runs on in production. Quinn runs autonomous scientific workflows inside enterprise pharma environments. Each customer gets an isolated deployment with dedicated storage and compute. Runs are long-lived, concurrent, and compute-intensive. The engineering challenge: deploy securely into customer-controlled cloud infrastructure, keep data fully isolated across tenants, and keep production reliable for customers where infrastructure failures have real business consequences. What you'll do Own deployment and data isolation for enterprise customer environments Ship observability and cost controls at scale Keep production running and be the person who answers when it isn't Build it, deploy it, prove it works What you'll need 5+ years owning production infrastructure end-to-end Deep AWS experience across compute, storage, networking, and identity Built customer-facing deployments with real data isolation and compliance requirements Shipped in environments where reliability is non-negotiable A bias toward verifying your own work before anyone else touches it You'll stand out if you Have deployed into customer-controlled cloud environments with SSO and dedicated storage Have worked with workflow orchestration and serverless compute at scale Use AI agents as core engineering tools, not novelties Tech stack AWS (compute, storage, identity, networking), Python, TypeScript, workflow orchestration, serverless compute. SOC 2/ISO 27001 compliant environments. First 90 days First 30 days: Own the production stack. Ship multiple customer-facing releases. Stand up new isolated environments. Prove you can operate independently from day one. First 60 days: Architect and ship the next generation of deployment and observability infrastructure. Be the person who defines how new customers get deployed, not just the person who executes it. First 90 days: You're defining the infrastructure roadmap, not just executing it. The team defers to you on technical direction. Why join us Your infrastructure directly enables scientific decisions that change how drugs get made in the world Shape systems that Fortune 500 pharma depends on Competitive compensation with meaningful equity You'd be the person Quinn depends on to run. Enterprise pharma already trusts Quinn with their highest-stakes R&D decisions. You make sure the infrastructure never gives them a reason to stop. If you want to own that, let's talk.