Member of Technical Staff

Chakra Labs

Where
New York

Posted 7 months ago· Checked live at Chakra Labs 1 hour ago

Stale: open 225 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Chakra Labs asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Chakra Labs's own hiring page 1 hour ago.
What is the job?
Chakra Labs' mission is to encode human taste into intelligence. We build high-fidelity environments, evals, and datasets for frontier AI research, working with several of the top labs. Our work sits at the frontier of post-training, agent environments, data quality, and research infrastructure. We care about building systems that make models better in ways that are measurable, useful, and hard to fake.
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

Chakra Labs' mission is to encode human taste into intelligence. We build high-fidelity environments, evals, and datasets for frontier AI research, working with several of the top labs.

Our work sits at the frontier of post-training, agent environments, data quality, and research infrastructure. We care about building systems that make models better in ways that are measurable, useful, and hard to fake.

About you

  • Generalist range, infra depth. You're a strong engineer across the stack - backend services, data pipelines, enough frontend to ship a real interface - with genuine depth in systems. You'd rather own a whole problem than a layer of one.
  • Container orchestration. You're comfortable running Kubernetes or similar in production. Auto-scaling, pod lifecycle, persistent storage, networking. You can figure out why something won't schedule and reason about resource contention.
  • Distributed systems. You've built or maintained message-driven architectures. SQS, Kafka, or similar. You know how to keep jobs moving when things back up, retry without duplicating, and fail without losing work.
  • LLM infrastructure. You've run LLM workloads at scale. Token instrumentation, rate limit handling, prompt caching, multi-provider routing. You've built the plumbing between models and external tools, and you know what it takes to keep it all running under load.
  • Experience. No hard rule. Ideally at least 3 years at this level, but less works if the above sounds like you.

Similar open jobs

Jobs in New York (19148)