Senior Forward Deployed Engineer, project44

• 5+ years in software engineering, solutions engineering, or technical implementation in a customer-facing role
• Mastery of API-first design and bi-directional webhook configuration
• Experience with event-driven architecture and stream processing (Kafka, PubSub, or similar)
• Hands-on integration experience with TMS, WMS, or ERP systems
• Strong debugging skills across distributed, agent-driven workflows
• Deep domain knowledge in logistics — freight procurement, load tendering, carrier management, and exception handling. LSP customers don't trust engineers who don't understand their world. You need to speak their language to earn the right to change how they work
• You take ownership of outcomes, not just deliverables
• You bring back what you see in the field and use it to make the product better
• You move fast, iterate in the open, and don't wait for perfect conditions
• You can translate technical complexity to both engineers and LSP operators without losing either audience
• Even if you don't meet 100% of the requirements, please consider applying — studies show you can still be a strong candidate at 50%

Desirable

• Most engineers build for customers. FDEs build with them. You'll be embedded directly with high-value LSP accounts — owning integration architecture, customizing agent workflows, and serving as the ground truth between how LSPs actually operate and how our product team thinks they do
• Your job is to transform logistics from a reactive service into a programmable network — replacing manual workflows with autonomous agent-to-agent coordination. What you learn in the field shapes the roadmap. You ship in weeks, not quarters
• Own end-to-end integration for dedicated LSP accounts — configure bi-directional webhooks and event-driven pipelines so AI agents can read, act, and write data into customer TMS, WMS, and ERP systems instantly
• Unify disparate customer data into a single actionable signal — driving dynamic interoperability across core business systems
• Customize interfaces and agent logic to fit existing LSP workflows across freight procurement, load tendering, and exception handling — reducing time-to-value and making adoption feel natural
• Feed the right context to agents and debug decisions when they go wrong — tracing failures back to the specific data point, prompt, or tool use that caused them
• Build event-driven pipelines (Kafka/PubSub) that carry agent intent at the scale of millions of logistics events per day
• Serve as the ground truth — we can't build a world-class product in a silo. Your field observations directly inform what gets on the roadmap and when