> Markdown version of [/jobs/ext/2590484-software-engineer-core-team](https://www.wearedevelopers.com/jobs/ext/2590484-software-engineer-core-team). 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). --- # Software Engineer - Core Team - **Company:** Edge Technologies, Inc. - **Location:** San Jose, CA, United States - **Experience:** Expert - **Salary:** $150,000.0 - $180,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Cloud Computing, Databases, Cursor (Graphical User Interface Elements), Software Debugging, Distributed Systems, Middleware, Python (Programming Language), PostgreSQL, Open Source Technology, Queueing Systems, Redis, Software Engineering, TypeScript, Scripting, ReactJS, Large Language Models, Multi-Agent Systems, Kubernetes, Apache Kafka, Free and Open-Source Software, Multiaccess Edge Computing, Docker, Golang, Microservices - **Published:** August 11, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-core-team-san-jose-ca-san-jose-ca--7a0ab54e-f688-4ce3-9acf-28095c80e08f ## About the Role Required: * 5+ years of professional software engineering experience * Strong proficiency in Go (Golang) for production services * Solid experience designing and operating microservices and distributed systems at scale * Working knowledge of PostgreSQL, Redis, Kafka and Docker * Background in cloud infrastructure, Kubernetes, or edge computing * Track record of debugging hard problems in production distributed environments * Hands-on experience using coding agents (Claude Code, Codex, or similar) as part of your workflow - and a genuine interest in pushing what they can do * Clear written and verbal communication; works well asynchronously Preferred: * Familiarity with Python and/or TypeScript/React * Experience with LLM-based systems, LangGraph, LangChain, or other agent frameworks * Exposure to MCP (Model Context Protocol) or LLM observability tools (Langfuse, LangSmith) * Open-source contributions, Architectural Services, Artificial Intelligence (AI), Artificial Intelligence (AI) Agents, Cloud Computing, Debugging Skills, Distributed Computing, Docker, Engineering, Go Programming Language (Golang), Identify Issues, MCP - Microsoft Certified Professional, Messaging Middleware, Microservices, Open Source, PostgreSQL, Presentation/Verbal Skills, Problem Solving Skills, Process Improvement, Production Systems, Python Programming/Scripting Language, Redis, Software Engineering ## Description This role requires you to be onsite in our San Jose Office. This position is not eligible for visa sponsorship. Applicants must be authorized to work in the United States without employer sponsorship, now and in the future. We're looking for an experienced engineer to take ownership of complex, AI-powered systems built on a microservice and distributed architecture. A core part of this role is designing and developing AI agents that run natively in our infrastructure - agents that integrate deeply with our services, run reliably at scale, and deliver real value to customers. You'll ramp up quickly on existing codebases, ship enhancements, debug production issues across services, and shape architecture as the systems scale. This role is for someone who is comfortable navigating unfamiliar code, makes thoughtful trade-offs, and treats coding agents (Claude Code, Codex, Cursor, etc.) as a force multiplier in their daily workflow. Job Core Responsibilities: * Understand large, evolving codebases quickly and contribute meaningfully within weeks * Design, build, and operate services in a microservice and distributed systems environment * Diagnose and resolve production issues across services, databases, message queues, and LLM integrations * Drive architectural improvements - scalability, reliability, observability, and developer experience * Design and develop AI agents that run natively in our infrastructure - owning architecture, tool integration, reliability, and performance * Collaborate with other engineers and use AI coding agents effectively to accelerate delivery ## Related Videos - [Building a Multi-Agent Orchestration Engine That Actually Follows the Rules](https://www.wearedevelopers.com/videos/100159-building-a-multi-agent-orchestration-engine-that-actually-follows-the-rules) - [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall) - [Building AI Applications with LangChain and Node.js](https://www.wearedevelopers.com/videos/1512-building-ai-applications-with-langchain-and-node-js) - [Accelerating Authentication Architecture: Taking Passwordless to the Next Level](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care) - [Dev Digest 210: AI Agents Are Go! Is MCP Dead? LLMs Crack Anonymity](https://www.wearedevelopers.com/magazine/709-dev-digest-210-ai-agents-are-go-is-mcp-dead-llms-crack-anonymity) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)