Responsibilities of the Candidate:

First-line technical support. Own initial triage for partner-facing technical issues - diagnose what's broken, resolve what you can directly, and route what you can't to engineering with enough context that it doesn't bounce back.
Scope automation opportunities. Spot the pattern behind repeat issues and turn it into a scoped opportunity for the product team - what's repetitive, roughly what it would take to fix at the platform level, and what it would save.
Client-facing communication. Talk to partners directly during issues - translating technical problems into plain language without underselling the problem or overwhelming a non-technical partner contact.
Internal coordination. Sit between partners and engineers - chasing fixes, setting expectations on both sides, and making sure at-risk timelines are flagged on time.
Read and modify code. Debug issues, make small fixes or configuration changes yourself where possible, and write precise, actionable bug reports for engineering when you can't.
Grow into solutions architecture. As the platform becomes more self-serve, take on more of the deployment-design and configuration-architecture work that reduces the need for manual triage in the first place.

Requirements:

Tech stack: Python and Node.js
Comfort reading and modifying code - you don't need to be a full-time engineer, but you should be able to debug real issues and make small fixes, not just describe them
Exposure to client-facing or partner-facing work - this role talks to real partners during real problems, often ones who aren't technical themselves
Great communication skills to translate complex problems into understandable issues and solutions
Enough technical grounding to eventually take on solutions-architecture work - understanding of APIs, deployment models, and configuration-driven systems will matter more over time, not less
Ability to handle pressure; partners come to this role when something's already broken
A pattern-recognition instinct - the automation-scoping half of this job depends on noticing what's repetitive, not just closing tickets
Comfort with a role that's designed to change - this isn't a fixed job description forever; the expectation is that both the work and the person's scope shift as the platform matures
Genuine interest in Karya's mission - ethical data work, fair compensation for data workers, and community ownership of data are core considerations, not side context