Software Engineer

JOLT•San Francisco, CA

12d•$125,000 - $135,000

About The Position

JOLT is disrupting two industries at once, EV charging infrastructure and out-of-home advertising, across five markets, with a team that moves fast to test and deliver exciting new innovations. We don't operate like a traditional software company, and we don't want engineers who think like one. We're building something genuinely new: an AI-native engineering culture where agentic systems, automated workflows, and intelligent tooling compound our output every week. The infrastructure we've built in the last year has transformed how the business operates. This role is about accelerating that, taking real ownership of the systems that power JOLT across markets, charging networks, and commercial partnerships. This isn't a role for someone who just wants to close tickets. It's for a lateral thinker who looks at a manual process and immediately designs the system that makes it disappear, someone who builds like an owner and ships with confidence.

Requirements

Cloud infrastructure experience — depth of understanding over specific stack
AI agentic software development (LLM integration, MCP, tool-use)
CI/CD pipeline management
Comfortable in a Linux environment
Full-stack capability — able to contribute across the stack
Strong written and verbal communication (non-negotiable)

Nice To Haves

Customer-facing app experience is a bonus

Responsibilities

Design, build, and maintain AI-driven workflows that automate real business processes — LLM integration, MCP servers, agentic pipelines, and automated ops tooling. You own technical execution end-to-end, guided by product direction.
Own monitoring, incident triage, backend production issues, cloud resource management, and back-office support for our field ops team. Autonomy to fix, automate, and improve as you go.
Manage and evolve our cloud infrastructure. Keep things running, scale what needs scaling, and build new infrastructure with a bias toward simplicity and maintainability. Stack-agnostic — we care about engineering judgment over familiarity with any specific toolset.
Contribute across the stack when the team needs it — debugging front-end issues, supporting releases, or picking up work that doesn't fit neatly into a lane. Customer-facing app experience is a bonus, not the focus.
Proactively communicate with cross-functional stakeholders who aren't engineers — operations leads, commercial teams, external partners. Explain what you're building, why it matters, and what the tradeoffs are without being asked.