The Opportunity As an Agentic Ops Intern, you'll build systems that take on real operational work — not prototypes, not demos. You'll turn messy, human processes into agents that execute consistently, reliably, and at speed. You'll architect and ship agents end-to-end: define the problem space, design multi-agent orchestration patterns with shared persistent state, build the tooling and memory layers that let agents compound intelligence over time, and iterate based on real production usage. You’ll work across the full stack of agent infrastructure — from intent classification and context assembly to feedback synthesis and tool integration — building systems that define problems clearly, drive decisions, and execute reliably in real-world business workflows. You'll work closely with operators and engineers to identify where agentic leverage exists, then drive solutions forward. You'll operate with autonomy, but not in isolation — our team provides context, feedback, and support as you build. When something is unclear, you bring clarity. When something breaks, you move to fix it. Strong interns don't just complete projects — they build systems that become part of how we operate. The best turn that into a full-time role. This opportunity is fully remote and operates within +/- 3 hours of EST. What You’ll Do & Learn - Design, build, and deploy agent-driven systems for key workflows (talent, onboarding, internal tooling) — ensuring adoption and real impact on how the business runs - Identify and prioritize high-impact opportunities where agent-driven systems can create leverage, and translate ambiguous business problems into scalable, executable solutions. - Design and refine agent behavior — prompting, memory, tools, and orchestration — to improve performance over time - Own a system end-to-end and its performance: accuracy, speed, reliability, and adoption improve because you’re in the loop - Work closely with internal users to ensure what you build is trusted, used, and embedded into daily workflows - Identify opportunities to streamline, accelerate, or automate fragmented work through adaptive, agent-based systems - Document what you build so it scales across the team — not just for you, but for others to reuse and extend About You - You’re actively exploring or building with AI agents — you’re curious, hands-on, and like testing what’s possible - You think in systems — inputs, outputs, feedback loops, and where things break - You can operate in ambiguity and make progress — you don’t need everything defined to get started - You care about outcomes — not just demos, but systems that hold up under real use - You take ownership of your work and move problems forward, pulling in others when it helps you get to a better result - You learn quickly across domains — technical, operational, or wherever the problem is - You build with iteration in mind — ship, observe, improve, repeat Preferred Experience - Final-year student (undergraduate or grad program), recent grad — or early in your career and already building with intent - You’ve experimented with designing multi-tier agent memory architectures (persistent, episodic, and learned knowledge layers) and orchestrating multi-agent systems with shared state, feedback loops, and compounding intelligence over time. - You’ve found your way into building with technology — through school, projects, or a self-directed path — and can point to things you’ve shipped - You’ve experimented with LLMs, agents, or automation tools (OpenAI APIs, LangChain, Zapier, etc.) beyond just following tutorials - You can code well enough to prototype, test, and iterate (Python or similar) - You’ve had exposure to workflows, operations, or systems — and have some sense of how real work gets done - You’ve built side projects, tools, or experiments that improve real tasks — shipped, used, and iterated on (this matters more than credentials) If you’ve built things, are excited about this space, and see a strong match with most of the above, we’d love to hear from you — even if you don’t check every box! About Nascent Founded in 2020, Nascent exists to build, expand, and capture opportunity, in open markets and permissionless technologies. Building from a base of permanent capital, we deploy assets across a range of both liquid and long-term strategies that ensure we are among the most active users of the open financial system we are helping to build. We've made venture investments in 100+ early-stage teams that we believe have the potential to create substantive change, expand boundaries, and find new horizons. We are consistently on the hunt for the most competitive and curious minds exploring the edges of the crypto ecosystem and leverage our hyper flexible structure to accelerate ideas into fully deployed strategies. Our Team & Culture At Nascent, we are an interdisciplinary team of investors, builders & creators, capable of achieving more together than we can as individuals. We offer the opportunity to contribute to building the future global economic system with a world-class team and culture that pairs the freedom to explore, experiment & play with a competitive drive to win. We invest in our people by providing the autonomy to build, coupled with accountability & honest feedback to help learn, grow, perform & win. Our distributed team understands the value of in-person time—we encourage team members to come together for more frequent in-person work. Principles that Drive Our Team & Work - Compete to win - Explore, experiment, play - Always be building - Seek and speak truth - Own your shit. What We Offer - Competitive hourly pay — you’re doing real work, and we treat it that way - Flexible 10–12 week program (May–August) with start dates that fit your schedule - Opportunity to convert to full-time based on performance - Remote-first with flexible hours (within ±3 hours of EST) - Mentorship and coaching from a team of world class operators, engineers, and subject matter experts — learn by building, not observing - Awesome Nascent swag! We are an equal opportunity employer and celebrate diversity and differences of perspectives. We do not discriminate on the basis of any status, inclusive of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.

At enum, we're building our the European cloud platform on bare metal hardware. Not a wrapper around hyperscalers, not a managed Kubernetes reseller, not sovereignty marketing on someone else's infrastructure. We design, operate, and continuously improve the full stack: compute, Kubernetes, storage, and networking. Bare metal to API. We have paying customers, a growing platform, and a small team that builds fast. What we're missing is someone who's built large-scale cloud infrastructure before, someone who already built the things we're building for the first time. We're looking for a Founding Engineer to join as the third member of our core engineering team. You'll work directly with the founder (Max) and the core engineering team, make architecture decisions that shape the platform for years, and write the Go and Rust code to back them up. You'll get equity, ownership, and the kind of impact that's impossible at a company with layers between you and production. Tasks - Design and evolve core platform infrastructure: compute, storage, networking, tenant isolation - Write production Go for our control plane, reconcilers, and API services - Work on distributed storage architecture and scaling (Ceph/RADOS) - Work on network design for multi-tenant isolation and multi-region expansion - Work on Kubernetes control plane internals and cluster lifecycle management - Review and challenge what we've built so far, tell us what's fragile, what won't scale, and what needs to change before it's too late - Mentor a strong engineer who's learning fast but hasn't operated infrastructure at this scale before - Help us make architecture decisions that hold up under growth, not just under demo load - Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success This is not a "maintain the cluster" gig. We're not looking for someone to watch dashboards or follow runbooks. We need someone who can go from whiteboard to Go code to production and own the result. Requirements - Worked at a cloud provider, hosting company, or large-scale infrastructure operation, not on top of one, inside one - Built application-level infrastructure code (Go, Rust, gRPC, reconcilers, APIs) - Delivered projects 0→N. Lead it, scaled it, seen your "brilliant solutions" become tech debt, replaced them - Designed systems that survived growth, multi-tenant, multi-region, high availability, failure-domain thinking - Communicated clearly using docs, RFCs, or architecture decision records to break up and deliver large tasks - Been on-call and know what it means to own production - Operated with agency and urgency - Built the confidence to say no to 99% of things, and the grit to deliver the 1% that matter - Distributed storage in production (Ceph) - Network architecture at fabric level (EVPN/VXLAN, BGP, Anycast, multi-tenant network design) - Kubernetes internals: control plane, CNI, multi-tenancy, not just Helm charts - Infrastructure software in Go or Rust: control planes, reconcilers, platform tooling - Bare metal operations, PXE, hardware lifecycle, datacenter environments Benefits - Founding Engineer title. You're not employee #47. You're building this from day one. - VSOP equity participation. - Competitive salary. Below BigCorp, honest about it. The tradeoff is ownership, equity and impact. - Remote first within EU. We care about what you build, not where you sit. Working language is English, German is a plus. - Hardware of your choice. - No layers. You talk to the founders, you write code, it ships. That's it. - Bootstrapped. We built this with our own money, our own hardware, and paying customers. No VC dependencies, no burn-rate panic. Fundraising is a strategic next step, not a survival one. - Ambitious mission. We're not building another SaaS tool. We're building the European public cloud platform to compete with hyperscalers. Few companies let you work on problems at this scope. We're a startup. That changes things. - There's no "platform team" you're joining. You are the platform team, together with the founder. There's no one to escalate to. You own it. - We ship fast. Architecture decisions go from whiteboard to production in days, not quarters. If that sounds stressful rather than exciting, this isn't the role. - We're building something that doesn't exist yet: A European public cloud that's technically competitive with the hyperscalers. That means ambiguity, unknowns, and decisions with incomplete information. Constantly. - We don't do Jira. We don't do daily standups. We don't do permission chains. We talk, we decide, we build. - You'll be on-call. At this stage, everyone is. If production breaks at 2am, we fix it. That's the deal. - We're honest about where we are: early, lean, in production with paying customers, and building the foundation for something much bigger. If you need structure, process, and a 50-page onboarding doc, we're not there yet.

• Support the availability and durability of critical services across production environments. • Monitor service health using SLIs, SLOs, and error budgets, and escalate issues when thresholds are at risk. • Participate in on-call rotations, incident response, and post-incident reviews to drive service improvements. • Follow established ITIL/OSS processes (incident, change, problem, and capacity management). • Develop automation for common operational tasks, reducing manual intervention and toil. • Contribute to monitoring, logging, and alerting frameworks (e.g., Prometheus, Grafana, Catchpoint,ELK). • Work with CI/CD pipelines, configuration management, and infrastructure as code tools (Terraform, Ansible, Jenkins). • Write scripts (Bash, Python, Go, etc.) to improve system reliability and efficiency. • Partner with engineering, product, and operations teams to support resilient system design and operations. • Assist in capacity planning and disaster recovery exercises. • Work with vendors and service providers to troubleshoot service issues and track SLA performance. • Document systems, share learnings, and help grow a reliability-minded engineering culture. • Contribute to playbooks, runbooks, and operational documentation. • Identify recurring issues and propose long-term improvements. • Promote reliability-focused practices within development and operations teams.

• Architecting, managing and scaling our cloud-native infrastructure on Google Cloud Platform and AWS • Work hands-on with modern serverless technologies, containerized architectures and container orchestration platforms • Leverage the full range of cloud services to ensure high availability, security and performance • Requires deep expertise in infrastructure such as code (Terraform), automated CI/CD pipelines and cloud-native best practices