FDE AI/ Solutions Architect (AI, Python/Data)

MD, US Mid Level AI/ML Engineer

Interested in this AI/ML Engineer role at Provectus?

Apply Now →

Skills & Technologies

AnthropicAwsAzureBedrockClaudeGcpKubernetesOpenaiPythonRag

About This Role

AI job market dashboard showing open roles by category

Provectus is an AWS Premier Partner and an Anthropic Strategic Partner, working at the frontier of applied AI. We help enterprises turn Claude, agentic systems, and their own data into measurable business outcomes — through bespoke applications, managed services, and advisory engagements. With offices in North America, LATAM, and EMEA, we partner with clients worldwide.

Our work centers on two verticals — Financial Services & Insurance and Healthcare & Life Sciences — where we deploy five pre-built AI Blueprints: Submission Flow, Portfolio Lens, Asset Flow, Revenue Flow, and Evidence Lens. Each Blueprint rebuilds a critical business process front to back, shipped from working code and tuned to a client's specific book, regulators, and operating posture.

Our team holds 100+ AWS certifications, is Claude Code certified, and co-delivers Anthropic's Agentic SDLC program, Cowork Activation, and AI Blueprint engagements.

Where this role sits

You will work in a small, senior pod alongside an FDX; our delivery arc is Sprint Enable Realize:

  • Forward Deployed Executive (FDX) owns the commercial relationship and the business outcome. Works alongside the client's leadership or C-suite level to move the client's KPIs — revenue growth, cost reduction, risk reduction.
  • Forward Deployed Engineer (FDE) embeds with a client to change how that client operates. You own the method; nobody hands you a ticket. You map the client workflow as it actually happens, identify the business problem underneath it, build a working AI solution, present to the client in the language of outcomes, and transfer it. Provectus maintains industry Blueprints — working systems that have already shipped for a client in the same industry — so you begin from running code and tuning it to this client's specific book, regulators, and operating posture. You will be measured on whether the Business Unit's number moved, not on hours or scope delivered.

What You’ll Do:

Take the seat

  • Sit with the client and the Forward Deployed Executive at the start of an engagement. Learn the function from inside, not from a requirements doc, and redesign the function from first principles.
  • Reach working fluency in a new domain — insurance underwriting, healthcare revenue cycle, asset flow.

Build

  • Design and ship production GenAI systems into the customer’s environment (cloud-native data, LLM-based, and agentic AI solutions). Implement and optimize RAG systems for production use cases
  • Build the evaluation harness before you build the feature. Define what working means, instrument it, and let the evals drive the design.
  • Write production code across the stack — AI, backend services, data pipelines. We choose tools to fit the customer.
  • Take systems to production on AWS (GCP or Azure where the customer requires it): containerised, CI/CD, automated testing, monitoring, and maintainable after we leave. Hand the system over to the client.
  • Start from the blueprint, and feed the blueprint. What you learn in the field becomes the baseline the next engagement starts from.
  • Lead architecture reviews, produce technical design documents, and contribute to standards. Mentor engineers and share knowledge across the team.

Own the outcome.

  • Work in a pair with a FDX who carries the Business Unit’s KPIs. Your work is measured against the same number.
  • Own the technical direction of technical proposals and scoping. Drive adoption. Change management is part of the engineering job here.
  • Be credible with the customer’s engineers and their executives.
  • Shape what we commit to before we commit to it.

What You’ll Bring:

Mindset

  • Proactive and self-directed; identify problems before they're handed to you
  • Comfort with ambiguity and ownership. Engagements start underspecified by design. Closing that gap is the job
  • B2+ English, comfortable collaborating across distributed, multicultural teams

Client Engagement

  • You are willing to spend time understanding and doing someone else’s job on the client's side before you write a line of code
  • Credible with senior stakeholders — you can hold a redesign conversation with a BU head and a scoping conversation with a CTO, presenting outcomes to them
  • You can produce a scoped, phased delivery plan with clear deliverables, dependencies, and risks — and estimate what it will cost to build and to run

Technical depth

  • 7+ years building and running production systems.
  • Solid AI/ML foundations. You understand what the models do well enough to reason about failure modes
  • Designed and shipped to production LLM applications and agentic workflows — not demos, not POCs, not notebooks
  • Agentic orchestration: multi-step workflows, graph-based orchestration, tool use, state management, and recovery from partial failure
  • Experience with LLM APIs (Anthropic, AWS Bedrock, or OpenAI) and agent frameworks.
  • Experience building and optimizing RAG systems in production
  • Strong engineering fundamentals — dropped into an unfamiliar codebase or language, you’re productive. Python and/or TypeScript proficiency; depth matters more than stack.
  • Experience in making and defending architectural trade-off decisions
  • Hands-on AWS production depth: Bedrock, Bedrock AgentCore, Lambda, ECS, S3, SQS, ECR, or similar. GCP or Azure is a plus
  • Cloud-native delivery: containers, ECS or Kubernetes, IaC, and CI/CD applied to AI pipelines
  • You evaluate. You have built or owned an eval suite for a non-deterministic system, and you can explain what you measured, how you produced ground truth, and what gated a release
  • Model and agent monitoring, drift detection
  • Cost and latency discipline: model tiering, caching, and the ability to say what a workload costs to run before it runs
  • Hands-on production experience with the Claude ecosystem — Claude Code, CLAUDE.md, hooks, skills files. Spec-driven development — writing the intent, constraints, and acceptance criteria before you let an agent build — is a strong plus
  • MCP: you can say why an agent would prefer it to a REST integration. Having authored a server is a plus

Nice to have:

  • Prior experience as a founder, CTO, or engineering leader who has chosen to return to individual contribution
  • Experience in one of the industries: financial services, insurance, healthcare
  • Consulting, professional services, or other embedded customer-facing delivery
  • A2A: you can explain agent-to-agent interoperability
  • AWS and Claude Code Certifications
  • CI/CD pipeline experience (GitHub Actions, GitLab CI)
  • Experience in an additional language (Go, TypeScript, or Rust)
  • Experience with Apache Spark, Apache Airflow, Kafkа

What We Offer:

  • The chance to shape how leading enterprises across LATAM, Europe, and North America adopt AI, from strategy through first deployment
  • A forward-deployed model working in small, senior teams alongside Principal Architects and Forward Deployed Engineers
  • A growing AI delivery practice where you help build the tooling and frameworks, not just use them
  • Remote-friendly culture
  • Internal training programs with full support for Claude, AWS, and other professional certifications, conference attendance
  • Career growth; we actively develop our engineers
  • Access to the latest AI tools and premium subscriptions
  • Long-term B2B collaboration
  • Private medical insurance or a budget for your medical needs
  • Paid sick leave, vacation, and public holidays
  • Equipment and all the tech you need for comfortable, productive work

How we hire:

  • Intro conversation. The role, your background and aspirations, tech questions.
  • Technical interview with live engineering sessions. Real problems, your own editor, you may use an LLM assistant
  • HR Interview. Soft skills and expectations
  • HM interview. Tech questions; a live engineering session is also possible

We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.

Role Details

Company Provectus
Title FDE AI/ Solutions Architect (AI, Python/Data)
Location MD, 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 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Provectus, 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

Anthropic (2% of roles) Aws (11% of roles) Azure (10% of roles) Bedrock (2% of roles) Claude (6% of roles) Gcp (7% of roles) Kubernetes (6% of roles) Openai (5% of roles) Python (23% of roles) Rag (9% 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 $213,800 based on 16,346 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200.

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.

Provectus AI Hiring

Provectus has 7 open AI roles right now. They're hiring across AI/ML Engineer. Positions span New York, NY, US, Manhattan, NY, MD, US. Compensation range: $170K - $250K.

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

Based on 16,346 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $213,800. 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 6% of the 10,419 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.
Provectus 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.