The ad says“Software engineering. You ship production systems and are comfortable dropped into an unfamiliar codebase or a customer environment with a deadline. Backend and systems depth, strong Python plus at least one systems language, and fluency with AI-assisted and agentic engineering as a core part of how you build”
The ad says“Software engineering. You ship production systems and are comfortable dropped into an unfamiliar codebase or a customer environment with a deadline. Backend and systems depth, strong Python plus at least one systems language, and fluency with AI-assisted and agentic engineering as a core part of how you build”
The ad says“Customer engagement. You want to be in the room. The point of this role is creating specialized intelligence for each customer: the best model for their task, their data, their constraints. That takes real interest in the customer’s problem, not just the technical one. Exceptional here looks like founder energy with customers; the floor is genuine appetite to embed, explain, and own outcomes with them”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“For the infrastructure spike: experience with GPU infrastructure, distributed serving, or inference engines”
The ad says“For the infrastructure spike: experience with GPU infrastructure, distributed serving, or inference engines”
The ad says“For the infrastructure spike: experience with GPU infrastructure, distributed serving, or inference engines”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Software engineering. You ship production systems and are comfortable dropped into an unfamiliar codebase or a customer environment with a deadline. Backend and systems depth, strong Python plus at least one systems language, and fluency with AI-assisted and agentic engineering as a core part of how you build”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer”
The ad says“Software engineering. You ship production systems and are comfortable dropped into an unfamiliar codebase or a customer environment with a deadline. Backend and systems depth, strong Python plus at least one systems language, and fluency with AI-assisted and agentic engineering as a core part of how you build”
As an Applied Machine Learning Engineer, you are the technical owner of a customer engagement
This is what is globally known as the Forward Deployed Engineer role; at Fireworks in EMEA it carries the AMLE title
You embed with a small number of accounts, work in their environment, and own whatever stands between them and production on Fireworks: the model, the serving path, the integration, the performance
You scope the work before signature and deliver what you scoped. Depth over breadth: few accounts, owned end to end
What we value most is first principles thinking: reasoning about unfamiliar problems from the ground up rather than from playbooks
You will be evaluated on this directly in the interview process, and strength here can outweigh gaps elsewhere in your background
Own Engagements: Take customer deployments from scoping through production, as the single accountable technical owner
Embed: Work directly inside customer teams; understand their domain, data, and constraints well enough to make decisions they trust
Train and Tune: Run fine-tuning and post-training work where the engagement needs it, from data to evaluation to a model serving in production
Optimize: Drive serving performance and cost on Fireworks: model choice, deployment shape, and inference optimization
Scope Honestly: Assess what is achievable before we commit, and inherit what you scope
Product Signal: Feed what customers need back to product and engineering, with enough precision to be actionable
Why Fireworks?
Solve Hard Problems: Tackle challenges at the forefront of AI infrastructure, from low-latency inference to scalable model serving
Build What’s Next: Work with bleeding-edge technology that impacts how businesses and developers harness AI globally
Ownership & Impact: Join a fast-growing, passionate team where your work directly shapes the future of AI—no bureaucracy, just results
Learn from the Best: Collaborate with world-class engineers and AI researchers who thrive on curiosity and innovation
Preferred experience
Spikes in two or all three areas
Experience in a startup or fast-paced environment
Machine learning. You take open models and make them better on a customer’s task: SFT, LoRA and other parameter-efficient methods, reinforcement learning (RLHF, RLVR), distillation. Just as important, you design evaluations that reflect the real task and let them drive training decisions, and you know when fine-tuning is not the answer
Customer engagement. You want to be in the room. The point of this role is creating specialized intelligence for each customer: the best model for their task, their data, their constraints. That takes real interest in the customer’s problem, not just the technical one. Exceptional here looks like founder energy with customers; the floor is genuine appetite to embed, explain, and own outcomes with them
For the ML spike: formal training (PhD, PhD in progress, or a strong MSc) and experience post-training LLMs specifically
Four Spikes:
Founder or founding engineer experience
Software engineering. You ship production systems and are comfortable dropped into an unfamiliar codebase or a customer environment with a deadline. Backend and systems depth, strong Python plus at least one systems language, and fluency with AI-assisted and agentic engineering as a core part of how you build
Infrastructure and performance. You know your GPUs: memory bandwidth, kernels, parallelism, what utilization numbers actually mean. Serving and inference optimization: quantization, speculative decoding, batching, KV cache behavior, latency vs throughput tradeoffs, multi-GPU and multi-node serving, capacity planning. You can take a deployment that works and make it fast and economical, and reason about where the bottleneck is before touching a profiler
For the infrastructure spike: experience with GPU infrastructure, distributed serving, or inference engines
