Didero
Didero3 open roles

Forward Deployed Engineer (New Grad)

CA$90–130kTorontoHybridEntryFull-time

Posted 24 days ago

The role in short

Build backend services, APIs, and ERP integrations for customers to automate supply chain workflows.

At Didero, we’re building the autonomous supply chain, starting with agentic supplier management.

Global trade has never been more complex or more critical. Teams are underwater, reacting to a flood of challenges — from geopolitical risk to tariffs. Didero helps by automating time-intensive workflows with AI agents, deploying cutting-edge technology into one of the world’s most vital domains.

We’re backed by some of the world’s best venture funds and leading figures across AI, supply chain, and enterprise software.

About the Role

We are looking for a new-graduate Forward Deployed Engineer to join our team in Toronto. This role is for a technically strong, curious engineer who wants to work directly with customers, learn complex operations quickly, and build the systems that deploy Didero in the real world.

You will partner with customers to understand procurement and operations workflows including ERP integrations, data pipelines, workflow automation, supplier communication, reporting, and custom deployment needs. You will help translate messy real-world processes into reliable technical systems, with mentorship from experienced Forward Deployed and Product Engineering teammates.

This is a hands-on engineering role. You will build backend services, integrations, APIs, data pipelines, and workflow automations. Our core platform uses Django and Python; we care more about strong fundamentals and solving customer problems than prior years of experience with any single stack.

Please Note: This is a hybrid role based in Toronto and may involve occasional on-site work with customers, approximately 1-2 times per month, for discovery sessions, technical workshops, and deployment phases.

What You'll Do

  • Work with customers and internal teammates to understand procurement, finance, ERP, and operational workflows.
  • Clarify requirements and identify the underlying business need before building.
  • Build and maintain integrations with ERP, procurement, finance, and operational systems.
  • Build backend services, APIs, data pipelines, workflow automations, and customer-specific solutions with guidance from senior engineers.
  • Translate ambiguous processes into structured designs.
  • Partner with Product and Engineering to spot patterns that should become part of the core platform.
  • Debug integration issues across customer systems, third-party APIs, and internal services.
  • Support discovery, deployment planning, and technical implementation.

You'll Be Successful in This Role If You

  • Are graduating soon (or recently graduated) and want a customer-facing engineering role.
  • Thrive in ambiguity and make steady progress with mentorship.
  • Think in systems and enjoy connecting workflows, data, and software.
  • Communicate clearly with technical and non-technical people.
  • Learn quickly, ask good questions, and take ownership of what you ship.

Qualifications

  • Graduating soon from a Computer Science, Software Engineering, or related program (or equivalent demonstrated skill), ideally Spring/Summer 2026 or within the last 12 months.
  • Strong coding fundamentals through coursework, co-ops/internships, research, open source, or substantial personal projects.
  • Experience or strong interest in backend development (Python preferred; other languages welcome if fundamentals are solid).
  • Comfort working with APIs, data, and debugging; prior internship/co-op experience is a plus.
  • Clear written and verbal communication; interest in working directly with customers.
  • Based in or willing to work hybrid in Toronto.

Bonus Points For:

  • Co-op or internship experience building backend services, integrations, or data pipelines.
  • Familiarity with Python/Django, React/TypeScript, SQL, or cloud basics (AWS/Azure/GCP).
  • Experience with customer-facing technical work, teaching, tutoring, or consulting-style projects.
  • Interest in supply chain, procurement, fintech, or enterprise software.

Tech Stack

Django · Python · React · TypeScript

What we value at Didero

  • We go beyond OTIF. We’re obsessed with our customers and go above and beyond to ensure we’re their top supplier. We work hard to earn and maintain their trust.
  • Own it. We own what we do. We stand behind the quality of our work and do the right thing, especially when it costs us.
  • Move fast. Learn faster. We have a strong bias to action and shorten the cycle by following our curiosity to improve as we go.
  • Be relentless. When one route closes, we find another.
  • Disagree, then commit. This is an open contest of ideas. We’re direct, but with respect. We’re decisive, and everyone commits because we win together.

What We Offer:

  • Competitive compensation and equity
  • Medical, dental, and vision insurance
  • Memberships for One Medical, Talkspace, Teladoc, and Kindbody
  • Unlimited PTO — we trust you to take the time you need
  • Monthly wellness stipend via ClassPass
  • Tech equipment for your setup
  • Catered lunches (for those in the office)

Prep for this interview

5 questions likely to come up at Didero, each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Familiarity with Python/Django, React/TypeScript, SQL, or cloud basics (AWS/Azure/GCP).”

    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.

  2. 2Integrations and APIs
    They wrote: “Debug integration issues across customer systems, third-party APIs, and internal services.”

    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.

  3. 3Discovery and scoping
    They wrote: “Please Note: This is a hybrid role based in Toronto and may involve occasional on-site work with customers, approximately 1-2 times per month, for discovery sessions, technical workshops, and deployment phases.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4Data and SQL
    They wrote: “Build backend services, APIs, data pipelines, workflow automations, and customer-specific solutions with guidance from senior engineers.”

    How would you design a daily pipeline that feeds customer data into our product?

    How to answer

    Why they ask: Tests basic data engineering: scheduling, failures, re-runs and monitoring.

    1. Extract with timestamps or change tracking, not full dumps, when possible
    2. Transform in steps you can re-run without creating duplicates
    3. Validate row counts and key fields before loading
    4. Alert a person on failure, with enough detail to fix it

    Tip: Make re-running safe (same input, same result) and say how you'd know it failed.

  5. 5LLMs, RAG and agents
    They wrote: “At Didero, we’re building the autonomous supply chain, starting with agentic supplier management.”

    A customer wants a chatbot over their internal documents. How do you build it?

    How to answer

    Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. Build a test set of real questions with expected answers before launch

    Tip: Spend more time on the data and on testing than on the model.

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.

More at Didero

Similar roles at other companies

Didero

CA$90–130k · Hybrid

Apply