Forward Deployed Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content.
We need to parse the job posting.
First, about the role: The initial paragraph describing Quadric and the opportunity. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Intro: "Quadric is redefining edge AI...". That's about the company and role context. Could be "About the role" or maybe "About the company". We'll use "About the role".
- Then "The Opportunity" with bullet-like paragraphs: "You'll own the technical path...". That's responsibilities.
- Then "What You'll Do" with bullet points: Own the Technical Path..., Embed..., Build..., Close the Loop... That's responsibilities as well.
- Then "What Success Looks Like": could be also responsibilities or expectations. Could be part of responsibilities.
- Then "What We're Looking For": Required and Preferred. That's qualifications/requirements/skills.
- Then "What we offer": includes base salary range, equity, bonus, benefits list. So we have Pay (salary range), Benefits (list), maybe also Schedule? Not mentioned. So we should include Pay and Benefits sections.
We must not include boilerplate like EEO, E-Verify, Privacy, etc.
We must not repeat job title as heading.
We must not include Job ID etc.
We need to preserve all substantive information.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to avoid filler sections like "Pay" if not specified; but we have salary range.
We need to avoid "Schedule" if not specified.
We need to ensure we don't create sections with placeholder text.
Now, let's extract content.
About the role: combine the introductory paragraphs up to "The Opportunity". Actually "The Opportunity" is a heading in the posting; but we treat that as part of responsibilities. So About the role could be the company description: "Quadric is redefining edge AI with the industry's first General Purpose Neural Processing Unit (GPNPU), enabling developers to run both neural network inference and conventional C++ code on a single programmable architecture. Our technology powers intelligent edge devices across automotive, industrial, robotics, and embedded systems. Founded in 2016 and based in downtown Burlingame, California, Quadric is building the world's first supercomputer designed for the real-time needs of edge devices. Quadric aims to empower developers in every industry with superpowers to create tomorrow's technology, today. The company was co-founded by technologists from MIT and Carnegie Mellon, who were previously the technical co-founders of the Bitcoin computing company 21."
That's substantive.
Now Responsibilities: combine "The Opportunity" paragraphs and "What You'll Do" and "What Success Looks Like". Let's extract.
The Opportunity text:
"You'll own the technical path from customer evaluation to silicon design and win on a genuinely novel architecture, the Quadric Chimera GPNPU, which runs everything from CNNs to LLMs to arbitrary C++ on one core, with no fallback processor. Unlike a FAANG solutions role, you'll work the entire stack: quantization, custom kernels, and compiler and your fingerprints will be on chips that ship in cars, cameras, and network appliances. At a Series C company, every design win has outsized impact. Our FDEs also build with frontier agentic tooling (Claude Code–based agentic workflows) — you won't just be supporting the product, you'll be inventing how edge-AI field engineering is done."
What You'll Do bullet points (converted to list):
- Own the Technical Path to Design Win: Convert 2–3 active customer evaluations into committed design wins by getting customer workloads running at target latency and accuracy on Chimera. Port customer workloads onto Chimera — architect, adapt, profile, and write custom kernels when required.
- Embed with Customer Engineering Teams: Work on-site and remotely with customer engineering teams: debug failures, hit benchmark targets, and guide model-architecture tradeoffs. Drive evaluations forward end-to-end, from first technical conversation through design win.
- Build the Agentic FDE Toolkit: Codify what you learn into reusable assets — SDK skills, porting playbooks, and agentic content — so each subsequent engagement moves faster than the last. Build applications and benchmark collateral that support future customer engagements.
- Close the Loop Internally: Partner with engineering and product teams to relay customer learnings and shape the roadmap. Contribute skills and playbooks to Quadric's growing agentic FDE toolset.
What Success Looks Like (list):
- Within your first 6–12 months, you'll:
- Convert 2–3 active customer evaluations into committed design wins on the Chimera platform.
- Build deep fluency across the Chimera stack — quantization, custom kernels, and compiler tooling — well enough to unblock customers independently.
- Establish reusable SDK skills and porting playbooks that measurably shorten the next engagement's timeline.
- Become a trusted technical partner to customer engineering teams, known for translating ambiguous requirements into shipped results.
- Help define and refine Quadric's agentic (Claude Code–based) FDE workflow — there's no existing playbook yet; you'll help write it.
We can combine these into responsibilities.
Now Requirements/Qualifications/Skills: The posting has "What We're Looking For" with Required and Preferred.
Required:
- Strong C++ and Python; has written performance-critical code for a constrained target (DSP, NPU, GPU, or embedded SoC).
- Systems-level performance intuition — memory bandwidth, data movement, cycle-level reasoning — and can read a profile and know where the time went.
- High agency and independent problem-solving; methodical and empirical rather than theoretical.
- Comfortable operating without a playbook and in ambiguity — this role is still being defined.
Preferred:
- Prior FAE, Sales Engineering, or FDE title — or startup experience as the de facto owner of an end-to-end implementation.
- Familiarity with agentic dev tooling (Claude Code, MCP) — or strong enthusiasm to adopt it.
- Background at NPU/edge-AI IP and silicon companies
- Background at inference-focused startups in field/customer engineering or kernel teams.
- FDE experience — candidates with embedded or ML-systems backgrounds.
- Experience at technical trading arms optimizing kernels or hardware for speed
- Big-firm consulting background, provided the candidate personally did the hands-on technical work rather than managing it.
We could split into Requirements (Required) and Qualifications (Preferred) or Skills. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide mapping.
We could have:
-
Requirements
for Required.
- Qualifications
for Preferred (or Skills).
But we also have Skills maybe separate.
We could put Required under Requirements, Preferred under Qualifications, and maybe Skills under Skills (but we already covered). However we might combine.
Better: Use Requirements for Required, Qualifications for Preferred, and maybe Skills for technical skills like C++ etc. But we already have those in Required.
Given instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include any of those that have content.
Thus we can have:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Benefits
- Pay
We don't have Schedule.
Now Benefits: list from "What we offer": Medical, dental, and vision insurance from day one - Premiums covered at 99% for Employees; Company-paid life Insurance; Voluntary supplemental life insurance; STD + LTD insurance; Commuter support including parking or Caltrain reimbursement.; Our office is conveniently located within walking distance of the Caltrain station; FSA + HSA; Equity with the business; Paid Parental Leave; 401(k) Retirement Plan; Flexible PTO; Winter holiday shutdown; Catered lunch each day in our office; Downtown Burlingame office location, close to shops, cafes, and local amenities; Collaborative, low-ego culture with significant ownership and impact; A work culture focused on innovative disruption.
We need to preserve all substantive information. Some are phrases like "Premiums covered at 99% for Employees". We'll keep as list items.
Pay: base salary range $170,000 to $230,000, plus equity and discretionary annual performance bonus. Also mention that actual base salary depends on factors. We'll include that as prose.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Make sure not to include empty sections.
Now we need to ensure we preserve all substantive information. Let's craft each.
About the role paragraph: combine the intro.
We'll write:
Quadric is redefining edge AI with the industry's first General Purpose Neural Processing Unit (GPNPU), enabling developers to run both neural network inference and conventional C++ code on a single programmable architecture. Our technology powers intelligent edge devices across automotive, industrial, robotics, and embedded systems. Founded in 2016 and based in downtown Burlingame, California, Quadric is building the world's first supercomputer designed for the real-time needs of edge devices. Quadric aims to empower developers in every industry with superpowers to create tomorrow's technology, today. The company was co-founded by technologists from MIT and Carnegie Mellon, who were previously the technical co-founders of the Bitcoin computing company 21.
Now Responsibilities: we need to combine the opportunity paragraph and the what you'll do and success looks like. Could be a single with items.
But the opportunity paragraph is prose; we could put it as a then list items. However instruction: use
- for any list of duties/requirements/benefits, and
for prose. So we can have a prose paragraph for the opportunity, then a list for the specific duties.
Thus:
Responsibilities
You'll own the technical path from customer evaluation to silicon design and win on a genuinely novel architecture, the Quadric Chimera GPNPU, which runs everything from CNNs to LLMs to arbitrary C++ on one core, with no fallback processor. Unlike a FAANG solutions role, you'll work the entire stack: quantization, custom kernels, and compiler and your fingerprints will be on chips that ship in cars, cameras, and network appliances. At a Series C company, every design win has outsized impact. Our FDEs also build with frontier agentic tooling (Claude Code–based agentic workflows) — you won't just be supporting the product, you'll be inventing how edge-AI field engineering is done.
- Own the Technical Path to Design Win: Convert 2–3 active customer evaluations into committed design wins by getting customer workloads running at target latency and accuracy on Chimera. Port customer workloads onto Chimera — architect, adapt, profile, and write custom kernels when required.
- Embed with Customer Engineering Teams: Work on-site and remotely with customer engineering teams: debug failures, hit benchmark targets, and guide model-architecture
for prose. We need to avoid filler sections like "Pay" if not specified; but we have salary range. We need to avoid "Schedule" if not specified. We need to ensure we don't create sections with placeholder text. Now, let's extract content. About the role: combine the introductory paragraphs up to "The Opportunity". Actually "The Opportunity" is a heading in the posting; but we treat that as part of responsibilities. So About the role could be the company description: "Quadric is redefining edge AI with the industry's first General Purpose Neural Processing Unit (GPNPU), enabling developers to run both neural network inference and conventional C++ code on a single programmable architecture. Our technology powers intelligent edge devices across automotive, industrial, robotics, and embedded systems. Founded in 2016 and based in downtown Burlingame, California, Quadric is building the world's first supercomputer designed for the real-time needs of edge devices. Quadric aims to empower developers in every industry with superpowers to create tomorrow's technology, today. The company was co-founded by technologists from MIT and Carnegie Mellon, who were previously the technical co-founders of the Bitcoin computing company 21." That's substantive. Now Responsibilities: combine "The Opportunity" paragraphs and "What You'll Do" and "What Success Looks Like". Let's extract. The Opportunity text: "You'll own the technical path from customer evaluation to silicon design and win on a genuinely novel architecture, the Quadric Chimera GPNPU, which runs everything from CNNs to LLMs to arbitrary C++ on one core, with no fallback processor. Unlike a FAANG solutions role, you'll work the entire stack: quantization, custom kernels, and compiler and your fingerprints will be on chips that ship in cars, cameras, and network appliances. At a Series C company, every design win has outsized impact. Our FDEs also build with frontier agentic tooling (Claude Code–based agentic workflows) — you won't just be supporting the product, you'll be inventing how edge-AI field engineering is done." What You'll Do bullet points (converted to list): - Own the Technical Path to Design Win: Convert 2–3 active customer evaluations into committed design wins by getting customer workloads running at target latency and accuracy on Chimera. Port customer workloads onto Chimera — architect, adapt, profile, and write custom kernels when required. - Embed with Customer Engineering Teams: Work on-site and remotely with customer engineering teams: debug failures, hit benchmark targets, and guide model-architecture tradeoffs. Drive evaluations forward end-to-end, from first technical conversation through design win. - Build the Agentic FDE Toolkit: Codify what you learn into reusable assets — SDK skills, porting playbooks, and agentic content — so each subsequent engagement moves faster than the last. Build applications and benchmark collateral that support future customer engagements. - Close the Loop Internally: Partner with engineering and product teams to relay customer learnings and shape the roadmap. Contribute skills and playbooks to Quadric's growing agentic FDE toolset. What Success Looks Like (list): - Within your first 6–12 months, you'll: - Convert 2–3 active customer evaluations into committed design wins on the Chimera platform. - Build deep fluency across the Chimera stack — quantization, custom kernels, and compiler tooling — well enough to unblock customers independently. - Establish reusable SDK skills and porting playbooks that measurably shorten the next engagement's timeline. - Become a trusted technical partner to customer engineering teams, known for translating ambiguous requirements into shipped results. - Help define and refine Quadric's agentic (Claude Code–based) FDE workflow — there's no existing playbook yet; you'll help write it. We can combine these into responsibilities. Now Requirements/Qualifications/Skills: The posting has "What We're Looking For" with Required and Preferred. Required: - Strong C++ and Python; has written performance-critical code for a constrained target (DSP, NPU, GPU, or embedded SoC). - Systems-level performance intuition — memory bandwidth, data movement, cycle-level reasoning — and can read a profile and know where the time went. - High agency and independent problem-solving; methodical and empirical rather than theoretical. - Comfortable operating without a playbook and in ambiguity — this role is still being defined. Preferred: - Prior FAE, Sales Engineering, or FDE title — or startup experience as the de facto owner of an end-to-end implementation. - Familiarity with agentic dev tooling (Claude Code, MCP) — or strong enthusiasm to adopt it. - Background at NPU/edge-AI IP and silicon companies - Background at inference-focused startups in field/customer engineering or kernel teams. - FDE experience — candidates with embedded or ML-systems backgrounds. - Experience at technical trading arms optimizing kernels or hardware for speed - Big-firm consulting background, provided the candidate personally did the hands-on technical work rather than managing it. We could split into Requirements (Required) and Qualifications (Preferred) or Skills. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide mapping. We could have: -
Requirements
for Required. -Qualifications
for Preferred (or Skills). But we also have Skills maybe separate. We could put Required under Requirements, Preferred under Qualifications, and maybe Skills under Skills (but we already covered). However we might combine. Better: Use Requirements for Required, Qualifications for Preferred, and maybe Skills for technical skills like C++ etc. But we already have those in Required. Given instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include any of those that have content.
Thus we can have:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Benefits
- Pay
We don't have Schedule.
Now Benefits: list from "What we offer": Medical, dental, and vision insurance from day one - Premiums covered at 99% for Employees; Company-paid life Insurance; Voluntary supplemental life insurance; STD + LTD insurance; Commuter support including parking or Caltrain reimbursement.; Our office is conveniently located within walking distance of the Caltrain station; FSA + HSA; Equity with the business; Paid Parental Leave; 401(k) Retirement Plan; Flexible PTO; Winter holiday shutdown; Catered lunch each day in our office; Downtown Burlingame office location, close to shops, cafes, and local amenities; Collaborative, low-ego culture with significant ownership and impact; A work culture focused on innovative disruption.
We need to preserve all substantive information. Some are phrases like "Premiums covered at 99% for Employees". We'll keep as list items.
Pay: base salary range $170,000 to $230,000, plus equity and discretionary annual performance bonus. Also mention that actual base salary depends on factors. We'll include that as prose.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Make sure not to include empty sections. Now we need to ensure we preserve all substantive information. Let's craft each. About the role paragraph: combine the intro. We'll write:Quadric is redefining edge AI with the industry's first General Purpose Neural Processing Unit (GPNPU), enabling developers to run both neural network inference and conventional C++ code on a single programmable architecture. Our technology powers intelligent edge devices across automotive, industrial, robotics, and embedded systems. Founded in 2016 and based in downtown Burlingame, California, Quadric is building the world's first supercomputer designed for the real-time needs of edge devices. Quadric aims to empower developers in every industry with superpowers to create tomorrow's technology, today. The company was co-founded by technologists from MIT and Carnegie Mellon, who were previously the technical co-founders of the Bitcoin computing company 21.
Now Responsibilities: we need to combine the opportunity paragraph and the what you'll do and success looks like. Could be a single- with items.
But the opportunity paragraph is prose; we could put it as a
- for any list of duties/requirements/benefits, and
for prose. So we can have a prose paragraph for the opportunity, then a list for the specific duties. Thus:
Responsibilities
You'll own the technical path from customer evaluation to silicon design and win on a genuinely novel architecture, the Quadric Chimera GPNPU, which runs everything from CNNs to LLMs to arbitrary C++ on one core, with no fallback processor. Unlike a FAANG solutions role, you'll work the entire stack: quantization, custom kernels, and compiler and your fingerprints will be on chips that ship in cars, cameras, and network appliances. At a Series C company, every design win has outsized impact. Our FDEs also build with frontier agentic tooling (Claude Code–based agentic workflows) — you won't just be supporting the product, you'll be inventing how edge-AI field engineering is done.
- Own the Technical Path to Design Win: Convert 2–3 active customer evaluations into committed design wins by getting customer workloads running at target latency and accuracy on Chimera. Port customer workloads onto Chimera — architect, adapt, profile, and write custom kernels when required.
- Embed with Customer Engineering Teams: Work on-site and remotely with customer engineering teams: debug failures, hit benchmark targets, and guide model-architecture
then list items. However instruction: use