Miami, FL
ML engineering recruiting for production model teams. Crosscheck recruits AI/ML & LLM Engineering candidates for contract, contract-to-hire, and permanent roles tied to Miami.
What We Place
Representative roles
Platforms and technologies
Our Approach
This editorial hiring guide starts with sourced Miami business context. Miami-Dade County materials identify international trade, aviation, financial services, information technology, and life sciences as separate economic-development targets. Hiring briefs need to distinguish border-spanning operations from regulated business systems and research work. A Machine Learning Engineer search needs a defined prediction task, training data owner, deployment path, and measure of useful performance. The same title can describe notebook research, feature engineering, backend development, or ownership of an inference service.
Screen ML engineers on modeling fundamentals and production tradeoffs
Match experience to the ML stack, data, and problem defined in the brief
target a first candidate slate within 48 hours for qualified exclusive searches in our core disciplines after a completed intake
Permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Start the search
Include the business context, systems, delivery phase, work model, compensation, and interview timeline. A Crosscheck search lead will use that context to calibrate the role before sourcing begins.
Local Market Brief
Write the brief around the model lifecycle. Include label creation, feature pipelines, experiment tracking, service integration, monitoring, and retraining duties that belong to this hire. Separate those duties from work owned by data, platform, or research teams. The three sourced Miami contexts below turn that scope into intake and screening decisions. They do not measure current vacancies, candidate supply, or Crosscheck client activity.
Editorial market scenario
List the production decisions the hire must own. Use those decisions to assess candidates whose prior title or industry differs from the opening. This is planning guidance, not measured local demand.
Editorial industry scenario
A finance-facing brief should identify the transaction, reporting, audit, privacy, and availability requirements attached to the role. Confirm that this context applies to the employer before using it in the search.
Screening focus
We test for model or application ownership, evaluation discipline, data judgment, and evidence that the candidate has shipped reliable AI systems.
Published labor benchmark
BLS does not publish an occupation matching ML Engineer. Crosscheck uses Data Scientists (15-2051) as the closest published broad benchmark; it is not a count or pay estimate for this exact specialty.
BLS OEWS May 2025, published May 15, 2026
Published metro employment
3,040
BLS publishes a narrower metro employment estimate for the proxy occupation. Screen for adjacent experience that transfers without lowering the production bar. The estimate equals 1.079 jobs per one thousand across the metro workforce.
Employment concentration
0.64 location quotient
Miami-Fort Lauderdale-West Palm Beach, FL reports a below-national employment concentration for this proxy occupation. Decide which requirements justify a wider regional or remote search.
Annual wage reference
$62,590 to $199,130
The metro median is 6% above the national Data Scientists median. Test whether the role's scope and location requirement support that difference. BLS reports a $127,450 median for the proxy occupation in Miami-Fort Lauderdale-West Palm Beach, FL.
Hiring brief scenarios
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Miami demand, clients, or candidate supply.
Sourced international trade and logistics context
Miami-Dade County describes international trade as a central part of the local economy and ties that work to PortMiami, Miami International Airport, and the region's trade and logistics organizations. Tie the sector scenario to a concrete outcome and data-generating process. Ask how the engineer would detect label leakage, sampling bias, missing history, and a metric that looks strong but fails the business use case. Trade systems can cross carriers, ports, customs, warehouses, customers, currencies, and time zones while goods and financial records move on different schedules.
Evidence to request: Review a feature or training pipeline and ask the candidate to trace one record from source through validation, training, and evaluation. Trace one shipment or trade transaction through partner interfaces, status events, exceptions, financial postings, reconciliation, retention, and support ownership.
Sourced aviation and aerospace context
Miami-Dade lists aviation and aerospace among the industries sought through its Targeted Jobs Incentive Fund and identifies airport areas among its strategic locations. Define the inference environment before screening. Batch scoring, low-latency APIs, edge deployment, and analyst-facing tools require different software design and operating evidence. Aviation work may join maintenance, assets, schedules, passengers, cargo, safety controls, secure access, vendors, and finance systems that must stay available during extended operating hours.
Evidence to request: Use a production scenario with throughput, latency, and reliability limits. Require an API or batch design plus a test plan. Identify the flight, cargo, maintenance, airport, or manufacturing boundary, then document uptime, access, audit, interface, and recovery requirements.
Sourced finance, technology, and life sciences context
The same Miami-Dade incentive program names financial and professional services, information technology, and life sciences among the industries the county seeks to support. Assign responsibility for drift, retraining, and model retirement. Candidates should explain the thresholds, review cadence, and human decision that follows an alert. These sectors can require transaction controls, protected records, validated calculations, model oversight, research traceability, or access reviews, depending on the system and business process.
Evidence to request: Ask for a model degradation example and the evidence used to separate data change, code change, and user-behavior change. Name the sector, record type, regulated boundary, system of record, control owner, change authority, and evidence required for acceptance.
Interview scorecard
Ask each candidate the same core questions. Score the evidence, ownership, and judgment in the answer instead of relying on job-title or keyword matches.
1. ML Engineer: PyTorch
Choose a PyTorch decision from your work as ML Engineer. Which constraint changed the design, and what evidence supported the result?
Use the answer to assess model evaluation, sensitive-data handling, explainability, and controls around automated decisions. The finance and insurance systems context is an editorial scenario, not a measured claim about Miami.
2. Senior ML Engineer: TensorFlow
Describe project work you completed as Senior ML Engineer involving TensorFlow that did not follow the original plan. What did you own, and how did you correct it?
Use the answer to assess evaluation tied to user tasks, latency, cost, monitoring, fallback behavior, and product ownership. The product and software delivery context is an editorial scenario, not a measured claim about Miami.
3. Staff / Principal ML Engineer: JAX
For a JAX system you supported, explain the handoff, operating limits, and measures used after launch. Where did your responsibility begin and end?
Use the answer to assess model evaluation, sensitive-data handling, explainability, and controls around automated decisions. The finance and insurance systems context is an editorial scenario, not a measured claim about Miami.
Need the full ML Engineer evaluation guide?
The role guide covers technical scope, interview questions, and evidence checks once, without repeating the same material on every city page.
FAQ
For qualified exclusive searches in our core disciplines, Crosscheck targets a first candidate slate within 48 hours after a completed intake. Contract placements include a 40-billable-hour replacement guarantee, and permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Local hiring brief
Write the brief around the model lifecycle. Include label creation, feature pipelines, experiment tracking, service integration, monitoring, and retraining duties that belong to this hire. Separate those duties from work owned by data, platform, or research teams. The three sourced Miami contexts below turn that scope into intake and screening decisions. They do not measure current vacancies, candidate supply, or Crosscheck client activity. Name the prediction task, training data, evaluation method, deployment path, latency, monitoring, retraining, and software ownership. Ask candidates to trace one model from experiment through production support.
Sources and methodology
Original Crosscheck visual
Each lane connects sourced regional context to a role-specific screening decision. The sources do not measure current candidate supply or Crosscheck client demand.
Review a feature or training pipeline and ask the candidate to trace one record from source through validation, training, and evaluation. Trace one shipment or trade transaction through partner interfaces, status events, exceptions, financial postings, reconciliation, retention, and support ownership.
Use a production scenario with throughput, latency, and reliability limits. Require an API or batch design plus a test plan. Identify the flight, cargo, maintenance, airport, or manufacturing boundary, then document uptime, access, audit, interface, and recovery requirements.
Ask for a model degradation example and the evidence used to separate data change, code change, and user-behavior change. Name the sector, record type, regulated boundary, system of record, control owner, change authority, and evidence required for acceptance.
Continue your research