Why Does AI Suddenly Need Forward-Deployed Engineers?
summary
Claims that AI makes forward-deployed engineering affordable at scale by letting AI collapse execution cost while the cost of human judgment stays high, with vendors like AWS and OpenAI embedding engineers at customer seams. Presents a competency model that combines technical craft, discovery/scoping and the human owns the outcome responsibilities, plus a six-step playbook: follow a problem end-to-end, borrow other disciplines’ lenses, build one deep anchor skill, use AI as a pair not an oracle, practice client conversations and lead without the title.
AI-written summary · about
chapters (30)
- 0:00Why Does AI Suddenly Need Forward-Deployed Engineers?
- 1:07Speaker Intro - Harinee Muralinath, Business Information Security Officer at Thoughtworks
- 3:10What an FDE Is - and Why It Deserves Better Than the Hype
- 4:14No Client Ever Woke Up Wanting a Forward-Deployed Engineer
- 4:44They Wake Up With a Need and Limited Resources
- 5:46What an FDE Actually Is, Per the Job Descriptions
- 6:48Two Extensions: Owning the Outcome and the Loop Running Both Ways
- 8:22This Role Has Always Existed Under Other Names
- 9:23AI Didn't Invent the Need - It Made the Person Affordable at Scale
- 10:26Strip Away the Title: Need, Constraints, Illities, Outcome
- 10:56Why the Configuration Is Possible: Dissolving the Role Badges
- 12:28Execution Cost Collapsed; the Cost of Judgement Did Not
- 14:00Skill One: Collecting Other Disciplines' Lenses Like a Prism
- 16:05Skill Two: Grow the Questions - Breadth Got Cheap, Depth Did Not
- 16:36The Security Example: Below the Waterline Questions
- 18:08AI Gives Breadth Inside the Boundary of Questions You Know to Ask
- 18:38A Competency Model That Covers the Whole Job, Not Just the Craft
- 19:08Why Forward-Deployed Engagements Actually Fail in the Field
- 20:10Discovery, Scoping, Pace With Predictability
- 20:41The Connection Factor: Listening, Narrative, Influence Without Authority
- 21:11Grading Yourself Honestly: Awareness, Working Capability, Depth
- 21:42The Playbook: Follow One Problem Past Your Boundary
- 22:43Borrow Another Discipline's Lens for a Month
- 23:13Build One Area of Real Depth as an Anchor
- 23:43Practise Client Conversations and Lead Without the Title
- 24:44For Leaders: The Environment Creates Judgement, Not the Academy
- 25:45If the Engineer Speeds Up and the System Doesn't, It Lands on the Client
- 27:18Two Easy Conclusions to Avoid - and the Opportunity Between Them
- 28:18The Question to Take Back: What Thinking Must Still Happen?
- 28:49Copy the Conditions, Not the Title
related talks
20mHow to Strategize Talent Hiring and Upskilling in the Age of AI
18mStructuring a modern AI team
13mAI as a Strategic Asset: Building Competitive Advantage
50mAgile Intelligence: Co-Engineering the Future, Not Just Automating It
33mEngineering AI Applications: A Conversation with AI Leaders
33mHow AI is Re-shaping Engineering Work (And How to Deal With It)
28mAI for Everything After Code
24mThe Impact of AI on the future of software engineering