Lead Forward Deployed Engineer
4M Analytics · Austin, TX · 1 mo ago
HybridEngineeringOther
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: Who We Are (maybe About the role?), Why Join Us (maybe Benefits?), The Role (Responsibilities?), What You'll Do (Responsibilities), Requirements: What You Bring (Requirements), Bonus if you are experienced with: (Skills?), Location and Travel (Schedule? maybe location and travel). There's no explicit Pay or Benefits. There's no explicit Benefits section; "Why Join Us" includes mission impact, career trajectory, etc. That could be considered Benefits? But we should only include Benefits if posting actually states them. It does mention career trajectory, impact, etc. That's more like "Why Join Us" which could be considered Benefits or About the company. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have content:
- Who We Are: description of company mission, size, locations. Could be "About the role"? Actually "About the role" is more about the role itself. But we have "Who We Are" which is about company. Could map to "About the role"? Might be better to use "About the role" for description of role? But we have "The Role" section describing role. So we could use "About the role" for that? However we also have "Why Join Us" which could be Benefits.
We need to avoid repeating job title as heading. No job title given explicitly.
We need to use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: Who We Are (maybe About the role?), Why Join Us (maybe Benefits?), The Role (Responsibilities?), What You'll Do (Responsibilities), Requirements: What You Bring (Requirements), Bonus if you are experienced with: (Skills?), Location and Travel (Schedule? maybe location and travel). There's no explicit Pay or Benefits. There's no explicit Benefits section; "Why Join Us" includes mission impact, career trajectory, etc. That could be considered Benefits? But we should only include Benefits if posting actually states them. It does mention career trajectory, impact, etc. That's more like "Why Join Us" which could be considered Benefits or About the company. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have content:
- Who We Are: description of company mission, size, locations. Could be "About the role"? Actually "About the role" is more about the role itself. But we have "Who We Are" which is about company. Could map to "About the role"? Might be better to use "About the role" for description of role? But we have "The Role" section describing role. So we could use "About the role" for that? However we also have "Why Join Us" which could be Benefits.
We need to avoid repeating job title as heading. No job title given explicitly.
We need to use - for any list of duties/requirements/benefits. We have lists: Requirements bullet points, Bonus bullet points, maybe responsibilities list (What You'll Do bullet points). We'll turn those into
- .
We need to use
for prose.
We must not include boilerplate like EEO etc. There's none.
We must not include sections with filler like "commensurate with experience". Not present.
We need to include sections only when posting has real specific content.
Thus we can have sections:
- About the role (maybe combine Who We Are and The Role? But we have separate: Who We Are (company), The Role (role overview), What You'll Do (responsibilities), Requirements, Bonus (skills), Location and Travel (schedule/location). Could also have Benefits (Why Join Us). Let's map:
About the role: Could be the summary of the role from "The Role". That includes description: founding Forward Deployed Engineer in US, work at intersection, etc. We'll put that as prose.
Responsibilities: from "What You'll Do". We'll list bullet points.
Requirements: from "Requirements: What You Bring". We'll list bullet points.
Skills: from "Bonus if you are experienced with:" list.
Benefits: from "Why Join Us". Could be bullet points? It's prose about impact, career trajectory. We'll put as
.
Schedule: from "Location and Travel": hybrid 3 days a week in Austin, travel expectations. We'll put as
maybe with bullet? It's not a list but we can put as
.
Pay: not present, so omit.
Qualifications: maybe same as Requirements? But we already have Requirements. Could omit Qualifications to avoid duplication.
We need to ensure we don't repeat content. We'll include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now produce HTML fragment.
Structure:
About the role
... (content from The Role)
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
... (Why Join Us)
Schedule
... (Location and Travel)
We must preserve all substantive information. Let's extract.
Who We Are: "The 4M story is likely one you haven't heard before: we're on a mission to unlock access to the world below us - to do for the world below ground what Google Maps did for the world above. By mapping subsurface infrastructure and making reliable, real-time utility data accessible to the construction and infrastructure industry, we're transforming a traditional, high-stakes industry. We're a growing startup with 120 employees, based in Tel Aviv, Israel and Austin, Texas."
Why Join Us: "Joining the Utility Owners Business Unit means you are at the forefront of a mission-critical expansion. You will have a direct impact on how major utilities manage their subsurface risk, preventing catastrophic damage and saving lives. This role offers a unique career trajectory: as a foundational hire, you have the opportunity to grow into owning broader product areas, leading new segments, or shaping our entire AI-product strategy as the business scales."
The Role: "Think like a founder. This is our founding Forward Deployed Engineer in the US - you'll work at the intersection of engineering, product, and the customer, paired day to day with a Product counterpart. You take an ambiguous operational problem, go see how the work actually happens, build the software that solves it, deploy it in the field, and turn what you learn into a product. Own the outcome, not the specification. You'll be the tip of the spear for a new product line: the platform Utility Owners use to run their locate-request and damage-prevention lifecycle end to end. Intake, classification, routing, field coordination, service levels, escalations, auditability, analytics, and AI-assisted workflows. Then you'll grow a US engineering team around it."
What You'll Do: list:
- Build fast, build for real. Ship production-quality software in response to real customer problems. Prototype, validate in the field, then harden.
- Go where the work happens. Spend real time at customer and job sites. Work alongside field crews, operations teams, and physical devices.
- Own complex integrations. Enterprise APIs, utility GIS, national field-technology platforms, and the ticketing networks the industry runs on. Expect undocumented behavior, legacy systems, and messy data.
- Turn field learning into a product. Understand the difference between a one-off request and a reusable platform capability. Partner with core engineering so field wins become a scalable product.
- Lead. Set your own priorities, manage your time, and make architecture calls without a finished spec. As the product scales, you’ll also mentor engineers as the US team grows.
- Be an integral part of the R&D organization. Our engineering center is in Israel. You'll keep it close across time zones - clear updates, tight collaboration, and shared standards.
Requirements: What You Bring:
- 8+ years building software, with a track record of shipping across the stack.
- Demonstrated success of personally building and deploying systems in ambiguous, customer-facing environments.
- Leadership experience with clear leadership instincts: mentoring, setting technical direction, or running a small team.
- Strong fundamentals in data and databases, cloud and distributed systems, security and authentication, and enterprise integration patterns.
- The ability to learn an unfamiliar system quickly and make it work in the field.
- Fluency with AI coding, agentic flows, and modern development practices to move faster.
- Excellent written and verbal communication, and the discipline to collaborate well with a remote team.
- Comfort with ambiguity. It should energize you, not block you.
Bonus if you are experienced with:
- Geospatial and GIS.
- IoT, mobile, or field hardware.
- Utility, energy, transportation, AEC, or industrial software.
Location and Travel:
- This role is hybrid, 3 days a week in our Austin, TX offices.
- Expect regular travel to customer and field sites, plus several trips a year to our R&D center in Israel.
Come work with us! Ready to build the future of subsurface infrastructure? We encourage you to apply even if you don't check every single box above. We are looking for potential, curiosity, and a bias for action above all else. We look forward to meeting you!
We need to remove application instructions like "Come work with us! Ready to build..." etc. That's basically a call to action; we should remove application instructions. The instruction says: remove application instructions. So we should omit the final paragraph that encourages to apply. Also remove "Come work with us! Ready to build the future of subsurface infrastructure? We encourage you to apply even if you don't check every single box above. We are looking for potential, curiosity, and a bias for action above all else. We look forward to meeting you!" That's application instructions. So we should not include that.
Thus Benefits section should only contain the "Why Join Us" prose (maybe also the "Who We Are"? Actually "Who We Are" is about company, could be considered About the role? But we already have About the role from The Role. Could we incorporate Who We Are into About the role? Might be redundant. But we have to preserve all substantive information. If we omit Who We Are, we lose info about company mission, size, locations. That's substantive. Where to put it? Could be part of About the role? But About the role is supposed to be about the role, not company. However we could create a section "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit company info into one of those. Perhaps we can put it under About the role as a preamble? But that might mix role and company. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. So we need to place company info somewhere, maybe under Benefits? But Benefits is about why join us (impact, career trajectory). Company info could be considered part of Benefits? Not exactly. Could be part of About the role? Might be acceptable to include company description under About the role as context. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but it gives examples. Safer to stick to those. We can put company info under About the role as a brief intro before role specifics. That would still be under About the role heading. That would preserve the info.
Thus About the role section will contain both company description (Who We Are) and role overview (The Role). We'll combine them into prose.
Now Benefits: only Why Join Us.
Now Schedule: Location and Travel.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We'll need to escape any special characters? Not needed.
Let's craft.
About the role
The 4M story is likely one you haven't heard before: we're on a mission to unlock access to the world below us - to do for the world below ground what Google Maps did for the world above. By mapping subsurface infrastructure and making reliable, real-time utility data accessible to the construction and infrastructure industry, we're transforming a traditional, high-stakes industry. We're a growing startup with 120 employees, based in Tel Aviv, Israel and Austin, Texas. Think like a founder. This is our founding Forward Deployed Engineer in the US - you'll work at the intersection of engineering, product, and the customer, paired day to day with a Product counterpart. You take an ambiguous operational problem, go see how the work
- .
We need to use
for prose. We must not include boilerplate like EEO etc. There's none. We must not include sections with filler like "commensurate with experience". Not present. We need to include sections only when posting has real specific content. Thus we can have sections: - About the role (maybe combine Who We Are and The Role? But we have separate: Who We Are (company), The Role (role overview), What You'll Do (responsibilities), Requirements, Bonus (skills), Location and Travel (schedule/location). Could also have Benefits (Why Join Us). Let's map: About the role: Could be the summary of the role from "The Role". That includes description: founding Forward Deployed Engineer in US, work at intersection, etc. We'll put that as prose. Responsibilities: from "What You'll Do". We'll list bullet points. Requirements: from "Requirements: What You Bring". We'll list bullet points. Skills: from "Bonus if you are experienced with:" list. Benefits: from "Why Join Us". Could be bullet points? It's prose about impact, career trajectory. We'll put as
. Schedule: from "Location and Travel": hybrid 3 days a week in Austin, travel expectations. We'll put as
maybe with bullet? It's not a list but we can put as
. Pay: not present, so omit. Qualifications: maybe same as Requirements? But we already have Requirements. Could omit Qualifications to avoid duplication. We need to ensure we don't repeat content. We'll include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Now produce HTML fragment. Structure:
About the role
... (content from The Role)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
... (Why Join Us)
Schedule
... (Location and Travel)
We must preserve all substantive information. Let's extract. Who We Are: "The 4M story is likely one you haven't heard before: we're on a mission to unlock access to the world below us - to do for the world below ground what Google Maps did for the world above. By mapping subsurface infrastructure and making reliable, real-time utility data accessible to the construction and infrastructure industry, we're transforming a traditional, high-stakes industry. We're a growing startup with 120 employees, based in Tel Aviv, Israel and Austin, Texas." Why Join Us: "Joining the Utility Owners Business Unit means you are at the forefront of a mission-critical expansion. You will have a direct impact on how major utilities manage their subsurface risk, preventing catastrophic damage and saving lives. This role offers a unique career trajectory: as a foundational hire, you have the opportunity to grow into owning broader product areas, leading new segments, or shaping our entire AI-product strategy as the business scales." The Role: "Think like a founder. This is our founding Forward Deployed Engineer in the US - you'll work at the intersection of engineering, product, and the customer, paired day to day with a Product counterpart. You take an ambiguous operational problem, go see how the work actually happens, build the software that solves it, deploy it in the field, and turn what you learn into a product. Own the outcome, not the specification. You'll be the tip of the spear for a new product line: the platform Utility Owners use to run their locate-request and damage-prevention lifecycle end to end. Intake, classification, routing, field coordination, service levels, escalations, auditability, analytics, and AI-assisted workflows. Then you'll grow a US engineering team around it." What You'll Do: list: - Build fast, build for real. Ship production-quality software in response to real customer problems. Prototype, validate in the field, then harden. - Go where the work happens. Spend real time at customer and job sites. Work alongside field crews, operations teams, and physical devices. - Own complex integrations. Enterprise APIs, utility GIS, national field-technology platforms, and the ticketing networks the industry runs on. Expect undocumented behavior, legacy systems, and messy data. - Turn field learning into a product. Understand the difference between a one-off request and a reusable platform capability. Partner with core engineering so field wins become a scalable product. - Lead. Set your own priorities, manage your time, and make architecture calls without a finished spec. As the product scales, you’ll also mentor engineers as the US team grows. - Be an integral part of the R&D organization. Our engineering center is in Israel. You'll keep it close across time zones - clear updates, tight collaboration, and shared standards. Requirements: What You Bring: - 8+ years building software, with a track record of shipping across the stack. - Demonstrated success of personally building and deploying systems in ambiguous, customer-facing environments. - Leadership experience with clear leadership instincts: mentoring, setting technical direction, or running a small team. - Strong fundamentals in data and databases, cloud and distributed systems, security and authentication, and enterprise integration patterns. - The ability to learn an unfamiliar system quickly and make it work in the field. - Fluency with AI coding, agentic flows, and modern development practices to move faster. - Excellent written and verbal communication, and the discipline to collaborate well with a remote team. - Comfort with ambiguity. It should energize you, not block you. Bonus if you are experienced with: - Geospatial and GIS. - IoT, mobile, or field hardware. - Utility, energy, transportation, AEC, or industrial software. Location and Travel: - This role is hybrid, 3 days a week in our Austin, TX offices. - Expect regular travel to customer and field sites, plus several trips a year to our R&D center in Israel. Come work with us! Ready to build the future of subsurface infrastructure? We encourage you to apply even if you don't check every single box above. We are looking for potential, curiosity, and a bias for action above all else. We look forward to meeting you! We need to remove application instructions like "Come work with us! Ready to build..." etc. That's basically a call to action; we should remove application instructions. The instruction says: remove application instructions. So we should omit the final paragraph that encourages to apply. Also remove "Come work with us! Ready to build the future of subsurface infrastructure? We encourage you to apply even if you don't check every single box above. We are looking for potential, curiosity, and a bias for action above all else. We look forward to meeting you!" That's application instructions. So we should not include that. Thus Benefits section should only contain the "Why Join Us" prose (maybe also the "Who We Are"? Actually "Who We Are" is about company, could be considered About the role? But we already have About the role from The Role. Could we incorporate Who We Are into About the role? Might be redundant. But we have to preserve all substantive information. If we omit Who We Are, we lose info about company mission, size, locations. That's substantive. Where to put it? Could be part of About the role? But About the role is supposed to be about the role, not company. However we could create a section "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit company info into one of those. Perhaps we can put it under About the role as a preamble? But that might mix role and company. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. So we need to place company info somewhere, maybe under Benefits? But Benefits is about why join us (impact, career trajectory). Company info could be considered part of Benefits? Not exactly. Could be part of About the role? Might be acceptable to include company description under About the role as context. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but it gives examples. Safer to stick to those. We can put company info under About the role as a brief intro before role specifics. That would still be under About the role heading. That would preserve the info. Thus About the role section will contain both company description (Who We Are) and role overview (The Role). We'll combine them into prose. Now Benefits: only Why Join Us. Now Schedule: Location and Travel. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft.
About the role
The 4M story is likely one you haven't heard before: we're on a mission to unlock access to the world below us - to do for the world below ground what Google Maps did for the world above. By mapping subsurface infrastructure and making reliable, real-time utility data accessible to the construction and infrastructure industry, we're transforming a traditional, high-stakes industry. We're a growing startup with 120 employees, based in Tel Aviv, Israel and Austin, Texas. Think like a founder. This is our founding Forward Deployed Engineer in the US - you'll work at the intersection of engineering, product, and the customer, paired day to day with a Product counterpart. You take an ambiguous operational problem, go see how the work