
Forward Deployed Engineer
Posted 2 days ago
The role in short
Embed with Exodigo's civil, BIM and mapping teams to build production AI agents, Civil 3D/Revit integrations and automations for their design workflows.
Exodigo is the leading underground mapping solution for non-intrusive discovery. Our platforms combine multi-sensor fusion, 3D imaging, and AI technologies to create complete, accurate underground maps that enable confident decision-making for customers across the built world. We transform the project lifecycle for our customers, who include key community stakeholders in the utilities, transportation and government sectors.
We are experiencing sky-rocketing growth and closed a historically large $96M Series B round in July of 2025.
Job description
Exodigo engineers the underground without digging. Our platform combines multi-sensor fusion and AI to produce complete, accurate 3D maps of buried utilities, foundations, and geotechnical conditions, which utilities, transportation agencies, and engineering firms use to plan, design, and build with confidence. Behind every map is a team of civil engineers, BIM modelers, and mapping specialists who turn raw subsurface data into engineering-grade deliverables.
We are looking for an AI BIM Engineer to help that team move faster, stay consistent, and scale with our growth. You will work alongside our Mapping, Delivery, and Engineering Services teams, learn how a project moves from field scan through interpretation to Civil 3D and OpenRoads models and client-ready utility maps, and find where AI can take on the repetitive work so our engineers can focus on engineering judgment.
This is a hands-on, builder role. You will scope the problem, build the solution, ship it into live projects, and stay with it until it becomes part of how the team works. You will be the bridge between engineers who know the underground deeply and the AI agents that can amplify them: you can discuss utility quality levels, model QA/QC, and client CAD standards in the morning, and write a new integration for an AI agent in the afternoon. What you learn on our projects will shape the AI capabilities we give every team.
What You'll Do
Embed with engineering teams
- Work side by side with highway, structures, water, and site development teams to understand their design processes, tools, standards, and pain points.
- Lead discovery sessions with engineers and project leads, and translate what you hear into clearly scoped, prioritized opportunities for AI and automation.
- Own delivery end to end: from first conversation and rapid prototype through to a stable tool in daily production use.
- Coach engineers on using AI effectively and safely in their work, through hands-on sessions, office hours, and one-on-one support.
Turn expertise into repeatable workflows
- Partner with senior engineers to capture their know-how (checking procedures, design criteria, QA/QC steps, naming and modeling standards) as reusable AI workflows, prompts, and playbooks.
- Design workflows that are repeatable and reviewable: clear inputs, clear outputs, and an engineer in the loop wherever professional judgment or sign-off is required.
- Build evaluation sets from real project data so we can measure whether a workflow is accurate and reliable before it scales.
- Document what you build and help teams own and extend their workflows themselves.
Extend what our AI agents can do
- Design and build integrations that let AI agents read, query, and act on civil engineering data: BIM models, alignments, surfaces, pipe networks, drawings, specifications, and project records.
- Develop tools and connectors on top of platforms such as Autodesk Civil 3D, Revit, and Autodesk Platform Services / ACC, Bentley OpenRoads and iTwin, and open formats such as IFC and LandXML.
- Build automations with Dynamo, pyRevit, Python, and C#/.NET where a deterministic script is the right answer and expose them as capabilities an AI agent can call.
- Make sound trade-offs between speed, scope, and quality, and keep everything you ship secure, version-controlled, and maintainable.
Close the loop
- Spot patterns across teams and turn one-off solutions into shared, reusable capabilities.
- Feed field insights back to our digital, IT, and data teams to shape platform priorities and roadmap.
- Contribute to our AI governance, data-handling, and BIM standards so adoption stays responsible as it grows.
Requirements
- Degree in Civil Engineering, Computer Science, or a related field, or equivalent practical experience.
- 4+ years combining software development with BIM, CAD, or digital delivery work, ideally on infrastructure or civil projects.
- Strong coding skills in Python, plus experience with C#/.NET or TypeScript.
- Hands-on experience automating BIM workflows using tools such as Dynamo, pyRevit, the Civil 3D or Revit APIs, or Autodesk Platform Services.
- Practical experience building with large language models: prompt and workflow design, tool or function calling, retrieval over documents, and evaluating model output.
- A working understanding of civil design deliverables: alignments and profiles, corridors, grading, drainage and utility networks, sheet production, and model coordination.
- Comfort working directly with end users: you listen first, explain clearly to non-technical audiences, and build trust by shipping.
- Ownership and a bias for action. You are happy working in ambiguity, scoping your own work, and seeing it through to adoption.
Nice to Have
- Experience building agent integrations, for example using the Model Context Protocol (MCP) or similar tool frameworks.
- Familiarity with openBIM and infrastructure data standards such as IFC 4.3, LandXML, and ISO 19650.
- Experience with Bentley OpenRoads, OpenFlows, or iTwin; Navisworks; or GIS platforms such as ArcGIS.
- Experience with document AI on drawings, specifications, and reports, including PDF and OCR pipelines.
- Background as a practicing civil engineer or BIM coordinator before moving into software.
- Experience delivering training or leading change-management programs in an engineering organization.
Learn more
What Success Looks Like
In your first year, you will have:
- Embedded with several project teams and built a clear map of where AI can save the most time and reduce the most risk.
- Shipped AI workflows that engineers use every week, with measurable time savings and quality improvements.
- Added new civil-specific capabilities to our AI agents, so they can work directly with the models and data our teams produce.
- Built a library of documented, evaluated workflows that other teams can pick up and adapt.
- Become the go-to person engineers call when they think, "There has to be a better way to do this."
Why Join Us
- Real impact: your work goes straight into the maps that help infrastructure owners avoid utility strikes, delays, and safety risks on major projects.
- An AI-native company: AI already sits at the core of how we read the subsurface. You will extend it to how we engineer and deliver.
- A rare mix of disciplines: geophysics, civil engineering, BIM, and modern AI in one role, with a global team spanning the US, Israel, and beyond.
- Room to shape, from the ground up, how a fast-growing company scales its engineering delivery with AI.
- Close collaboration with field, mapping, and engineering experts who care about getting the underground right.
Our mission is to power the next era of underground exploration – saving time, money, lives, and the planet. We are focused, intentional, confident, and hard working. We solve big problems, but we are approachable, open-minded, and love hard questions.
You can learn more about us on our website or check out this short video.
Apply on our careers page, via Linkedin or send your resume to cara.partovich@exodigo.ai
Prep for this interview
5 questions likely to come up at Exodigo, each matched to a line in this posting.
- 1Coding
They wrote: “Strong coding skills in Python, plus experience with C#/.NET or TypeScript.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 2Ownership and working with customers
They wrote: “Ownership and a bias for action. You are happy working in ambiguity, scoping your own work, and seeing it through to adoption.”
Tell me about a project where the requirements kept changing. What did you do?
How to answer
Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.
- The project and why requirements kept moving
- What you did to pin them down (short demos, written decisions)
- The trade-offs you made to keep shipping
- The result, with a number if you have one
Tip: Show how you reduced the change, beyond how you coped with it.
- 3Discovery and scoping
They wrote: “Lead discovery sessions with engineers and project leads, and translate what you hear into clearly scoped, prioritized opportunities for AI and automation.”
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.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- 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.
- 4Integrations and APIs
They wrote: “Design and build integrations that let AI agents read, query, and act on civil engineering data: BIM models, alignments, surfaces, pipe networks, drawings, specifications, and project records.”
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.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- 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.
- 5LLMs, RAG and agents
They wrote: “Partner with senior engineers to capture their know-how (checking procedures, design criteria, QA/QC steps, naming and modeling standards) as reusable AI workflows, prompts, and playbooks.”
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.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- 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.
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.
