Forward Deployed Engineer
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, AI hiring process, etc. Also remove duplicated lines.
We need to extract content.
Let's parse the posting:
- Intro paragraph about Intenseye mission (maybe not needed as it's about company). Could be part of "About Intenseye" but we may not need a heading for that; but we could include as part of "About the role"? Actually "About Intenseye" is company description. Could be considered "About the role"? Not exactly. But we could include a section "About Intenseye" but not in allowed headings list; but instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid other headings, but says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when applicable, but we could also use other headings if needed? It says "use for section headings (e.g. ...)". Likely they expect us to use those standard headings. So we should map content to those headings.
Thus:
- About the role: description of Forward Deployed Engineer role (the paragraph starting "You help us get edge AI running...").
- Responsibilities: the bullet list under "What you will work on:" (Edge AI for safety and operations: detect hazards, track interactions, time exposure, and verify fixes; Turn signals into actions with evidence and simple feedback loops that crews trust; Generalize field work into reusable modules, playbooks, and product improvements). Could also include other duties like meeting team, observing, building prototype, fixing, writing docs, etc. Those are in the role description paragraph. Might be better to put those under Responsibilities as well. But we need to avoid duplication. We could combine all duties into Responsibilities list.
- Requirements: combine "About you:" and "Background:" content. That includes practical problem solver, customer facing, comfortable testing, clear communicator, built and deployed products end to end, collaborative, strong plus past founder, nice to have CV or edge systems, background in manufacturing/logistics/industrial, 1+ years relevant experience, strong engineering background preferred in CS, Math, Software Engineering, Physics, Data Science, strong coder proficiency in Python, TypeScript/JavaScript, React or similar, ability and interest to travel up to 30%.
- Pay: "$140,000 - $200,000 a year"
- Schedule: "This position is based out of our NYC office and requires three days in the office."
We should not include boilerplate like EEO, AI hiring process, etc.
We need to ensure we don't include placeholders like "commensurate with experience". Not present.
Now produce HTML fragment.
Structure:
About the role
You help us get edge AI running in real factories and warehouses, then keep it working. You meet the team, watch how the work actually happens, sketch a simple plan, build a prototype, try it on site, and adjust. When something breaks, you fix it. You write things down so the next install is easier. One week you’re on the floor at 7am observing how things operate. Next you tighten a flow end to end: detect, track, time, alert, then sit with their team to see if you actually solve the problem. You tune it until it’s boring and reliable. You work with backend, frontend, and research teams, share what you learned, and turn the field fix into something we can reuse. There is no playbook. You will help write it and scale deployments across regions.
Responsibilities
- Edge AI for safety and operations: detect hazards, track interactions, time exposure, and verify fixes
- Turn signals into actions with evidence and simple feedback loops that crews trust
- Generalize field work into reusable modules, playbooks, and product improvements
Requirements
- Practical problem solver who enjoys real-world constraints and still ships
- Customer facing by default; you turn vague goals into crisp scopes and success criteria
- Comfortable testing, developing, and validating edge AI flows on site with the users
- Clear communicator with technicians in the morning and exec team in the afternoon
- You have built and deployed products end to end, ideally in startups
- Collaborative; you share context, teach, learn, and iterate with feedback
- Strong plus: past founder or early builder who has owned outcomes front to back
- Nice to have, not required: computer vision or edge systems experience; background in manufacturing, logistics, or industrial settings
- Background: 1+ years of relevant, post-college work experience
- Strong engineering background, preferred in fields such as Computer Science, Mathematics, Software Engineering, Physics, and Data Science
- Strong coder with shown proficiency in programming languages such as Python, TypeScript/JavaScript, React or similar
- Ability and interest to travel up to 30%, as needed to client sites
Pay
$140,000 - $200,000 a year
Schedule
This position is based out of our NYC office and requires three days in the office.
Check for any duplicated content: we included "Background: 1+ years..." as a list item; that's okay.
We should ensure we didn't miss any substantive info: The initial paragraphs about Intenseye mission and "About Intenseye" section describing company. Should we include that? It's substantive but not covered by headings. Could we include as "About the role"? No, that's about role. Could we add a section "About the company"? Not in list but maybe allowed. The instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. However, the company description is substantive; if we omit it, we lose info. But maybe it's considered boilerplate? It's not boilerplate; it's about the company mission. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include it. Where to put? Could be under a heading "About Intenseye". That's not in the list but seems reasonable. The instruction didn't say we cannot use other headings; it just gave examples. So we can add a heading "About Intenseye". Use . That would preserve the info.
Thus add:
About Intenseye
At Intenseye, we believe protecting people at work is non‑negotiable. That’s why we’re building the world’s most advanced AI‑powered platform for industrial environments, designed to help organizations move from reactive programs to proactive risk prevention across safety, operations, and quality management. Our technology gives enterprises the ability to see risk and inefficiency as they emerge, take action in real time, and prevent incidents before they happen. Powered by cutting‑edge AI and Intenseye’s proprietary Sentinel hardware, our platform delivers ethical, highly accurate intelligence across complex worksites. EHS, operations, and quality teams gain continuous leading indicators, deep operational insight, and unprecedented visibility into how work actually happens. Today, Intenseye helps protect hundreds of thousands of workers across 25+ countries—and we’re just getting started.
Then also maybe include the "About Intenseye We build industrial AI where the work happens..." paragraph after that. Actually there is a second paragraph: "About Intenseye We build industrial AI where the work happens. Our edge vision systems plug into real workplaces. They help teams spot risk early, act fast, and keep people and goods moving. Safety is part of the job, not an add-on. We think long term about how factories and DCs should run in ten years and ship tools that move that future into the present. What we actually do: Build fast, reliable models that understand complex physical environments. Package them into plug-and-play workflows that teams adopt in hours, not months. Close the loop from hazard signal to action to measurement to improvement on live floors." This is also substantive. Should we include? It's more detail about what they do. Could be merged into the About Intenseye section. We'll combine both paragraphs into one maybe two
s. Better to keep as separate
under same heading.
Thus:
About Intenseye
At Intenseye, we believe protecting people at work is non‑negotiable. That’s why we’re building the world’s most advanced AI‑powered platform for industrial environments, designed to help organizations move from reactive programs to proactive risk prevention across safety, operations, and quality management. Our technology gives enterprises the ability to see risk and inefficiency as they emerge, take action in real time, and prevent incidents before they happen. Powered by cutting‑edge AI and Intenseye’s proprietary Sentinel hardware, our platform delivers ethical, highly accurate intelligence across complex worksites. EHS, operations, and quality teams gain continuous leading indicators, deep operational insight, and unprecedented visibility into how work actually happens. Today, Intenseye helps protect hundreds of thousands of workers across 25+ countries—and we’re just getting started.
We build industrial AI where the work happens. Our edge vision systems plug into real workplaces.
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, AI hiring process, etc. Also remove duplicated lines. We need to extract content. Let's parse the posting: - Intro paragraph about Intenseye mission (maybe not needed as it's about company). Could be part of "About Intenseye" but we may not need a heading for that; but we could include as part of "About the role"? Actually "About Intenseye" is company description. Could be considered "About the role"? Not exactly. But we could include a section "About Intenseye" but not in allowed headings list; but instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid other headings, but says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when applicable, but we could also use other headings if needed? It says "use for section headings (e.g. ...)". Likely they expect us to use those standard headings. So we should map content to those headings.
Thus:
- About the role: description of Forward Deployed Engineer role (the paragraph starting "You help us get edge AI running...").
- Responsibilities: the bullet list under "What you will work on:" (Edge AI for safety and operations: detect hazards, track interactions, time exposure, and verify fixes; Turn signals into actions with evidence and simple feedback loops that crews trust; Generalize field work into reusable modules, playbooks, and product improvements). Could also include other duties like meeting team, observing, building prototype, fixing, writing docs, etc. Those are in the role description paragraph. Might be better to put those under Responsibilities as well. But we need to avoid duplication. We could combine all duties into Responsibilities list.
- Requirements: combine "About you:" and "Background:" content. That includes practical problem solver, customer facing, comfortable testing, clear communicator, built and deployed products end to end, collaborative, strong plus past founder, nice to have CV or edge systems, background in manufacturing/logistics/industrial, 1+ years relevant experience, strong engineering background preferred in CS, Math, Software Engineering, Physics, Data Science, strong coder proficiency in Python, TypeScript/JavaScript, React or similar, ability and interest to travel up to 30%.
- Pay: "$140,000 - $200,000 a year"
- Schedule: "This position is based out of our NYC office and requires three days in the office."
We should not include boilerplate like EEO, AI hiring process, etc.
We need to ensure we don't include placeholders like "commensurate with experience". Not present.
Now produce HTML fragment.
Structure:
About the role
About the role
You help us get edge AI running in real factories and warehouses, then keep it working. You meet the team, watch how the work actually happens, sketch a simple plan, build a prototype, try it on site, and adjust. When something breaks, you fix it. You write things down so the next install is easier. One week you’re on the floor at 7am observing how things operate. Next you tighten a flow end to end: detect, track, time, alert, then sit with their team to see if you actually solve the problem. You tune it until it’s boring and reliable. You work with backend, frontend, and research teams, share what you learned, and turn the field fix into something we can reuse. There is no playbook. You will help write it and scale deployments across regions.
Responsibilities
- Edge AI for safety and operations: detect hazards, track interactions, time exposure, and verify fixes
- Turn signals into actions with evidence and simple feedback loops that crews trust
- Generalize field work into reusable modules, playbooks, and product improvements
Requirements
- Practical problem solver who enjoys real-world constraints and still ships
- Customer facing by default; you turn vague goals into crisp scopes and success criteria
- Comfortable testing, developing, and validating edge AI flows on site with the users
- Clear communicator with technicians in the morning and exec team in the afternoon
- You have built and deployed products end to end, ideally in startups
- Collaborative; you share context, teach, learn, and iterate with feedback
- Strong plus: past founder or early builder who has owned outcomes front to back
- Nice to have, not required: computer vision or edge systems experience; background in manufacturing, logistics, or industrial settings
- Background: 1+ years of relevant, post-college work experience
- Strong engineering background, preferred in fields such as Computer Science, Mathematics, Software Engineering, Physics, and Data Science
- Strong coder with shown proficiency in programming languages such as Python, TypeScript/JavaScript, React or similar
- Ability and interest to travel up to 30%, as needed to client sites
Pay
$140,000 - $200,000 a year
Schedule
This position is based out of our NYC office and requires three days in the office.
Check for any duplicated content: we included "Background: 1+ years..." as a list item; that's okay. We should ensure we didn't miss any substantive info: The initial paragraphs about Intenseye mission and "About Intenseye" section describing company. Should we include that? It's substantive but not covered by headings. Could we include as "About the role"? No, that's about role. Could we add a section "About the company"? Not in list but maybe allowed. The instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. However, the company description is substantive; if we omit it, we lose info. But maybe it's considered boilerplate? It's not boilerplate; it's about the company mission. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include it. Where to put? Could be under a heading "About Intenseye". That's not in the list but seems reasonable. The instruction didn't say we cannot use other headings; it just gave examples. So we can add a heading "About Intenseye". Use . That would preserve the info.
Thus add:
About Intenseye
About Intenseye
At Intenseye, we believe protecting people at work is non‑negotiable. That’s why we’re building the world’s most advanced AI‑powered platform for industrial environments, designed to help organizations move from reactive programs to proactive risk prevention across safety, operations, and quality management. Our technology gives enterprises the ability to see risk and inefficiency as they emerge, take action in real time, and prevent incidents before they happen. Powered by cutting‑edge AI and Intenseye’s proprietary Sentinel hardware, our platform delivers ethical, highly accurate intelligence across complex worksites. EHS, operations, and quality teams gain continuous leading indicators, deep operational insight, and unprecedented visibility into how work actually happens. Today, Intenseye helps protect hundreds of thousands of workers across 25+ countries—and we’re just getting started.
Then also maybe include the "About Intenseye We build industrial AI where the work happens..." paragraph after that. Actually there is a second paragraph: "About Intenseye We build industrial AI where the work happens. Our edge vision systems plug into real workplaces. They help teams spot risk early, act fast, and keep people and goods moving. Safety is part of the job, not an add-on. We think long term about how factories and DCs should run in ten years and ship tools that move that future into the present. What we actually do: Build fast, reliable models that understand complex physical environments. Package them into plug-and-play workflows that teams adopt in hours, not months. Close the loop from hazard signal to action to measurement to improvement on live floors." This is also substantive. Should we include? It's more detail about what they do. Could be merged into the About Intenseye section. We'll combine both paragraphs into onemaybe two
s. Better to keep as separate
under same heading. Thus:
About Intenseye
At Intenseye, we believe protecting people at work is non‑negotiable. That’s why we’re building the world’s most advanced AI‑powered platform for industrial environments, designed to help organizations move from reactive programs to proactive risk prevention across safety, operations, and quality management. Our technology gives enterprises the ability to see risk and inefficiency as they emerge, take action in real time, and prevent incidents before they happen. Powered by cutting‑edge AI and Intenseye’s proprietary Sentinel hardware, our platform delivers ethical, highly accurate intelligence across complex worksites. EHS, operations, and quality teams gain continuous leading indicators, deep operational insight, and unprecedented visibility into how work actually happens. Today, Intenseye helps protect hundreds of thousands of workers across 25+ countries—and we’re just getting started.
We build industrial AI where the work happens. Our edge vision systems plug into real workplaces.