Forward Deployed - Software Engineer (m/f/n)

Currently, this opportunity is for a project delivered for a US-based enterprise environment. The role is within a small Forward Deployed Engineer (FDE) pod consisting of two engineers, where the engineer writes most of the code themselves and coaches the other engineer.

• Bachelor's Degree
• Minimum 4 years of experience
• English language proficiency at C1 level

Nice to have:

• Master's Degree preferred
• Fluency with agentic development frameworks and AI coding assistants
• Experience building with LLMs and MCP server architectures to integrate client data and AI applications
• Ability to handle ambiguous and shifting requirements, reframing problems as needed
• Experience coaching less experienced engineers while maintaining hands-on coding
• Experience working directly with non-technical stakeholders to demo, align, and translate between technical and business concerns
• Quick learning of new domains to deliver client needs
• Good judgment on architecture decisions, build-vs-buy, and prioritization under time pressure
• Understanding of responsible AI practices and sound data handling in client environments

• Embed with client teams to extract requirements from incomplete or shifting specifications and define a technical direction
• Perform the majority of hands-on software development across full stack, including front end, back end, APIs, and integrations
• Use agentic development frameworks and AI coding assistants such as Claude Code, Cursor, and Copilot to prototype and deliver quickly
• Set up and integrate MCP servers and LLM-powered features that connect client data and tools to AI workflows
• Demo solutions frequently, incorporate stakeholder feedback, and iterate rapidly
• Coach the secondary engineer on the pod, providing teaching and code review
• Decide architecture and build-vs-buy technology choices for each problem
• Promote reusable patterns to the core platform when applicable
• Maintain quality appropriate for proving value with polish where necessary
• Plan for handoff or retirement of engagement-built software from the start