Architect - Machine Learning and Data

US Mid Level AI/ML Engineer

Interested in this AI/ML Engineer role at Coretek Services?

Apply Now →

Skills & Technologies

AutogenAzureDrift AiMlflowOpenaiPgvectorPower BiPythonSemantic Kernel

About This Role

AI job market dashboard showing open roles by category

Coretek is seeking an Architect, Machine Learning and Data to lead the design of production machine learning and generative AI platforms on Microsoft Azure and Microsoft Fabric. This role sits at the point where data platform architecture, MLOps, and applied AI meet. You will define how client organizations move models out of notebooks and into governed, monitored, reproducible production operation, and how generative AI capabilities are architected to be secure, evaluable, and cost\-controlled at enterprise scale.

You will own the technical architecture on client engagements end to end: target\-state design, environment and identity models, pipeline and promotion patterns, observability standards, and the operational handoff that lets a client run the platform without you.

You will work alongside data scientists, data engineers, and delivery leadership, translating requirements into architecture decisions and then staying close enough to implementation to be accountable for the result.

This is a delivery architecture role. Depth of production experience matters more than breadth of exposure, and the expectation is that you have personally been responsible for systems that ran unattended and were handed to someone else to operate.

Key Responsibilities:Solution Architecture and Technical Strategy* Own end\-to\-end technical architecture for machine learning and AI engagements, from target\-state design through production acceptance.

  • Define reference architectures for Fabric\-first data science and MLOps platforms, including environment topology, storage boundaries, and promotion paths.
  • Produce architecture decision records, requirements traceability, and design documentation that hold up under client security and compliance review.
  • Make and defend platform tradeoff decisions: Fabric versus Azure\-native services, managed versus custom components, build versus configure.
  • Define compute sizing assumptions, cost guardrails, and capacity planning for batch and inference workloads.
  • Establish third\-party and open\-source governance patterns, including dependency disclosure, licensing implications, and controls that keep unapproved packages out of production.

ML Platform, MLOps, and Operationalization* Architect Sandbox, Dev/Staging, and Production environment models with enforced isolation and role\-based access aligned to Entra ID group structures.

  • Design governed read access to enterprise data warehouse sources alongside controlled data science owned write\-back boundaries for features, model metadata, artifact references, predictions, and experiment results.
  • Define reusable batch prediction and forecasting pipeline architectures spanning ingestion, feature preparation, quality validation, model execution, output persistence, and alerting.
  • Architect forecasting\-specific patterns where they diverge from batch scoring, including time\-series inputs, rolling forecasts, and horizon\-based outputs.
  • Design CI/CD and promotion architecture for notebooks and platform assets: Git integration, branching standards, automated testing, deployment pipelines, approval gates, and rollback paths.
  • Define orchestration and scheduling patterns covering time\-based, trigger\-based, and manual execution with dependency\-level failure visibility.
  • Architect data quality gates that block downstream model execution on failure, covering schema validation, null and range thresholds, and distributional anomaly detection.
  • Mandate and design headless execution: all scheduled and production workloads run under managed identities or service principals with secrets in Azure Key Vault, never under individual user credentials.
  • Establish model, code, environment, and package versioning standards so any production run is traceable to a versioned combination of code, configuration, environment, and data reference.
  • Design observability and drift monitoring architecture, including baseline statistics, health checks, alert thresholds, routing, and escalation paths.
  • Provide backup, recovery, and retention architecture input for data science owned tables, model artifacts, and experiment metadata.
  • Define foundational experimentation platform patterns for experiment configuration, metrics, treatment assignment, matched datasets, and results.

Generative AI and LLMOps Architecture* Architect production generative AI solutions on Azure OpenAI, including retrieval\-augmented generation, summarization, classification, extraction, and conversational patterns.

  • Design retrieval architectures and select vector stores appropriate to scale and query profile, spanning Azure Database for PostgreSQL with pgvector, Azure AI Search for hybrid keyword and vector retrieval, and scale\-out alternatives.
  • Define chunking, embedding, indexing, and reranking strategies, and the evaluation approach that proves retrieval quality rather than assuming it.
  • Architect agent and multi\-agent solutions using frameworks such as Pydantic AI, Semantic Kernel, AutoGen, or the Microsoft Agent Framework, with clear tool boundaries and failure handling.
  • Establish LLMOps practice: prompt and version management, automated evaluation harnesses, groundedness and hallucination testing, regression suites, and release gating.
  • Design guardrails, content safety, and responsible AI controls, including PII handling, grounding constraints, and human\-in\-the\-loop checkpoints where warranted.
  • Define inference and orchestration patterns across API, serverless, and container\-based deployment, with attention to latency, throughput, and failure modes.
  • Architect token, cost, and model\-selection strategies, including routing between model tiers and caching where it materially changes unit economics.
  • Design observability for generative systems: tracing, evaluation telemetry, drift in output quality, and cost attribution.

Azure and Microsoft Fabric Platform* Design solutions across Microsoft Fabric, including Lakehouse, Warehouse, Notebooks, Data Pipelines, deployment pipelines, and semantic models.

  • Architect integrations across Azure Machine Learning, Azure OpenAI, Azure AI Search, Azure Databricks, Azure Data Factory, Cosmos DB, and Azure Storage.
  • Define identity, networking, and security architecture including Entra ID, managed identities, service principals, Key Vault, RBAC, and private connectivity where required.
  • Ensure downstream consumption patterns are validated, including Power BI access to model output and semantic layer design.
  • Design for performance, reliability, security, compliance, and observability as first\-class architectural concerns rather than post\-deployment additions.

Client Engagement and Advisory* Serve as the senior technical voice on engagements, leading design sessions and workshops with client architects, data science teams, and IT leadership.

  • Communicate architecture, tradeoffs, risk, and cost to both engineering audiences and executive stakeholders, and drive consensus across them.
  • Advise clients on AI and data platform roadmaps, platform selection, and sequencing of capability investment.
  • Assess data readiness, AI maturity, and organizational constraints, and set realistic expectations about what production operation requires.
  • Lead knowledge transfer and operational handoff so client teams can run, monitor, and troubleshoot what was delivered.

Technical Leadership and Collaboration* Provide technical direction to consultants and engineers on engagement teams, including design review and code review.

  • Mentor team members on Azure, Fabric, MLOps, and generative AI practice, raising the technical floor of the teams you work with.
  • Author solution designs, runbooks, and reusable accelerators that outlive a single engagement.
  • Contribute to internal reference architectures and delivery standards.
  • Foster a collaborative, problem\-solving culture across delivery teams.

Requirements

  • 5\+ years of professional experience in data, machine learning, or AI engineering, including 3\+ years in a solution architecture or lead technical design capacity.
  • Demonstrated ownership of production machine learning systems, meaning systems that executed on a schedule, were monitored, and were operated by someone other than the author.
  • Hands\-on architecture experience with Microsoft Azure data and AI services, including Microsoft Fabric and lakehouse architectures.
  • Production generative AI experience, including large language model solutions, retrieval\-augmented generation, and prompt\-based workflows deployed beyond proof of concept.
  • Strong Python and SQL, sufficient to review and correct the work of senior engineers.
  • Deep MLOps expertise: model lifecycle management, versioning, reproducibility, evaluation, monitoring, drift detection, and retraining strategy.
  • CI/CD and automation experience with Azure DevOps or GitHub Actions applied to data, notebook, and model assets.
  • Working command of Azure identity and security: Entra ID, managed identities, service principals, Key Vault, and RBAC, including designing workloads that run without user\-bound authentication.
  • Experience architecting orchestration, scheduling, and data quality validation for production pipelines.
  • Excellent written and verbal communication, with the ability to present architecture to executive stakeholders and defend it under technical challenge.
  • Ability to manage technical scope, priorities, and expectations across concurrent engagements.
  • Bachelor's degree in Computer Science, Data Science, Statistics, Engineering, or a related quantitative discipline. Master's degree preferred.

Preferred Qualifications* Experience with time\-series forecasting at production scale, including rolling origin evaluation and horizon\-based output design.

  • Experimentation platform design: treatment assignment, matched datasets, causal inference methods, and result storage.
  • Familiarity with MLflow, experiment tracking, and prompt and version management tooling.
  • Working knowledge of R in a platform context, including renv and executing client\-provided R workloads on a schedule.
  • Experience with data quality frameworks such as Great Expectations or Soda.
  • Infrastructure as Code with Bicep or Terraform.
  • Spark\-based processing in Databricks or Fabric.
  • Power BI and semantic modeling depth.
  • Azure certifications such as Azure Solutions Architect Expert (AZ\-305\), Fabric Data Engineer Associate (DP\-700\), Fabric Analytics Engineer Associate (DP\-600\), Azure Data Scientist Associate (DP\-100\), Azure AI Engineer Associate (AI\-102\), or Azure Data Engineer Associate (DP\-203\).
  • Consulting or professional services background, delivering to fixed scope and milestone acceptance.
  • Experience in regulated or security\-reviewed environments where architecture is subject to formal review.

Why Join Coretek?* Microsoft Azure Expert Partner delivering advanced AI, Generative AI, Data, and Fabric solutions.

  • Ownership of architecture on high\-impact, real\-world engagements across multiple industries.
  • Strong emphasis on learning, innovation, and technical leadership.
  • Collaborative, remote\-first consulting culture with experienced architects and practitioners.
  • Direct exposure to the full AI lifecycle, from strategy and design through production and optimization.

Role Details

Title Architect - Machine Learning and Data
Location US
Category AI/ML Engineer
Experience Mid Level
Salary Not disclosed
Remote No

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 4,317 AI roles we're tracking, AI/ML Engineer positions make up 70% of the market. At Coretek Services, 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 Required

Autogen (3% of roles) Azure (22% of roles) Drift Ai (2% of roles) Mlflow (4% of roles) Openai (10% of roles) Pgvector (1% of roles) Power Bi (5% of roles) Python (52% of roles) Semantic Kernel (2% of roles)

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 $214,900 based on 6,420 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $194,400.

Across all AI roles, the market median is $215,000. Top-quartile compensation starts at $266,300. The 90th percentile reaches $320,790. For comparison, the highest-paying categories include AI Safety ($287,500) and Research Engineer ($272,100). By seniority level: Entry: $110,000; Mid: $194,400; Senior: $227,400; Director: $274,554; VP: $241,000.

Coretek Services AI Hiring

Coretek Services has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in US.

Location Context

AI roles in Austin pay a median of $214,343 across 143 tracked positions.

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 4,317 open positions tracked in our dataset. By seniority: 138 entry-level, 2,071 mid-level, 1,655 senior, and 453 leadership roles (Director, VP, C-Level). Remote roles make up 15% of the market (635 positions). The remaining 3,657 roles require on-site or hybrid attendance.

The market median for AI roles is $215,000. Top-quartile compensation starts at $266,300. The 90th percentile reaches $320,790. Highest-paying categories: AI Safety ($287,500 median, 34 roles); Research Engineer ($272,100 median, 227 roles); AI Engineering Manager ($244,000 median, 23 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 4,317 open positions across 15 role categories. The largest categories by volume: AI/ML Engineer (3,004), Data Scientist (345), AI Software Engineer (309). 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 (138) are outnumbered by mid-level (2,071) and senior (1,655) 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 453 positions, representing the bottleneck between technical execution and organizational strategy.

Remote work availability sits at 15% of all AI roles (635 positions), with 3,657 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 $215,000. Top-quartile roles start at $266,300, and the 90th percentile reaches $320,790. 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 $287,500 median, while Prompt Engineer roles sit at $145,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,249 postings), Aws (1,224 postings), Azure (938 postings), Rag (915 postings), Gcp (660 postings), Pytorch (640 postings), Prompt Engineering (624 postings), Kubernetes (559 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

Based on 6,420 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $214,900. Actual compensation varies by seniority, location, and company stage.
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.
About 15% of the 4,317 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
Coretek Services is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from AI/ML Engineer positions include ML Architect, AI Engineering Manager, Principal ML Engineer. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.