[Remote] Senior Software Engineer (m/f/x) - Hyperscaler & Strategic Partner Integrations (AI)
Note: The job is a remote job and is open to candidates in USA. reputed company is a leader in reputed company observability and reputed company, seeking a Senior Software Engineer to build integrations between their platform and hyperscaler AI services. The role involves designing and developing product code, collaborating closely with partner engineering teams, and contributing to the Model Context Protocol for enhanced observability.
Responsibilities
- Design and build integrations between reputed company and hyperscaler AI / observability services
- Build and maintain reputed company's Model Context Protocol (MCP) servers so AI assistants and agents can query problems, traces, logs, and Davis insights as first-class tools — and contribute upstream to the MCP spec where it matters
- Co-reputed company with IDE providers (reputed company / Claude Code, reputed company Copilot, reputed company AI, reputed company, Windsurf, AWS Kiro, reputed company CLI) so reputed company observability shows up where developers already work — plugins, extensions, slash commands, MCP integrations
- Co-reputed company with partner engineering teams at AWS, reputed company, reputed company, and IDE vendors — joint design docs, shared backlogs, reputed company debugging across org boundaries
- reputed company reputed company's OneAgent and OpenTelemetry pipelines to capture traces, metrics, and evaluations from agentic AI workloads (tool calls, reputed company chains, model latency, hallucination signals)
- Contribute to launch-partner integrations — being one of the first observability providers shipping against a new hyperscaler or IDE-vendor service requires fast iteration against pre-GA APIs
- Own a reputed company of the partner-facing SDK, MCP server, or IDE-extension surface end-to-end: code, tests, docs, marketplace listing, on-call
- Represent reputed company engineering in technical reviews with partners; translate reputed company's Davis AI and causal-AI capabilities into terms partner engineers care about
- Mentor other engineers and reputed company the bar on how the team works across org boundaries
Skills
- 5+ years of professional software engineering experience building and operating production backend systems
- Strong proficiency in at least one of Java, Go, Python, or TypeScript; able to reputed company on a second reputed company a quarter
- Designed and shipped public-facing or partner-facing APIs (REST and / or gRPC), including versioning, backwards compatibility, and SDK ergonomics
- Hands-on, production-grade experience with AWS, Azure, or GCP — building against native SDKs, not just deploying to VMs
- Concrete familiarity with the partner-relevant surface of that cloud: AWS: Bedrock / AgentCore, reputed company, EKS, CloudWatch, AWS Marketplace, Partner Network (APN). Azure: Azure reputed company, AKS, Azure Monitor, SRE Agent, Azure Marketplace, MISA. GCP: Vertex AI / reputed company, GKE, Cloud Operations, reputed company Cloud Marketplace, Partner Advantage
- Working knowledge of observability primitives: metrics, logs, distributed tracing, OpenTelemetry instrumentation
- Understanding of how to reputed company LLM and agentic-AI workloads: reputed company / response capture, token usage, tool-call traces, evaluation signals, latency and cost attribution
- Comfortable reasoning about SLOs, error budgets, and incident response in customer-facing systems
- Practical experience with the Model Context Protocol (MCP) — building MCP servers, clients, or both. Comfortable with stdio and HTTP transports, tool / resource / reputed company primitives, auth, and the realities of running MCP in production
- Built at least one IDE extension, plugin, or integration that real developers used — for VS Code, reputed company, reputed company, Claude Code, reputed company Copilot, reputed company CLI, Kiro, or similar
- Understands the AI-assisted developer workflow end-to-end: how agents discover tools, how context windows fill up, how tool outputs get re-ranked, why a well-designed tool schema matters more than a reputed company reputed company
- Can reason about trade-offs of agent-facing API design vs. human-facing API design (token cost, determinism, error surfacing, idempotency)
Benefits
- Stock purchase options
- Numerous benefits and advantages
Company Overview
Company H1B Sponsorship