Software Development Engineer Mobile & Commerce Apprentice

HighLevel LLC is hiring for the role of Software Development Engineer Mobile & Commerce Apprentice!

Responsibilities of the Apprentice:

• You'll be placed on one team with one charter. Depending on where you land, that could look like: -
• Domain services in Go- designing protobuf contracts, implementing ConnectRPC handlers, and taking a service from ADR to production behind a flag. -
• Ledger and accounting- posting commerce events into a double-entry ledger in real time, building chart-of-accounts translation, and shipping journal APIs that external systems can read.
• Payments infrastructure- provider integrations, capability registries, idempotency and replay semantics for operations that must never double-charge. -
• Document rendering - a cross-runtime templating engine with a conformance suite that keeps Go, JS, and Dart implementations honest. -
• Developer tooling and MCP- protobuf-first code generation, manifest generators, and governance annotations that let AI agents call our APIs safely.
• You'll write ADRs, review other people's designs, and carry your own on-call context for what you ship. Interns here merge to `main` in week two.

Requirements:

• A completed term in a recognized open source mentorship or contribution program, with merged and reviewed work in a real project - we will read your PRs.
• Working fluency in Go, or demonstrated depth in another systems language plus evidence you pick things up fast.
• Comfort with distributed systems fundamentals: idempotency, retries, consistency models, and what happens when the network lies to you.
• Familiarity with containers and Kubernetes at the level of "I have debugged why my pod won't start."
• The habit of writing things down - design docs, issue threads, commit messages that explain why.
• Graduation timeline that allows a full-time conversion at the end of the term.
• Signals we weight heavily: Sustained contribution to a single project across many months.
• Public review threads where you argued a position and changed your mind well.
• Anything you've built that handles money, correctness invariants, or multi-tenant isolation.
• Conference talks, blog posts, or upstream spec proposals (SEPs, KEPs, RFCs).
• Curiosity about the business problem underneath the ticket.