Software Development Engineer - Mobile & Commerce (Apprentice)

About HighLevel: HighLevel is an AI-powered business operating system that gives agencies, entrepreneurs and SMBs the infrastructure to build, automate and scale. Today, HighLevel supports SMBs across 150+ countries, fueling community-driven growth rooted in real customer outcomes. To date, businesses operating on HighLevel have generated over $7 billion in ecosystem value, demonstrating the impact of shared infrastructure at scale. By centralizing conversations, automation and intelligence into one system, we help businesses move faster, reduce complexity and execute efficiently. Behind the platform, HighLevel powers more than 4 billion API hits and 2.5 billion message events daily. With 250 terabytes of distributed data, 250+ microservices and over 1 million domain names supported, our architecture is built for performance, resilience and long-term scalability. Our People With over 2,000 team members across 10+ countries, HighLevel operates as a global, remote-first organization built for speed and ownership. We value initiative, clarity and execution, creating space for ambitious people to build systems that support millions of businesses worldwide. Here, innovation thrives, ideas are celebrated and people come first, no matter where they call home. Our Impact Every month, HighLevel enables more than 1.5 billion messages, 200 million leads and 20 million conversations for the more than 1 million businesses we support. Behind those numbers are real people building independence, expanding opportunity and creating measurable impact. We’re proud to be a part of that. Learn more about us on our YouTube Channel or Blog Posts . About the Role: We are looking for a Software Development Engineer in Test Apprentice to join our Quality Engineering function for a structured 12-month apprenticeship. This full-time apprenticeship is designed for someone who wants to build a strong foundation for a career in software engineering. Apprentices will work on real testing and automation initiatives that directly contribute to product quality, supported by mentorship, technical guidance, and structured learning throughout the programme. They will work alongside experienced SDETs and software engineers while developing practical knowledge of automation frameworks, API testing, defect analysis, CI/CD processes, and software quality practices. Programme Details: Work Type: Apprenticeship Department: Engineering Sub Department: SDET Duration: 12 months Monthly Stipend: 50,000 INR Location: Remote - India Programme Start: September 2026 Responsibilities: 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: You'll be a strong fit if you have: - 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. What the six months look like: Weeks 1–3: Environment, codebase tour, and a scoped starter charter that touches production. Y Weeks 4–16.: Your primary charter. One substantial piece of the platform that is yours to design, build, instrument, and ship. You'll present the design to the org and defend the tradeoffs. Weeks 17–24: Hardening, migration, and handoff — or extension into a second charter if the first lands early. Conversion conversations begin around week 18.