Clera is actively hiring for 2 AI and machine learning positions, concentrated in LLM Engineer (1) and AI/ML Engineer (1) roles. Positions are based in Munich, Bavaria, Germany, San Francisco, CA. Mid-level roles account for 100% of openings.
Locations
Munich, Bavaria, Germany, San Francisco, CA
Hiring by Role Category
Open Positions (2)
AI/LLM Engineer
Machine Learning Engineer
What Clera's hiring tells you
With 2 active AI role(s), this company is in the early exploration phase. That can mean either a pilot project being staffed up or a small embedded AI function inside a larger team. Worth investigating directly: ask the recruiter how the AI work is funded and who it reports to. Compensation is not disclosed in postings, which is increasingly out of step with how AI talent expects to be hired.
Questions worth asking in the Clera interview loop
The signals above come from public job postings. The signals you actually need come from the conversation. A few questions calibrated to this company's tier:
- Is this AI work funded for at least 18 months, or is it tied to a specific project deadline?
- Will I be the only person doing this, or are there others I will collaborate with day to day?
- What does success look like at six months? At eighteen months?
Clera AI and ML Hiring
Clera has 2 active AI and ML roles in our dataset. Open positions span LLM Engineer, AI/ML Engineer. Roles are based in Munich, Bavaria, Germany, San Francisco, CA.
Salary Benchmarks
The market median for AI roles is $213,400. LLM Engineer roles pay a median of $160,000 across the market. AI/ML Engineer roles pay a median of $212,000 across the market. Top-quartile AI compensation starts at $264,230.
Skills in Demand
RAG and vector databases are the most common requirements. Expect to work with LangChain or LlamaIndex, embedding models, and at least one vector store (Pinecone, Weaviate, Chroma). Python is non-negotiable. Understanding the cost/latency/quality tradeoffs between different model providers and architectures is what separates senior from junior engineers.
Fine-tuning experience is valuable for specific use cases but most production LLM work is RAG-based. Agent frameworks (LangGraph, CrewAI, custom orchestration) are increasingly important as companies move beyond simple chat interfaces. Evaluation and observability tools (LangSmith, Arize, custom dashboards) are essential for production deployments.
Look for roles that specify the production stack, mention specific use cases, and talk about cost optimization. Companies that understand LLM engineering will mention evaluation methodology, latency requirements, and scale targets. Vague 'build AI features' postings often mean they haven't figured out their architecture yet.
AI Role Categories
LLM Engineer
LLM Engineers specialize in building applications powered by large language models. They design RAG systems, fine-tune models, build agent frameworks, and optimize inference pipelines for cost and latency. This is the role that didn't exist three years ago and now has thousands of open positions.
RAG and vector databases are the most common requirements. Expect to work with LangChain or LlamaIndex, embedding models, and at least one vector store (Pinecone, Weaviate, Chroma). Python is non-negotiable. Understanding the cost/latency/quality tradeoffs between different model providers and architectures is what separates senior from junior engineers.
Market compensation for LLM Engineer roles: $160,000 median across 33 positions with disclosed pay.
AI/ML Engineer
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Market compensation for AI/ML Engineer roles: $212,000 median across 11,857 positions with disclosed pay.
The AI Job Market Today
The AI job market spans 9,653 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,301), Data Scientist (441), AI Software Engineer (438). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (193) are outnumbered by mid-level (4,500) and senior (3,455) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,505 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (568 positions), with 9,010 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $213,400. Top-quartile roles start at $264,230, and the 90th percentile reaches $319,400. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $253,100 median, while Prompt Engineer roles sit at $141,440. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (1,605 postings), Aws (916 postings), Azure (724 postings), Rag (634 postings), Gcp (522 postings), Pytorch (495 postings), Kubernetes (384 postings), Claude (383 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
AI Hiring Overview
The AI job market has 9,653 open positions tracked in our dataset. By seniority: 193 entry-level, 4,500 mid-level, 3,455 senior, and 1,505 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (568 positions). The remaining 9,010 roles require on-site or hybrid attendance.
The market median for AI roles is $213,400. Top-quartile compensation starts at $264,230. The 90th percentile reaches $319,400. Highest-paying categories: AI Safety ($253,100 median, 57 roles); Research Engineer ($252,000 median, 419 roles); AI Engineering Manager ($251,622 median, 51 roles).
LLM Engineer is one of the fastest-growing AI job titles. Every company building AI-powered products needs people who understand the full stack: from embedding models to vector stores to inference optimization. The supply of experienced LLM engineers is thin because the field is so new, which keeps compensation high and demand strong.
What to Expect in Interviews
Technical screens cover RAG architecture design, embedding model selection, chunking strategies, and retrieval evaluation. Expect questions about cost optimization: how you'd reduce inference costs by 50% without degrading quality. System design rounds often present scenarios like 'design a customer support chatbot that can access 100K documents' and evaluate your understanding of the full stack from embedding to serving.
When evaluating opportunities: Look for roles that specify the production stack, mention specific use cases, and talk about cost optimization. Companies that understand LLM engineering will mention evaluation methodology, latency requirements, and scale targets. Vague 'build AI features' postings often mean they haven't figured out their architecture yet.
Frequently Asked Questions
Frequently Asked Questions
Related Resources
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.