Wand

Data Analyst

• You'll own the metrics that run the business.
• You'll own the dashboards and definitions Product, Growth, Marketing, and Finance rely on every day.
• You'll build in Hex, document in our spec, and enforce consistent definitions across teams.
• When retention dips or a funnel leaks, you won't stop at the symptom.
• You'll follow the thread — through cohorts, segments, the quirks of specific games — until you can name the cause and recommend a fix.
• You'll design and analyze A/B tests on product changes, pricing, onboarding, and growth initiatives.
• You'll set sample sizes, call stat sig, and write the readouts.
• You'll work directly with our leaders on the questions that don't have obvious answers.
• You'll frame the question, run the analysis, and deliver the recommendation.

Product Data Analyst

Backend Engineer

• Own meaningful parts of the backend
• Scope, design, ship, and stabilize the services the rest of the product depends on. Own the fix when something misbehaves at 2am.
• Make the architectural calls — data model evolution, caching boundaries, where to spend latency budget, when to refactor and when to rewrite.
• Work fluidly across the data layer. Relational stores at scale (MySQL, MariaDB) and document stores (Firestore) are both in the toolkit, and you know which to reach for and when.
• Treat infrastructure as code as part of the job. Terraform and Ansible aren’t someone else’s problem; a service isn’t shipped until it can be re-deployed without you in the room.
• Treat performance, observability, and operational health as part of “done.” Dashboards and alerts ship with the feature.
• Move across the stack when the work demands it
• Open TypeScript PRs in the Electron app when a feature is better wired end-to-end than handed off. You’re comfortable on both sides of the boundary.
• Have opinions on UX workflows and product surfaces, not just API shapes. The best backend engineers we’ve worked with care how the thing feels.
• Get into the Electron app, the overlay, or the web surface when that’s where the bug actually is.
• Drive the backend roadmap
• Take ownership of what we work on, what we cut, and what we sequence. The Head of Engineering will partner closely early on; the bar is that this person eventually drives the roadmap on their own.
• Push cross-cutting initiatives nobody else will — observability gaps, data model debt, perf regressions, API hygiene. The work that quietly compounds.
• Provide substantive code review, mentor where it lands naturally, and raise the level of design discussions when the design needs it, not just the implementation.
• Bring thoughtfulness and genuine passion for the work. Contribute to roadmap decisions with an eye on outcomes.

Senior Backend Engineer

QA Engineer

• Test and validate game modifications across a wide range of PC titles
• Meet established performance metrics and testing KPIs
• Document and report findings with detailed attention to functionality and user experience
• Provide structured feedback to improve mod instructions and descriptions

QA Tester – Latin America Region, Weekend Shift

• Build and own native infrastructure.
• Own substantial parts of Wand’s Windows native stack and move fluidly across the breadth of it.
• Make the architectural calls that compound.
• Design SDK and plugin surfaces that other people actually want to build against.
• Treat the application teams as your customers.
• Write the docs, examples, and small tools that turn “ask the native team” into “look it up.”
• Provide substantive and thoughtful code reviews.
• Mentor mid-level engineers through the parts of Windows that aren’t on Stack Overflow.
• Contribute to roadmap decisions with an eye on outcomes.

Product Data Analyst

Senior Backend Engineer

QA Tester – Latin America Region, Weekend Shift

Senior Windows C++ Engineer