Director, Build Engineer
Pfizer
- Location
- United States New York New York City
- Work model
- On-Site
- Level
- Staff
- H-1B history
- 9 approvals (FY2023)
- Posted
- Sep 17, 2026
Skills
About this role
ROLE
SUMMARY This role owns hands-on software engineering delivery for the Medical Affairs AI Acceleration portfolio. This role turns solution architecture and product requirements into working, production-grade AI systems. This is a deeply technical, individual-contributor role. This position is accountable for designing components and writing, testing and shipping code to production. Decisions made in this role — how a feature is implemented, how AI-generated code is verified before it reaches production, how quickly a validated prototype is hardened into a scalable system — directly determine the reliability and velocity of the AI systems Medical Affairs depends on. This role carries individual technical authority over its assigned build area, reporting into the Senior Director, Engineering alongside two peer Build Engineers and the Data Integration Engineer. The role partners closely with Solution Architecture to implement architectural blueprints, with the Data Integration Engineer to incorporate data from various sources into the AI solutions, and with Product Management and UX/Experience Design to translate product and workflow requirements into working software solutions. Solutions will be deployed through the full life cycle including proofs of concepts, MVPs and production grade systems. The Director, Build Engineer is a hands-on software engineer who builds, tests, and ships the AI-powered products and platforms that make up the Medical Affairs AI Acceleration portfolio. Reporting to the Senior Director, Engineering, this role takes solution architecture and product requirements from prototype through production — writing full-stack code, integrating Agentic AI and LLM-based capabilities, and verifying AI-generated code with the same rigor applied to human-written code. This is an individual-contributor role built for engineers who move fluidly across the stack, work comfortably in ambiguity, and take personal ownership of whether what they ship actually works in production.
ROLE
RESPONSIBILITIES Full-Stack & AI System Build Build, test, and ship production-grade software across the stack, working in whatever language or framework the problem requires. Integrate Agentic AI, LLM-based capabilities, and RAG pipelines into Medical Affairs products, translating architectural design into deployed, functioning services. Take validated prototypes and MVPs through to production-grade systems, applying the quality gates and standards set by Solution Architecture and the Senior Director, Engineering. Write and maintain code that meets the team's engineering standards for quality, maintainability, and reuse. Document code, APIs, and system design decisions clearly and consistently as a standard part of the development process ensuring solutions are maintainable and understandable by others beyond the original author. AI-Augmented Development & Verification Use AI-augmented development tools to accelerate delivery, while applying rigorous verification and review to all AI-generated code before it ships. Apply LLM integration patterns (e.g., prompt design, multi-provider/model considerations, RAG) to build features that depend on generative AI capabilities. Monitor and troubleshoot AI/ML components in production, partnering with Solution Architecture on model performance, drift, and reliability issues. Design and optimize LLM and agent interactions for token efficiency — balancing prompt design, context window usage, and model selection to control cost and latency without sacrificing output quality. Data & Systems Integration Partner with the Data Integration Engineer to ensure builds are backed by reliable, well-governed data pipelines. Integrate with core enterprise systems (e.g., Veeva CRM, PromoMats, Salesforce Life Sciences/Marketing Cloud) as required by product and architecture specifications. Identify and resolve technical debt in owned build areas, balancing delivery speed against long-term system