DigitalOcean Senior Software Engineer at DigitalOcean owns the AI reference architecture and builds core components of agentic systems. The role involves designing AI platforms, defining standards, and integrating AI agents with enterprise systems.
Responsibilities
One distinctive advantage: DigitalOcean sells the substrate we run on. You will partner with our AI platform organization and build on our own AI platform and inference products—dogfooding that is also the fastest path to enterprise capability. Few architect roles make you the internal design partner to the products you depend on.
This is not an advisory role or a review-board seat. You will write code, build prototypes, publish reference implementations, and pair with engineers on the hard parts. You will also say no—to a design that won't scale, to an agent that shouldn't have write access to the general ledger, to a vendor feature that papers over an architecture problem. Ivory-tower distance is the failure mode we screen against.
Own the AI reference architecture. Define the patterns and standards for how DigitalOcean builds agentic systems—orchestration, tool use, capability boundaries, memory and state, retrieval, evaluation, and observability—and make the governed path the easiest one to take. Standards enforced through tooling and paved paths, not approval boards.
Build alongside the team. Design, prototype, and code the hardest and most ambiguous components, and publish reference implementations others build on. Recent hands-on building is the core of this job, not a nice-to-have.
Architect the internal AI platform. Shape the shared services every agent depends on: model access and routing, agent runtimes, evaluation harnesses, durable orchestration for long-running stateful workflows that pause and resume across days, and the developer experience that makes all of it self-service.
Design the tool and capability layer. Define how agents discover and invoke capabilities, built on open standards such as the Model Context Protocol: versioned, schema-defined tools with clear ownership, and evaluation gates before anything becomes available for reuse.
Design how agents meet enterprise systems. Establish the integration, identity, and authorization patterns that let agents work safely against systems of record—never replacing a system's own authorization, only narrowing it. This is where most enterprise agent programs quietly fail.
Re-architect business processes to be AI-native. Sit with the people doing the work—finance, recruiting, sales operations, support, IT—to understand a workflow before designing for it, then partner with functional leaders to find the highest-leverage opportunities and ship them.
Set the standard for governance and safety. Capability boundaries, human approval for consequential actions, autonomy earned on evaluation evidence, audit trails, and lifecycle management—designed into the architecture rather than written into policy documents, and aligned with the security and compliance obligations we already carry.
Own the unit economics. Design for cost per completed task, not per token: model selection and routing, context management, caching, batching, and cost attribution teams can act on.
Make architectural decisions legible and durable. Write RFCs and ADRs, and keep interfaces stable so components can be swapped without re-architecting. Define the technical standards for AI development, deployment, and operation across the organization.
Multiply the team. Set the technical bar through architecture reviews and high-leverage code, mentor engineers across the US and India, and be the escalation point when a design decision crosses team boundaries.
Qualification
Experience building automationStrong understanding of networkingExperience working with network devicesStrong technical writing skillsExperience re-engineering financeKnowledge graphsBachelor's degree in Computer Science
Required
Significant experience designing and building production software systems at scale.
Strong software engineering fundamentals, including distributed systems, API design, concurrency, testing, observability, and system reliability.
Strong programming experience in one or more languages such as Go, Python, or C++
Experience building automation, orchestration, or infrastructure platforms.
Strong understanding of networking, including TCP/IP, BGP, EVPN/VXLAN, VLANs, routing, switching, and network telemetry.
Experience working with network devices, network automation frameworks, APIs, or vendor SDKs.
Experience designing systems that operate safely in highly available, production environments.
Ability to understand complex infrastructure problems and simplify them into scalable software architectures.
Strong technical writing skills, with demonstrated ability to produce RFCs, architecture/design documents, technical proposals, project plans, and other documentation required to drive complex engineering projects.
Ability to take ambiguous problems and turn them into clear technical proposals, documented requirements, architectural decisions, and actionable implementation plans.
Strong communication skills and the ability to influence technical decisions across engineering teams.
Demonstrated ability to operate as a technical leader without relying on organizational authority.
Preferred
Experience deploying AI developer tooling at scale to internal users (Cursor, Claude Code, GitHub Copilot, or equivalent enterprise rollouts).
Experience re-engineering finance, people, GTM, or support processes in enterprise systems, including SOX-relevant or otherwise audited workflows.
Familiarity with emerging agent interoperability and identity work—A2A, agent registries, SPIFFE/SPIRE, and the MCP authorization spec.
Agent evaluation and observability tooling (LangFuse, Arize, Braintrust, LangSmith, OpenTelemetry-based tracing, or equivalents).
Knowledge graphs, semantic layers, or ontology modeling applied to enterprise retrieval, including GraphRAG patterns.
Enterprise architecture practice experience (reference architectures, ADRs, C4 modeling, portfolio rationalization) or a framework background such as TOGAF—useful context, never a substitute for delivery.
Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience.