Interested in this AI/ML Engineer role at ubiqs?
Apply Now →About This Role
This is not a standard job post.
We are looking for a co-founder to own the technology side of our NPU: innovation, architecture and implementation, from the first idea to silicon.
What we are building
An AI inference accelerator built from a clean sheet. Two ideas drive the design.
- No back and forth of weights. Inference today spends most of its energy and time moving weights between memory and compute. We want an architecture where the weights stay put and the compute comes to them.
- Agent context as a first-class tier. Long-running agents hold context for hours. The chip and the memory system have to be designed for that from day one, not for short prompts.
The bar
We are looking for someone who dreams of beating the GPU, Google's TPU, the LPU and Cerebras at inference, not matching them. You know exactly where each one wins and where each one leaves performance on the table, and you have a specific idea of how to do better. If your answer to "why hasn't someone already done this?" is thin, this is not for you.
Challenges you have already tackled
We want to hear about hard problems you have taken on yourself, in areas such as:
- DRAM: Have you dealt with DRAM limits head on? Bandwidth walls, capacity, cost and supply shortages. Did you invent a way around them: designs that need less DRAM, keep more on chip, tier memory differently, or make a scarce part go further? DRAM is the constraint that shapes every inference chip today, and we want the person who has already fought it.
- Weight and data movement: cutting memory traffic, keeping weights resident, compute-in-memory, near-memory compute, dataflow and tiling choices that changed the numbers.
- Power and energy: performance per watt, on-chip memory hierarchy, precision and quantization choices, and where the joules actually go in decode.
- Agentic AI workloads: long context, growing KV cache, prefill versus decode, checkpointing and restoring state, and how these change what an inference chip needs.
- Silicon delivery: RTL and micro-architecture, verification against a golden model, and the road from proof of concept through FPGA and emulation to tape-out.
Tell us what you measured, what surprised you and what you would do differently. Specifics beat titles.
You
- You have a startup founder's mentality. You have built something from nothing, or you are itching to. You make decisions with incomplete information, work with a small team and limited money, and treat constraints as design inputs, not excuses.
- You are in the thick of AI, GPUs and neural processing chips, and you have done the homework. You know what is in the market and you think you can do it 10X better.
- You have taken RTL and micro-architecture to silicon, or come very close.
- You have a view on how LLMs and agents will change what an inference chip needs, and you can defend it against people who disagree.
- You are ready to put skin in the game. You are not looking for a job.
- You lose sleep over this. That is the reason you are reading this.
What you would own
- Architecture and technical roadmap for the NPU, from proof of concept through tape-out.
- The build-out of the engineering team and the choice of tools, partners and foundry path.
Compensation, stated plainly
This is equity only. There is no salary until we close external funding, and we will not pretend otherwise. You would be a founding partner with meaningful ownership, on vesting terms agreed up front and put in writing before you commit. Once funding closes, compensation moves to a market-appropriate salary plus your equity. If you need a paycheck from day one, this is not the right fit. If you want to build the chip that defines the company, it is.
How to respond
Send your story, not a résumé alone. Tell us which of the challenges above you have tackled, especially how you handled DRAM, what you think the market gets wrong about inference silicon, and what you would do first.
Role Details
About This Role
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.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At ubiqs, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills in Demand for This Role
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.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. C-Level-level AI roles across all categories have a median of $250,000.
Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.
ubiqs AI Hiring
ubiqs has 3 open AI roles right now. They're hiring across AI/ML Engineer.
Location Context
Across all AI roles, 6% (580 positions) offer remote work, while 9,776 require on-site attendance. Top AI hiring metros: New York (3,785 roles, $222,480 median); San Francisco (3,262 roles, $261,300 median); Los Angeles (1,896 roles, $210,000 median).
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.
The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). 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 (117) are outnumbered by mid-level (4,975) and senior (3,840) 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,487 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 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 $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. 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 $274,500 median, while Prompt Engineer roles sit at $140,000. 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 (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 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.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.