Skip to content

Jobicy

Principal Manager, ML Solutions Architecture - Token Factory at Nebius

Jobicy is hiring a Principal Manager, ML Solutions Architecture - Token Factory at Nebius for a remote role. Level rates it ; you can apply on Jobicy.

Source: Jobicy. Level lists this role from Jobicy; you apply on their page.

Level's read on this job

  • Level rates this solutions architect role Little AI ●○○○: aI is not part of the work.
  • The posting lists this role as remote.
  • Tools and skills the posting cites include OpenAI, Anthropic and Bedrock.
  • Level lists 698 other open roles at Jobicy.
  • The role was posted in the last few days.

AI in this role

OpenAIAnthropicBedrockVertex AIvLLMSageMaker
fine-tuningml-ops

About Nebius:

Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure.

Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI.

Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.

The role

This position sits within Nebius Token Factory, our serverless platform for running and customizing open-source LLMs in production. Token Factory allows for serverless inference and fine-tuning backed by in-house optimizations like custom speculative decoding, quantization, cache-aware routing and dedicated endpoints. Customers come to us to move from prototype to scaled production without the cost and complexity of building and tuning their own inference stack.

Our Solutions Architects own the technical delivery of customer engagements: deploying open-source models, tuning the serving stack, benchmarking against the customer's success criteria, and carrying the technical relationship through to production. Sales Engineers qualify and scope the opportunity; SAs execute it. Technical Account Managers take it from production onward.

We're looking for a Principal Manager, ML Solutions Architecture to lead our EU regional SA teams. Your scope is PoC delivery and post-sales technical support: the people who do it, the standard they do it to, and the operating cadence that keeps it predictable. You will report to the Head of Solutions Architecture and partner with a peer manager in the other region.

We expect you to push people when they need pushing, make the uncomfortable call when deliverables don't land even though the effort was real, and take ownership of the documentation work: implement and monitor the following of the guidelines, ticket hygiene, and making sure the team actually uses all three.

You're welcome to work remotely from any EU country.

Your responsibilities will include:

Lead the team

  • Manage a team of 8 Solutions Architects, with continued growth planned: 1:1s, goal setting, performance reviews, promotion cases, and individual growth plans
  • Build an accurate picture of each SA's strengths, gaps, and preferences, and allocate accounts and engagements against both expertise and interest
  • Run the cadence that surfaces blockers early, then take them to the development, product, and business teams that can clear them, and stay on them until they do
  • Hold people to outcomes: distinguish effort from delivered results, say so plainly when the two diverge, and reflect it in ratings and compensation decisions
  • Onboard new joiners through to their first independently delivered engagement
  • Coach SAs into stronger engineers and stronger communicators, and make deliberate calls about who is ready for more scope

Own delivery

  • Be accountable for your team's delivery outcomes: time from PoC kick-off to first optimized dedicated endpoint, success-criteria hit rate, and the quality of the technical relationship after the customer goes to production
  • Review technical work before it reaches the customer: benchmarking methodology, serving configurations, results, closure documents; catch the wrong conclusion drawn from a metrics artifact before a customer sees it
  • Ensure staffing and escalation coverage across accounts and timezones, including post-sales request load that does not respect sprint boundaries
  • Call infeasibility early and with evidence, rather than letting the team burn iterations against requirements the platform cannot meet today

Own the operating system of the team

  • Maintain and extend the team's documentation: responsibilities, runbooks, guides, onboarding, definitions of done, engagement closure templates. Keep it accurate and reachable; link, don't copy
  • Get it used, not just written: documentation nobody reads is a cost, not an asset
  • Keep the ticket tracker the system of record, so PoC and production status is readable without asking anyone
  • Instrument the work: define and report the metrics that show whether delivery is getting faster and more reliable over time

Work across teams

  • Development and research teams: convert recurring customer pain into prioritized platform work, and represent the customer's technical reality in roadmap discussions
  • Pre-sales: hold the scoping-to-execution boundary: push back on under-scoped engagements, and feed feasibility signal back upstream
  • Account management: make production handoffs uneventful, and keep post-sales technical requests moving
  • Business and leadership: give a straight read on account health, technical feasibility, and capacity needs

We expect you to have:

  • 3+ years managing technical teams, including performance management and difficult conversations
  • Experience managing a customer-facing team. Running a team whose work is visible to customers, on customer timelines, with customer escalations.
  • Strong ML knowledge: LLM architectures, fine-tuning approaches (SFT/LoRA, RL-based), evaluation design, and a working command of inference internals — quantization, KV-cache management, batching, routing, speculative decoding — and of the frameworks the team works in (vLLM, SGLang, TensorRT-LLM)
  • Enough technical judgment to review someone else's benchmark and find the flaw in the methodology, not just in the conclusion
  • Python strong enough to read and review your team's code
  • Excellent communication skills, with the ability to clearly explain technical concepts to diverse audiences, from engineers to executives, including in front of enterprise customers under pressure
  • Genuine tolerance for operational work: documentation, process design, reporting, and the follow-through that makes them stick
  • Comfort operating with ambiguity across distributed teams and timezones, and a bias toward writing things down

It would be an added bonus if you have:

  • References from both former managers and former direct reports
  • Experience scaling a team through rapid growth (5 → 15+) without losing delivery quality
  • Prior experience in a customer-facing technical function at a cloud, inference, or AI infrastructure provider
  • Experience defining process and documentation for a team that had none
  • Hands-on background running LLMs in production and debugging inference workloads at the framework level
  • Work with multimodal AI models (vision-language, speech)
  • Proficiency with DevOps tooling (Docker, Kubernetes) and infrastructure-as-code

Preferred technical stack:

  • Programming languages: Python
  • ML frameworks and libraries: vLLM, TensorRT-LLM, SGLang, Transformers, OpenAI/Anthropic SDKs
  • MLOps and DevOps tools: Kubernetes (K8s), Docker, Git
  • Cloud platforms: AWS (SageMaker, Bedrock), GCP (Vertex AI), Azure (Azure ML)

Benefits & Perks:

  • Competitive compensation
  • Career growth and learning opportunities
  • Flexibility and ownership
  • Collaborative and innovative culture
  • Opportunity to work on impactful AI projects
  • International environment and talented teams

What's it like to work at Nebius:

Fast moving - Bold thinking - Constant growth - Meaningful impact - Trust and real ownership - Opportunity to shape the future of AI

Equal Opportunity Statement:

Nebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law.

Applicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire.

If you need accommodations during the application process, please let us know.

How we rate this

Principal Manager, ML Solutions Architecture - Token Factory at Nebius at Jobicy rates 11 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.

Classification

Little AI. AI is not part of the work.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

Fine-tuningML OpsOpenAIAnthropicBedrockVertex AIvLLMSageMaker

Also common in solutions architect jobs at this level

Pay

Typical solutions architect job
$169k

This posting doesn't list pay. Use the typical solutions architect figure when pay comes up. See solutions architect jobs

Questions you could be asked

  1. Walk me through fine-tuning a model: what data did you use, and how did you check the result?
  2. How do you monitor a model once it's live, and how do you know it needs retraining?
  3. What are the limits of OpenAI that you've run into, and how did you work around them?
  4. What's a project where you used Anthropic hands-on?
  5. Walk me through how you've used Bedrock in your day-to-day work.

Adapt your resume

  • List these exact terms on your resume: Fine-tuning, ML Ops, OpenAI, Anthropic, and Bedrock. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.

Get new remote solutions architect jobs by email

One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free.

Similar roles

Other roles that involve little AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at Jobicy

More solutions architect jobs

Related searches

Same AI level