Raft is actively hiring for 3 AI and machine learning positions, concentrated in MLOps Engineer (2) and AI Software Engineer (1) roles. Positions are based in Tampa, FL, Honolulu, HI. Mid-level roles account for 66% of openings.
Locations
Tampa, FL, Honolulu, HI
Hiring by Role Category
Open Positions (3)
ML Ops Engineer
Software Engineer (AI Focus)
Principal MLOps Engineer
What Raft's hiring tells you
With 3 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 Raft 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?
Raft AI and ML Hiring
Raft has 3 active AI and ML roles in our dataset. Open positions span MLOps Engineer, AI Software Engineer. Roles are based in Tampa, FL, Honolulu, HI.
Salary Benchmarks
The market median for AI roles is $213,380. MLOps Engineer roles pay a median of $205,000 across the market. AI Software Engineer roles pay a median of $220,000 across the market. Top-quartile AI compensation starts at $264,148.
Skills in Demand
Kubernetes, Docker, and cloud infrastructure are baseline. Most roles want experience with ML-specific tooling: MLflow, Kubeflow, Weights & Biases, or similar. Strong DevOps fundamentals matter more than ML theory. You need to understand model serving (TorchServe, Triton, vLLM), monitoring (Prometheus, Grafana), and infrastructure-as-code (Terraform, Pulumi).
GPU infrastructure knowledge is increasingly valuable as LLM inference becomes a major cost center. Understanding GPU scheduling, multi-node training setups, and inference optimization (quantization, batching, caching) puts you in the top tier. Experience with model registries and feature stores rounds out the profile.
Good MLOps postings specify their ML stack, infrastructure scale, and the problems they're solving (deployment velocity, cost optimization, monitoring gaps). Red flag: companies that want MLOps but don't have any models in production yet. You'll end up doing general DevOps instead.
AI Role Categories
MLOps Engineer
MLOps Engineers build the infrastructure that keeps ML models running in production. They own CI/CD pipelines for model deployment, monitoring for data drift and model degradation, and the tooling that lets data scientists ship faster. If ML Engineers build the models, MLOps Engineers build the roads those models travel on.
Kubernetes, Docker, and cloud infrastructure are baseline. Most roles want experience with ML-specific tooling: MLflow, Kubeflow, Weights & Biases, or similar. Strong DevOps fundamentals matter more than ML theory. You need to understand model serving (TorchServe, Triton, vLLM), monitoring (Prometheus, Grafana), and infrastructure-as-code (Terraform, Pulumi).
Market compensation for MLOps Engineer roles: $205,000 median across 151 positions with disclosed pay.
AI Software Engineer
AI Software Engineers build the applications and systems that AI models run inside. They own the API layers, data pipelines, frontend integrations, and infrastructure that turn a model into a product users interact with. Every AI company needs engineers who can build the software around the AI.
Full-stack engineering skills with AI integration experience. Python and TypeScript are the most common requirements. You'll need to understand API design, database architecture, and how to build reliable systems around probabilistic outputs. Experience with streaming, async processing, and caching patterns is increasingly important as real-time AI applications proliferate.
Market compensation for AI Software Engineer roles: $220,000 median across 1,448 positions with disclosed pay.
The AI Job Market Today
The AI job market spans 8,943 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (6,739), AI Product Manager (403), AI Software Engineer (402). 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 (175) are outnumbered by mid-level (4,132) and senior (3,268) 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,368 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (521 positions), with 8,351 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,380. Top-quartile roles start at $264,148, and the 90th percentile reaches $319,310. 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,422 postings), Aws (808 postings), Azure (638 postings), Rag (555 postings), Gcp (457 postings), Pytorch (433 postings), Claude (341 postings), Kubernetes (337 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 8,943 open positions tracked in our dataset. By seniority: 175 entry-level, 4,132 mid-level, 3,268 senior, and 1,368 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (521 positions). The remaining 8,351 roles require on-site or hybrid attendance.
The market median for AI roles is $213,380. Top-quartile compensation starts at $264,148. The 90th percentile reaches $319,310. 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).
MLOps demand tracks closely with production ML adoption. As more companies move models from notebooks to production, the need for MLOps grows. The role is well-established at large tech companies and growing fast at mid-stage startups that are hitting the 'our models work in notebooks but break in production' phase.
What to Expect in Interviews
Interviews emphasize infrastructure and reliability. Expect questions about CI/CD for ML models, monitoring for data drift, and how you'd design a model serving platform that handles 10K requests per second. Coding rounds focus on Python and infrastructure-as-code (Terraform, Helm). Be ready to discuss tradeoffs between different model serving frameworks and how you'd handle rollback when a new model degrades performance.
When evaluating opportunities: Good MLOps postings specify their ML stack, infrastructure scale, and the problems they're solving (deployment velocity, cost optimization, monitoring gaps). Red flag: companies that want MLOps but don't have any models in production yet. You'll end up doing general DevOps instead.
Career Path
Common paths into MLOps Engineer roles include DevOps Engineer, Platform Engineer, Data Engineer.
From here, career progression typically leads toward ML Platform Lead, Infrastructure Architect, Engineering Manager.
DevOps engineers with ML curiosity have the shortest path. You already understand deployment, monitoring, and infrastructure. Add ML-specific knowledge (model serving, data pipelines, experiment tracking) and you're competitive. The career ceiling is high: ML Platform Lead roles at top companies pay well because the infrastructure complexity is enormous.
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.