Lead Forward Deployed Engineer

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings only. We need to decide which sections to include. We have content for: - About the role: could be the "A day in the life" paragraph plus maybe overview of role. We'll put that. - Responsibilities: the "Key Responsibilities Include" list. - Requirements: could combine Required and Preferred? Usually Requirements is required qualifications. Qualifications could be preferred? But we have both Required and Preferred. We could make Requirements for required, Qualifications for preferred, or Skills for technical skills. Let's see: The posting includes "Required" list (experience, skills). Also "Preferred Experience". Also there is "Building blocks for success" heading with Required and Preferred. We could treat Required as Requirements, Preferred as Qualifications, and maybe Skills separate? But we have many skill items in Required (Python, APIs, etc). Could put those under Skills. However we need to avoid duplication. Let's think: We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping: - About the role: overview paragraph (A day in the life). - Responsibilities: Key Responsibilities Include list. - Requirements: Required experience (8+ years hands-on software engineering, etc). Could be a list. - Qualifications: Preferred Experience list. - Skills: maybe the hands-on programming and architecture capability across Python, APIs, data platforms, cloud, modern application technologies; practical experience building LLM applications, etc. But those are already in Required. Could still list them under Skills. But we must not repeat content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all info, but we can organize into sections; duplication is okay if it's present in multiple places? Might be okay but better to avoid duplication unless it's naturally separate. However we can split the Required list into two: core experience requirements (years, leading deployments, partnering with business) under Requirements; and technical skills (programming, architecture, LLM, etc) under Skills. Preferred list under Qualifications. Let's extract details. From posting: "A day in the life The Lead FDE partners with business teams to reimagine how work gets done with AI and leads the technical delivery of Prologis’ most complex business-embedded AI deployments while remaining hands-on in architecture, code, evaluation, and production implementation. As the first FDE hire, this role will help establish the FDE capability at Prologis and shape how AI is translated into new ways of working and measurable business results. The Lead FDE will be assigned to a primary Prologis business domain, generally for 9 to 12 months and potentially longer, to build deep operating context while leading several discrete deployments without creating permanent embedded support. This senior individual-contributor role sets technical direction, guides Senior FDEs and partner engineers, resolves cross-functional blockers, and remains accountable through business acceptance, production stabilization, and ownership transfer." That's the overview. Key Responsibilities Include (list): - Lead a portfolio of AI deployments within an anchor business domain, spanning multiple workflows, business units, or enterprise systems, with defined outcomes, sponsorship, architecture, milestones, production ownership, and handoff plans. - Partner with business leaders, frontline users, and AI Product to identify high-value opportunities, understand current workflows, redesign processes using AI, software, and human judgment, and define value cases, success measures, operating constraints, and acceptance criteria. - Architect, build, test, troubleshoot, and support production-grade AI applications, agents, retrieval systems, integrations, and workflow solutions through release and stabilization. - Set technical direction across FDE deployments, guide Senior FDEs, central AI engineers, and partner teams, and resolve tradeoffs among business value, engineering quality, security, speed, maintainability, and cost. - Design representative test sets, acceptance thresholds, regression testing, observability, security, privacy, auditability, and human controls, and facilitate business validation against agreed acceptance criteria. - Coordinate with AI Product, Applied AI Engineering, Platform, Data and Knowledge, Security and Governance, Process and Agent Orchestration, Enablement, Architecture, and AI Operations to resolve dependencies, support adoption, and establish durable production ownership. - Identify reusable components, evaluation assets, reference architectures, standards, and delivery playbooks; mentor Senior FDEs and partner engineers; and provide concise executive reporting on value, progress, risks, tradeoffs, and decisions. Required (Building blocks for success Required): - Eight or more years of hands-on software engineering, AI engineering, technical delivery, enterprise-solution experience, or equivalent practical experience. - Demonstrated success leading multiple complex software or AI deployments from discovery through business acceptance, production release, stabilization, and ownership transfer. - Proven experience partnering with business leaders and frontline teams to redesign an end-to-end business process using AI while personally contributing to engineering delivery and demonstrating sustained production use and measurable business improvement. - Hands-on programming and architecture capability across Python, APIs, data platforms, cloud, and modern application technologies. - Practical experience building and operating LLM applications, agentic systems, retrieval solutions, tool integrations, evaluations, guardrails, and production observability. - Experience applying enterprise architecture, data integration, identity, security, data protection, and software operating-model requirements to production solutions. - Demonstrated ability to lead technical delivery without formal organizational authority and translate senior business objectives into executable technical work. - Product judgment to distinguish reusable patterns from one-off customization and make disciplined build, buy, or stop decisions. - Demonstrated ability to create reusable engineering components, evaluation assets, standards, and playbooks. - Written and verbal communication skills for executive communication and technical design documentation. - Ability to acquire deep domain context quickly and use it to make enterprise delivery tradeoffs. Preferred Experience: - Extending successful AI workflow transformations across business units or geographies within a large global enterprise. - Deep knowledge of one or more Prologis business domains or adjacent industries. - Experience leading several parallel deployments or a portfolio of related AI use cases. - Experience building shared AI components, governed retrieval, knowledge architectures, reference architectures, or enterprise developer tooling. - Experience with AWS, Dataiku, SQL, automated testing, containers, CI/CD, and cloud or hybrid enterprise deployment patterns. - Demonstrates willingness and capability to leverage emerging technology, automation, and AI tools to improve efficiency, quality, and speed. - Exercises sound judgment, creative thinking, and accountability for outcomes. Hiring Salary Range: Of $200,000 - $285,000. Salary and whole compensation package (bonus target) to be determined by the candidate’s location, education, experience, knowledge, skills, and abilities, as well as internal equity and alignment with market data. People First (benefits): paragraph about total rewards, healthcare, dental, vision insurance, 401(k) match 50% up to 12% of eligible compensation, generous PTO with starting accrual of 22 days a year plus paid holidays and volunteer time, etc. Also mention All full-time roles in the US come with a robust benefits package which includes healthcare, dental, and vision insurance for employees and eligible dependents. Prologis also offers several other wellness, financial, and work/lifestyle-specific benefits. Our 401(k) retirement plan has a company match of 50% up to 12% of eligible compensation. We also offer generous PTO with a starting accrual of 22 days a year in addition to paid holidays and volunteer time. Also mention: All job offers contingent upon background verification. EEO etc. We should remove boilerplate like EEO, equal-opportunity, scam-warning, etc. Also remove navigation/cookie/legal. So we keep benefits description but remove EEO lines. Location: Denver, Colorado plus additional locations list. This is not in allowed headings; we could include under About the role maybe as a sentence. Or we could add a separate section not in list? The instruction says use those headings for section headings; it doesn't forbid other headings but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings if we need sections. It doesn't say we cannot add other headings, but to be safe we can incorporate location into About the role paragraph. Schedule: Not mentioned. No schedule info (like full-time, maybe schedule is full-time). The posting mentions Employment Type Full time. That's schedule? Could be considered schedule. But we should only include Schedule section if posting actually states them. It does state Employment Type Full time. That's schedule info. So we can include a Schedule section with "Full time". However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Employment Type Full time, so we can include Schedule. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

About the role

... (including location maybe)

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

... (benefits description)

Pay

... salary range and note about bonus target etc.

Schedule

Full time