Tech Lead — DevX & AI
Confirmed on the employer's own hiring board on Oct 19, 2026. First seen by Alion on May 14, 2026. Xsolla scores B on the Alion truth index.
ABOUT YOU
We are looking for a Tech Lead to drive delivery and cross-team coordination for the Shop Builder DevX and AI team. You are the bridge between architecture and execution: you take the technical direction set by the Principal Engineer and turn it into a running, shipping team.
You lead a squad of three engineers building the developer surface that Shop Builder is missing - MCP server, CLI, SDK, documentation pipeline, local dev environment, deploy and versioning path. You set the delivery cadence, remove blockers, coordinate inbound dependencies from payments, auth, live ops, and catalog, and own the quality of what ships.
This is a hands-on role. You write production code, lead code reviews, and drive technical decisions within your domain. You also have the seniority and judgment to coordinate across teams and represent the team's work to engineering leadership.
ABOUT US
Xsolla is a global payments and commerce platform for the games industry, used by thousands of publishers to monetize, distribute, and operate their titles worldwide. Shop Builder is Xsolla's storefront platform - used by publishers and game developers to launch and operate game shops, from straightforward catalog and webshops to fully custom storefronts built headless on our backend. For more information, visit xsolla.com.
The DevX and AI team owns the public APIs, documentation, and AI features that give developers - and AI agents - the full surface they need to customize and extend Shop Builder. This is a net-new team of seven, standing up to fill a real gap: no dedicated team has owned the developer surface end to end. That changes now.
Responsibilities
Drive the delivery of the Shop Builder developer surface: MCP server, CLI and local dev environment, public SDK, documentation pipeline, sandbox and preview environments, deploy and versioning path.
Lead and mentor a team of three engineers - setting technical direction within the squad, running code reviews, and ensuring consistent engineering quality.
Own cross-team coordination: identify and pull inbound API capabilities from payments, auth, live ops, and catalog teams; unblock dependencies; manage integration timelines.
Actively contribute to implementation - you ship production code alongside the team, particularly on the most critical and complex components.
Partner with the Principal Engineer to translate architecture decisions into sprint-level execution plans and realistic timelines.
Collaborate with the PO on roadmap sequencing, scope decisions, and trade-offs between speed and correctness.
Own the team's delivery rhythm: sprint planning, technical grooming, retrospectives, and status visibility to engineering and business leadership.
Define and maintain the team's engineering standards: testing strategy, observability, deployment practices, and documentation quality.
Act as the primary technical contact for integrations with headless partners and the MIT professional services team during early partner onboarding.
Contribute to hiring by conducting technical interviews and defining what great looks like for the engineers joining this team.
Qualifications & Skills
6+ years of professional software engineering experience, with at least 2 years in a tech lead, staff, or senior lead role driving delivery across a team.
Strong proficiency in JavaScript/TypeScript and Node.js, with experience shipping production APIs, CLIs, or SDKs to external developers.
Hands-on experience building CLI tools and developer-facing workflows: command design, config file formats, local dev loops, deploy commands, and error messages that actually help.
Solid understanding of REST API design principles, SDK ergonomics, and what makes a developer experience work - you have strong opinions and can back them up.
Practical familiarity with the Model Context Protocol (MCP) or agentic tool-use patterns: you understand how AI agents consume tool interfaces and what makes a tool reliable for an LLM.
Experience coordinating across multiple engineering teams to ship features that depend on inbound capabilities you don't own.
Proven ability to lead engineers: clear technical direction, raising the quality bar through reviews, developing other engineers' skills.
Cloud-native experience: CI/CD pipelines, containerization (Docker/Kubernetes), and deployment automation on AWS or GCP.
Strong communication skills - you translate technical complexity into clear status for leadership, and technical requirements into actionable work for your team.
Nice to Have
Experience in game tech, digital commerce, storefront platforms, or headless architecture.
Background building React component libraries, design systems, or frontend platforms consumed by external developers.
Experience building sandboxed execution environments for third-party code (custom blocks, extensions, plugins).
Familiarity with LLM-generated code evaluation: assessing whether an AI-produced block, component, or layout is correct and safe to ship.
Prior experience standing up a greenfield team from scratch and knowing what that demands.
Exposure to documentation-as-code workflows and toolchains that publish to multiple surfaces from a single source of truth.