Own the outcome
Work backward from the decision, user, workflow, risk, and evidence—not a prewritten implementation ticket.
Careers at Innomium
Join a remote, research-minded engineering company working across AI models, software products, evaluation, data, edge systems, GPU infrastructure, reliability, design, and technical growth. We value evidence of craft, clear judgment, and ownership beyond the first release.

Innomium Agency
Craft · Curiosity · Accountability · Handover
Across engineering, AI, research, data, infrastructure, design, and technical growth.
International collaboration with explicit overlap, ownership, and written working practices.
We care about what you built, learned, measured, improved, and can explain clearly.
What the work feels like
Innomium is a place for people who want proximity to the technical question and responsibility for what happens after the prototype. Roles are broad enough to require judgment and focused enough to leave a meaningful body of work.
Work backward from the decision, user, workflow, risk, and evidence—not a prewritten implementation ticket.
Write decisions, build tests, expose limitations, and leave enough evidence for another person to challenge the result.
Researchers, engineers, designers, data specialists, and operators share the same delivery context.
Documentation, reliability, accessibility, observability, and handover are part of the definition of done.
What you can expect
We are deliberately not publishing unverified benefit promises. Role-specific compensation, engagement structure, benefits, eligibility, and overlap are discussed directly and early.
Understand why the work matters, who owns the decision, what evidence exists, and what still needs to be discovered.
Own a system, research question, product area, platform capability, or growth mandate—not only disconnected tasks.
Expect designs, experiments, code, writing, and product decisions to be challenged constructively and specifically.
Novel technology is welcome when it earns its complexity. Clear baselines and practical judgment matter more than fashion.
Hiring process
The exact sequence changes by role, but the process should remain focused, relevant, and respectful of the candidate’s time.
We review your note and relevant work for the role’s core mandate, not for keyword density.
Discuss a project, decision, failure, or body of work you know deeply and can explain honestly.
A technical, portfolio, or campaign discussion; any exercise should be bounded and directly relevant.
Align on mandate, team, remote overlap, engagement structure, compensation, eligibility, and start path.
Open roles
Every posting describes a real capability we are advertising. Apply with the evidence that best predicts your contribution, even if your path does not match every bullet.
Two ways to contribute
Employment and Arena participation are separate. Arena provides structured challenges and tasks for builders; it is not unpaid trial work for a job and does not guarantee employment.
Candidate respect
We do not require generic cover letters.
We avoid speculative, open-ended take-home work.
We discuss role structure and eligibility before a long process.
We do not sell or reuse candidate work as client deliverables.
The ten published roles are remote and open to international candidates, subject to role-specific time-zone overlap, contracting or employment availability, work authorization, and local legal requirements. We confirm those details early in the process.
We’re expanding
We’re actively growing across engineering, research, and product. Follow us on LinkedIn, GitHub, and Hugging Face to hear about new roles, releases, and the work we ship in public—without waiting for a careers-page refresh.
Open a role, then submit through the dedicated application page with your résumé and evidence of craft.
Built for accountable delivery
We begin with the operating constraint, agree on what success looks like, and build a delivery path your technical and business teams can review.
01
Scope, constraints, milestones, and decision owners before build work starts.
02
Evaluation plans, working artifacts, and reviewable technical decisions—not presentation-only progress.
03
Integration, observability, documentation, and an operating path for the teams who own the result.