> Markdown version of [/jobs/ext/4717858-ai-ml-engineer](https://www.wearedevelopers.com/jobs/ext/4717858-ai-ml-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # AI/ML Engineer - **Company:** Dow - **Location:** New York, NY, United States - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Code Generation, Software Debugging, Python (Programming Language), Language Modeling, Open Source Technology, Software Engineering, Verification and Validation (Software), Working Model 2D, Reinforcement Learning, Pytorch, Prompt Engineering, Model Validation, Transformer Architectures, Web Api - **Published:** November 14, 2026 - **Apply:** https://startup.jobs/ai-ml-engineer-kaizen-labs-10766846 ## About the Role * Hands-on experience training, fine-tuning or adapting language models. You've worked with model weights, not just model APIs or prompts. * Strong software engineering fundamentals. You build reliable training pipelines, debug complex systems, and write code other engineers build on. * Strong Python and PyTorch, with a working understanding of transformer architectures, tokenization and language model training. * Something you've built that shows real model engineering ability: a fine-tuned model, an original training approach, or a meaningful open-source ML contribution. Industry, research or independent work all count; demonstrated ability matters more than years or credentials. ## Description Most companies building with AI connect someone else's models to their software. Kaizen's AI-native platform turns requirements into working applications, and today much of that intelligence comes from general-purpose models that carry capabilities we don't need, lack knowledge we do, and leave us and our customers paying frontier-model token costs for intelligence we don't control. This role changes that. You'll fine-tune, adapt and distill open-weight models into specialized intelligence Kaizen owns, and prove where it beats the general-purpose alternative. The goal isn't the biggest model or the most papers: it's public-sector software that works better, costs less to run, and is harder to replicate. What You'll Do * Fine-tune, adapt and distill open-weight models for requirements interpretation, code generation, repository understanding, structured output and software validation. * Own the experiment loop: curate datasets, build training pipelines, and test architectures and techniques until a promising idea becomes a working model. * Build evaluations on real software engineering tasks that set baselines, expose failure modes, and separate real gains from benchmark noise. * Work with platform engineers to find where current models fall short, then build the capabilities that close those gaps and ship them into production. * Experiment with supervised fine-tuning, synthetic data, preference optimization and reinforcement learning to improve model behavior on specialized tasks. * Deliver applications built around each customer's needs without frontier-model token spend, so public budgets go to residents, not inference. * Lay the groundwork (datasets, evals, research practices) for Kaizen to eventually train its own models from scratch., * Have fine-tuned models for code generation, program synthesis or repository understanding. * Design experiments and evaluation sets that tell a meaningful improvement from noise or overfitting. * Bring experience with synthetic data, distillation, quantization, or preference optimization and RL with verifiable rewards. * Have contributed to open-source model development, published applied ML research, or reproduced significant research results. Don't Apply If... * Your model experience is prompt engineering and API calls. * You'd rather publish a result than ship a model people use every day. * You hand off notebooks and expect someone else to make them run in production. * You assume the biggest model is the right answer and don't want to think about cost. Residents and public servants rely on the software we build because they don't have another option. The models underneath it have to earn that.