Staff Software Engineer Smart Wallet & Account Abstraction at Xsolla

Job description

About Xsolla Xsolla is a global commerce company with robust tools and services to help developers solve the inherent challenges of the video game industry. From indie to AAA, companies partner with Xsolla to help them fund, distribute, market, and monetize their games. Grounded in the belief in the future of video games, Xsolla is resolute in the mission to bring opportunities together, and continually make new resources available to creators. Headquartered and incorporated in Los Angeles, California, Xsolla operates as the merchant of record and has helped over 1,500+ game developers to reach more players and grow their businesses around the world. With more paths to profits and ways to win, developers have all the things needed to enjoy the game. For more information, visit xsolla.com . About the Role We are hiring a Staff Software Engineer to own the smart wallet and account abstraction layer of Xsolla ZK , Xsolla 's Web3 platform on a zkSync-based L2. This is an individual contributor role with a large technical scope. You are the technical anchor for how millions of players get an on-chain account they never have to think about. The product. Every player who signs in with Xsolla ID receives a deterministic, non-custodial smart account. The account is derived from their identity claim, is identical on every device, and its private keys never leave the client. It is not a separate wallet screen: it is the player's inventory. It backs: minting and gifting; trading on our Bazaar marketplace; Merkle-based reward airdrops; gas sponsorship; an in-app dApp browser that exposes the same signer to third-party applications through an EIP -1193 provider. Responsibilities The technical strategy and architecture of the smart wallet platform: account model, signing, session management and gas abstraction at scale The smart account and permissioning model, evolved to meet both product and compliance needs The security model where our signer meets third-party applications: what a player is actually approving, and proof that the UI shows it The custody and recovery roadmap, from today's interim mechanisms (including raw key export) to MPC -based custody Cross-team technical decisions on account architecture, SDK contracts, data modeling and platform reliability, with buy-in from the wallet, marketplace, SDK, mobile and security teams Engineering standards in the Web3 domain Production escalations in the wallet and account abstraction domain WHAT YOU WILL DO Design and evolve the ERC -4337 user operation lifecycle (prepare → sign → submit → confirm), EIP -7702 delegation, deterministic address derivation from identity, and the session-key and permission primitives (including origin-bound Smart Sessions) that let players act without a prompt on every transaction Set the paymaster and gas-sponsorship strategy: what we sponsor, how we meter and cap it, how we defend it from abuse, and how it degrades when sponsorship is unavailable Define EIP -1193 / EIP -6963 provider behavior, origin-bound and policy-versioned sessions, trust tiers, and the transaction and signature confirmation flow Design recovery paths (passkeys, guardians, social recovery) that a non-crypto-native player can complete without losing assets Identify systemic risks (key management, signature phishing, reorgs and indexer staleness, bundler and RPC dependencies, contract upgrade paths) and lead initiatives that resolve them before they become incidents Write RFCs and design docs; review critical code, contracts and designs Work with product, security, legal and infra teams to align on the roadmap and turn business and regulatory needs into well-scoped technical plans Create leverage for the engineering org through documentation, tooling and mentorship Serve as the escalation point for complex production issues: a stuck user operation, a drained paymaster, a signing prompt a player didn't understand Set up and maintain AI tooling in the repositories (Claude Code, Codex, Curso