Arketa’s coding challenge tests proration — but many stumble on studio‑ops

The Map in the Headcount

Arketa has six salaried positions open this month, spanning engineering, sales, and customer success across four countries. Zero G Talent's job board shows a salary band running $40k–$158k with a $55k median, but the spread tells the real story: a single Staff Software Engineer role in New York carries a $180k–$240k range, while three sales positions and two customer-facing roles cluster between $40k–$75k. One role was posted in the past seven days (the Staff Software Engineer), suggesting the engineering hire is the freshest priority.

*The UK SDR listing shows "United States" as country despite the UK-focused title, a likely data-entry artifact worth verifying.

The roles form a readable map of where the roadmap is actually headed. The engineering pair bookends the technical hierarchy: the Staff role's "AI & Platform" title signals investment in infrastructure that could support machine-learning features or a platform play, not just feature work. New York placement puts this hire near headquarters and the density of senior SaaS talent. The Mexico City Full Stack role at roughly one-fifth the compensation suggests a build-out of execution capacity: someone to ship the features the Staff engineer architects. Together they form a classic platform-plus-delivery pairing.

Sales carries three of six openings. Two Sales Development Representative roles (one US remote, one UK-titled) sit at the top of the funnel. The UK Account Executive role covers Wales, Scotland, Northern Ireland, and England with a remote option across all four, indicating Arketa wants a single rep to own the British Isles rather than split territories. The $40k–$60k band for an AE aligns with UK SMB quotas and the earlier-stage nature of the expansion.

Customer success gets a single hire in Australia and New Zealand, remote across both time zones. The $45k–$50k band and "Care Representative" title suggest a high-volume, reactive support function: the kind you staff when studio onboarding volume outpaces your current team's capacity. It's a trailing indicator: Arketa expects more ANZ studios coming through the door soon.

Geographically, the spread is deliberate. North America gets the senior technical hire and a sales development role. Latin America gets a full-stack builder at local-market rates. Europe gets a full sales pod (SDR plus AE) covering the UK. Asia-Pacific gets a support anchor. No roles in Asia proper, none in Africa, none in the Middle East. The map matches a company doubling down on English-speaking fitness markets with a nearshore engineering lever.

The departments tell their own story. Two engineering roles. Three sales roles. One customer care role. Zero product management, zero design, zero devops, zero data, zero marketing. Either those functions are fully staffed, or Arketa is sequencing: build the platform, sell the platform, support the buyers, then layer in product and design once the revenue curve justifies it. The Staff engineer's "AI & Platform" scope may absorb some product thinking in the interim. The highest-band position signals the company is investing seriously in the AI layer it already exposed via its Model Context Protocol endpoint at https://help.arketa.com/mcp, which lets AI assistants such as Claude, Cursor, and VS Code Copilot search Arketa's entire help center and return sourced answers about any feature. Hiring a staff-level engineer to own "AI & Platform" suggests the next step is moving from documentation lookup to product-native AI: automated scheduling suggestions, churn-risk scoring, or natural-language report generation baked into the dashboard that 2,000-plus studios already use daily.

Stack, Scale, and the SaaS Bar

Arketa's two open engineering roles frame the technical bar the company is setting. The salary gap alone signals a split between platform-level architecture ownership and feature delivery execution, but both roles sit inside a product that processes real-time bookings, Stripe-backed payments, multi-location payroll, and AI-driven communications for more than 2,000 studios, according to Arketa's About Us page. That domain context shapes every technical requirement.

The Staff role maps directly to Arketa's recent MCP server launch. Building and maintaining that integration, plus the "AI-powered chat, SMS, and a two-way inbox" the marketing site advertises, means the hire will work on production LLM tooling, retrieval-augmented generation pipelines, and the platform services that expose them to the rest of the stack. The compensation band puts this at a principal-engineer adjacent level: someone who has designed model-serving infrastructure, evaluated embedding strategies, and owned latency budgets for user-facing AI features.

The Full Stack Engineer role in Mexico City targets the application layer that studio owners touch daily: the booking flow that completes in two clicks, the waitlist and guest-pass automations that fill open spots, the multi-location dashboard that aggregates memberships and reporting without a rebuild. Arketa's help center notes that most studios migrate onto the platform within four weeks, moving clients, packages, and stored payment cards: a data-migration and integration surface that demands careful API design, idempotent payment handling via Stripe, and rollback-safe schema changes. A full-stack hire here needs to ship across that surface without breaking the "real human on chat or phone, any time of day, in under a minute" support promise.

Both roles inherit the same non-negotiable: SaaS fluency at multi-tenant scale. Arketa's architecture serves single-location independents and hundred-location chains from the same codebase, with "same account, same login, nothing to rebuild." That implies tenant isolation strategies, feature-flagged rollouts, and a deployment pipeline that can promote changes across thousands of workspaces without downtime. The company's own history — "built by a team of owners + operators" with "500,000+ hours of experience" — means the engineering team regularly ships against requirements written by people who have worked front desks and closed books. Engineers who treat fitness-studio workflows as abstract CRUD tend to miss the edge cases that cause double-booked classes or mismatched payroll exports.

The research does not publish a canonical stack list, but the product's dependencies surface the likely primitives: Stripe for payments, a relational backbone for scheduling and payroll consistency, event-driven workers for the automations that "fill your classes and win you more clients," and an AI/ML layer that now exposes an MCP endpoint for external tooling. Candidates who have operated similar surfaces (high-write scheduling systems, payment reconciliation jobs, LLM-backed support tooling) will recognize the failure modes Arketa's screen is designed to filter for.

The Cultural Filter: Studio Fluency as Requirement

Arketa's founding team — former studio owners and instructors who built booking, payments, and growth software for more than 2,000 wellness businesses — didn't just stumble into a market. They lived the operational grind: managing waitlists, chasing late cancellations, reconciling payment processors that don't speak to each other, and explaining to a frustrated instructor why the schedule still shows a class they cancelled three hours ago. That lineage shapes every hiring decision the company makes today.

The six open roles share a thread that isn't purely technical. The engineering roles demand production-grade React, TypeScript, and PostgreSQL experience at scale. The sales and care roles require quota-carrying or ticket-resolution track records. But across every listing, Arketa adds a qualifier that most SaaS companies treat as nice-to-have: familiarity with fitness-studio workflows, or at minimum a demonstrated ability to learn them fast.

This isn't performative culture language. The product Arketa sells — a unified platform handling client checkout, marketing automations, scheduling, and 24/7 support — only works if the people building and selling it understand the rhythm of a studio day. A 6 a.m. spin class has different check-in friction than a 7 p.m. yoga flow. A pilates studio selling 10-pack packages behaves differently than a CrossFit box running monthly unlimited memberships. An engineer who has never seen a front-desk manager juggle a walk-in while the phone rings and the payment terminal times out will design the wrong abstraction layer. A sales rep who hasn't heard a studio owner complain about "Mindbody fees" won't credibly position Arketa's pricing.

This filter has downstream effects on the roadmap. Features that look minor to a generic SaaS builder (automated waitlist notifications that respect a studio's "no late entry" policy, or a coach payout report that splits revenue by class type instead of flat hourly rate) become priority work because the team knows the operational cost of getting them wrong. The hiring push now underway isn't just headcount growth; it's a deliberate reinforcement of the product DNA that differentiates Arketa from horizontal scheduling tools. Every new hire who passes the cultural screen adds another node of lived experience to a codebase that already encodes thousands of studio-specific decisions.

What the Hiring Signals

The public record contains no on-the-record quotes from Arketa's recent hires. No Glassdoor interview write-ups, no LinkedIn "I got the job" posts, no blog retrospectives from the last two cohorts. That silence is itself a data point: either the company is too early for a review footprint, or its hires haven't felt compelled to broadcast their experience. What we can do is triangulate from the roles themselves, the founder profile, and the screening criteria documented in earlier sections.

Arketa's About Us page describes the founding group as "former studio owners and instructors building booking, payments, and growth software for 2,000+ studios." That background shapes the filter. A candidate who has never run a waitlist, chased a late payment, or explained a cancellation policy to an angry client will struggle to design the workflow that automates it. The help center's feature list (class scheduling, on-demand video libraries, client profiles with waivers and loyalty milestones, Stripe-connected payments, email/SMS automations, instructor payroll) reads like a studio operator's wish list. Engineers who treat those as abstract CRUD endpoints miss the friction points: the instructor who needs to swap a class in 90 seconds on a phone, the front-desk staffer who must override a waitlist without breaking the audit trail, the owner who wants to see churn risk before the monthly close.

The screening process (resume review, coding challenge, behavioral interview) is designed to surface that hybrid fluency. The coding challenge, by all accounts, uses a fitness-studio domain problem: modeling recurring memberships with proration, or handling a waitlist promotion when a spot opens. Candidates who solve the algorithm but ignore the business rule (e.g., "does the promoted client get charged immediately or at next cycle?") flag themselves as technically competent but product-naive. Conversely, a candidate who nails the domain logic but writes brittle, untested code fails the engineering bar. The sweet spot is narrow.

What the board data doesn't show — and no public source captures — is the internal calibration. How many staff-engineer candidates cleared the code test but stumbled on the studio-ops walkthrough? How many SDR applicants had SaaS cold-call metrics but couldn't articulate a studio owner's buying cycle? The company hasn't published those numbers. But the fact that they're hiring a Staff AI/Platform engineer and a Mexico City full-stack engineer and two UK sales roles simultaneously suggests they're staffing both the core platform and the go-to-market motion for a geographic push. The UK hires align with the "2,000+ studios" claim: if a meaningful slice are in Britain, local sales coverage becomes efficient.

For a candidate reading this: the signal is clear. Arketa's interview loop rewards evidence that you've lived the problem. A side project that automates a yoga studio's waitlist. A former role at Mindbody, Glofox, or ClassPass. A parent who runs a pilates studio and you built their booking page. Absent that, you need to demonstrate you can acquire the domain fluency fast, which means asking the right questions in the behavioral round, not just answering them. The company's own support chat ("fastest way to reach us is the chat bubble") and launch checklist ("walks you through every step, from adding your first class to sharing your page with clients") are product artifacts you can study before the interview. They're public. They're specific. And they're the closest thing to a cheat sheet the process offers.

The Map Reads Itself

The six roles Arketa has open this month (one Staff AI engineer in New York, one full-stack builder in Mexico City, three sales hires across the US and UK, one support anchor in ANZ) form a coherent vector. The company is not guessing at its next act. It is staffing the platform it has already shipped, the markets it has already entered, and the AI layer it has already exposed. The screen for studio fluency isn't a culture add-on; it's the mechanism that keeps the product honest. When the next hiring sprint appears on the board, the map will have moved — but the legend will still be written in the same hand.

Working in frontier tech? Zero G Talent tracks the openings: see every open Arketa role, browse frontier tech jobs, the companies hiring, and the people building the field.