project44
project44

Senior Forward Deployed Engineer - LSP

Chicago, IL; San Francisco, CA, USHybridSeniorFull-time

Posted 4 days ago

The role in short

Embed with logistics service providers to build production integrations, customize AI agent workflows, and ship event-driven pipelines.

Why p44LSP.ai?

At project44, we believe in better — and p44LSP.ai is what better looks like for the logistics service provider market. 

For years, project44 focused on global shippers as our core customer. That focus worked. Our Shipper business is a category leader growing 20% year-over-year. That strength is what makes the next chapter possible. 

Shippers and LSPs are fundamentally different businesses. Shippers buy logistics software to support their core operations. Logistics Service Providers — freight forwarders, brokers, and 3PLs — sell logistics as their product. Their software is their competitive edge. They buy fast, build on APIs and agents, and reward teams that ship in weeks, not quarters. 

This is why we created p44LSP.ai: a dedicated, AI-native division built to serve the LSP market with the focus, speed, and resources it deserves. It's the scope and ownership of an AI startup, backed by the infrastructure of a $124M business — 259K carriers, billions of shipment outcomes, agents in production, and direct access to project44's data graph, carrier network, and enterprise relationships. 

This is a small, hand-picked team operating across Chicago, San Francisco, Bangalore, and the EU. Flat org. Forward-deployed engineering. AI coding tools across the workflow. Agents as the product surface. Customers who pilot in weeks and tell you what they think directly. 

The LSP market is moving fast. AI agent startups are growing 300%+ year-over-year, and seven of eight sell to LSPs. We have the data position, the platform, the customers, and now the team. We're hiring the engineers who will build it with us. 

AI at project44

We expect every project44 team member, regardless of role or function, to actively leverage AI in their day-to-day work. Whether you're building product, serving customers, managing people, or running operations, AI is a tool you're expected to use with intent, curiosity, and judgment. We don't expect everyone to be a data scientist. We do expect everyone to be an intelligent user of AI: able to identify where it adds value, direct it effectively, evaluate outputs critically, and govern it responsibly. We invest in our team's AI fluency because we believe it's a competitive advantage for every person at project44, not just our engineers

If you’re driven to solve meaningful problems, leverage AI to scale rapidly, drive impact daily, and be part of a high-performance team – we should talk. 

The Role 

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.

What You'll Work On 

  • 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

What We're Looking For 

Qualifications 

  • 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.

Nice to Have 

  • Experience with agentic AI systems — context feeding, prompt engineering, tool invocation, stateful agents
  • Prior experience in a forward-deployed or field engineering role
  • Containerization and orchestration (Docker, Kubernetes)

How You 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

Work Authorization: Candidates must be authorised to work in the US without current or future employer-sponsored visa support.

**In-office Commitment:**Our office is where ideas spark, connections thrive, and innovation comes alive. We are looking for candidates who are enthusiastic and committed to joining our team on-site, in our beautiful headquarters 3 days a week. Together, we’re building something extraordinary—learn, grow, and thrive in our fast-paced, transformative environment.

Diversity & Inclusion 

At project44, we're designing the future of how the world moves. As we work to deliver a truly world-class product, we're intentionally building teams that reflect the unique communities we serve. We're focused on creating a company where all team members can bring their authentic selves to work every day. 

project44 is an equal opportunity employer. If you share our values and passion for the future of logistics, we'd love to review your application. Even if you don't meet 100% of the requirements, please consider applying — studies show you can still be a strong candidate at 50%. 

For any accommodation needed during the hiring process, please email recruiting@project44.com.

Prep for this interview

4 questions likely to come up at project44, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “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”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  2. 2LLMs, RAG and agents
    They wrote: “Experience with agentic AI systems — context feeding, prompt engineering, tool invocation, stateful agents”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

  3. 3Cloud, deployment and security
    They wrote: “Containerization and orchestration (Docker, Kubernetes)”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  4. 4Ownership and working with customers
    They wrote: “You take ownership of outcomes, not just deliverables”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

project44

Hybrid

Apply