Senior AI Engineer (Edge Dialog Systems)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: description paragraph(s) at start: "Senior AI Engineer – Edge Dialog Systems BrightAI is a high-growth Physical AI company...". We'll put that in
. - Responsibilities: list of responsibilities bullet points. We'll create
Responsibilities
then- each.
- Educational Background: maybe under Requirements or Qualifications. The posting has "Educational Background" then "Applied background...". Could be part of Requirements/Qualifications. We'll treat as Requirements.
- Required Skills & Expertise: includes LLM and retrieval foundation etc. Could be Skills.
- Edge Dialog Systems Engineering — What This Role Additionally Requires: more skills.
- Growth Axis — Desirable Rather Than Required: desirable skills.
- Bonus Qualifications: more.
- Location & Type: location and type.
We need to decide which sections to output: About the role, Responsibilities, Requirements (maybe combine Educational Background and Required Skills?), Skills (maybe combine Required Skills & Expertise and Edge Dialog Systems Engineering?), Benefits, Pay, Schedule: none present, so omit.
We must not create sections with placeholder text. So only include sections with actual content.
We'll produce:
About the role
...
Responsibilities
- ...
Requirements
- ... maybe combine Educational Background, Required Skills & Expertise, Edge Dialog Systems Engineering, Growth Axis (desirable), Bonus Qualifications? But we need to separate maybe Requirements vs Skills vs Desirable. However instructions: Prefer a few substantive sections over many thin ones. So we could combine all qualification-like content into one Requirements section. But we must preserve all substantive info; we can list them as bullet points.
We need to ensure we don't lose nuance: maybe separate into Requirements and Desired Skills (Growth Axis) and Bonus Qualifications. But that's many sections. Could combine into Requirements and then a separate Desired Skills section. But we need to decide.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe two sections: Responsibilities and Requirements (including all skill/education/desired/bonus). That seems okay.
But we also have Location & Type: that's substantive; could be a short paragraph under About the role or separate section? Could be a small
- .
Now Requirements: combine Educational Background, Required Skills & Expertise, Edge Dialog Systems Engineering — What This Role Additionally Requires, Growth Axis — Desirable Rather Than Required, Bonus Qualifications.
We need to list bullet points preserving all details.
Let's extract each:
Educational Background:
"Trained in AI, Machine Learning, Electrical/Computer Engineering, or a related field, with specialization in NLP, speech, or deep learning; or equivalent industry experience delivering production conversational AI systems.
Applied background in NLU, dialog systems, or on-device machine learning."
Required Skills & Expertise:
"LLM and retrieval foundation — the baseline for this role
5+ years of experience in ML/AI, with a strong focus on NLP, LLMs, or conversational AI.
Strong applied experience with LLMs: prompting, structured output, tool and function calling, evaluation, and retrieval-augmented generation (RAG) – together with the judgment to recognize when a model should not be used at all.
Solid command of embeddings and semantic similarity (e.g., cosine similarity, centroid versus maximum-similarity strategies, threshold tuning, and out-of-domain detection).
Strong Python with the ability to write clean, tested, reviewable code. Fluent with pytest, and Git and has CI discipline."
Edge Dialog Systems Engineering — What This Role Additionally Requires:
"Strong experience building edge conversational systems, including multi-turn dialog/state management and efficient intent/NLU pipelines using local-first, cheap-to-expensive inference strategies.
Disambiguation and repair: resolving ambiguous intent and noisy spoken references, and asking a clarifying question or re-prompting rather than committing to a confident wrong answer.
Comfort placing deterministic guardrails around a probabilistic model, including safety floors, confirmation gating, and negation handling, and experience with state-machine or workflow engines covering branching, variable capture, and resumability.
Experience running models on constrained hardware such as NPUs, mobile, or embedded targets, under real latency, memory budgets. This includes ONNX and onnxruntime, model quantization, and cross-architecture packaging for aarch64.
Practical embedded development workflow: Linux, Docker, adb, systemd services, and the ability to diagnose problems from device logs.
The ability to take ownership of an existing, non-trivial codebase and keep it healthy.
A safety-first instinct, a misheard answer on a safety-critical step is treated as a hazard, not as a metric regression.
Measurement discipline: benchmarking under realistic device conditions, curated golden datasets used as regression gates, and attention to embedding collisions and centroid drift as the command catalog grows.
Excellent problem-solving skills and strong written and verbal communication, with the ability to collaborate across engineering, product, and domain experts."
Growth Axis — Desirable Rather Than Required:
"SLM fine-tuning, including LoRA and QLoRA, instruction and format tuning, and distillation of a larger evaluator model into a smaller on-device model.
Latency and footprint optimization: INT8 and INT4 quantization, ONNX export and graph optimization, hardware-aware model selection, and profiling to reduce inference costs.
A pragmatic view of the boundary between configuration-driven adaptation and fine-tuning.
Building the data flywheel that supports this work, turning on-device session logs into evaluation sets and training data."
Bonus Qualifications:
"Speech recognition experience and comfort working downstream of noisy transcription.
Familiarity with LLM-as-a-judge evaluation.
Multilingual NLU; the system's data layer is already language-partitioned.
Industrial, field-service, or safety-critical product experience, for example in utilities, energy, or manufacturing.
GO familiarity, for integration with the on-device voice pipeline agent.
Exposure to MCP or agentic tooling.
Prior experience in a startup or a fast-paced team, building products from ground up."
Location & Type we already handled.
Now we need to output HTML fragment only.
We'll wrap sections in appropriate tags.
We'll output:
About the role
Senior AI Engineer – Edge Dialog Systems BrightAI is a high-growth Physical AI company transforming how businesses interact with the physical world through intelligent automation. Our AI platform processes visual, spatial, and temporal data from billions of real-world events—captured across edge devices, mobile sensors, and cloud infrastructure—to enable intelligent decision-making at scale. We are now hiring a Sr. AI Engineer – Edge Dialog Systems to own and evolve the on-device conversational AI that powers our industrial safety wearable. The assistant guides field technicians through safety-critical procedures by voice, and it runs on the device itself, under hard latency, memory, and thermal budgets, with deterministic safeguards that take precedence over model output. This is a systems role rather than a prompt-and-retrieve role. The competencies of a strong LLM and RAG engineer are needed for the position, but the work itself is dialog systems engineering at the edge, where most conversational turns are resolved by deterministic and embedding-based methods, and the language model is the last resort rather than the first move.
Location & Type: Full-time, on-site or hybrid, based in Palo Alto, CA.
Responsibilities
- Own the on-device dialog pipeline end to end: intent routing, hybrid intent classification (pattern matching combined with embedding similarity and out-of-domain detection), text normalization for noisy speech input, and the multi-step guided-procedure engine.
- Maintain and extend the deterministic safety layer that wraps the language model—confirmation and echo-back gating, criticality tagging, negation handling—so that a misheard answer on a safety-critical step cannot pass silently.
- Run SLM inference on-device under memory, computational complexity, and latency budgets, and reduce the per-turn inference cost through model selection, quantization, and runtime optimization.
- Preserve and extend the zero-shot configuration model, in which new device commands and customer procedures are authored as data rather than released as code, so that a new customer can be onboarded in hours rather than weeks.
- Coordinate the device deployment pipeline with the edge team
- Maintain the API contract with on-
after About the role. Since it's location and type, we could include in About the role paragraph or separate small section like
Location & Type
but that might be considered thin. However it's substantive info. Could be aafter About the role. We'll include Location & Type as a
after About the role. Thus sections: About the role (including location?), Responsibilities, Requirements. Let's extract content. About the role paragraph: The first paragraph(s) before Responsibilities: "Senior AI Engineer – Edge Dialog Systems BrightAI is a high-growth Physical AI company transforming how businesses interact with the physical world through intelligent automation. Our AI platform processes visual, spatial, and temporal data from billions of real-world events—captured across edge devices, mobile sensors, and cloud infrastructure—to enable intelligent decision-making at scale. We are now hiring a Sr. AI Engineer – Edge Dialog Systems to own and evolve the on-device conversational AI that powers our industrial safety wearable. The assistant guides field technicians through safety-critical procedures by voice, and it runs on the device itself, under hard latency, memory, and thermal budgets, with deterministic safeguards that take precedence over model output. This is a systems role rather than a prompt-and-retrieve role. The competencies of a strong LLM and RAG engineer are needed for the position, but the work itself is dialog systems engineering at the edge, where most conversational turns are resolved by deterministic and embedding-based methods, and the language model is the last resort rather than the first move." We'll keep that as one
. Location & Type: "Location & TypeFull-time, on-site or hybrid, based in Palo Alto, CA." We'll make a
maybe. Now Responsibilities bullet list: Let's extract each line after "Responsibilities". The text: "Own the on-device dialog pipeline end to end: intent routing, hybrid intent classification (pattern matching combined with embedding similarity and out-of-domain detection), text normalization for noisy speech input, and the multi-step guided-procedure engine. Maintain and extend the deterministic safety layer that wraps the language model—confirmation and echo-back gating, criticality tagging, negation handling—so that a misheard answer on a safety-critical step cannot pass silently. Run SLM inference on-device under memory, computational complexity, and latency budgets, and reduce the per-turn inference cost through model selection, quantization, and runtime optimization. Preserve and extend the zero-shot configuration model, in which new device commands and customer procedures are authored as data rather than released as code, so that a new customer can be onboarded in hours rather than weeks. Coordinate the device deployment pipeline with the edge team Maintain the API contract with on-device voice pipeline & its speech-to-text (STT) stack. Define and run on-device benchmarks: latency, accuracy, and false-accept/reject rates on safety-critical steps; use measurements to drive engineering decisions. Build and maintain golden datasets and a non-regression suite, and use them as the release gate as the command and procedure catalogs grow. Lead the migration from zero-shot to fine-tuned on-device models in order to reduce latency, without reintroducing a per-customer retraining burden. Collaborate with product, firmware, and cloud teams, and bring new capabilities online, including additional languages, device commands, and guided workflows." We'll make each as
- .
Now Requirements: combine Educational Background, Required Skills & Expertise, Edge Dialog Systems Engineering — What This Role Additionally Requires, Growth Axis — Desirable Rather Than Required, Bonus Qualifications.
We need to list bullet points preserving all details.
Let's extract each:
Educational Background:
"Trained in AI, Machine Learning, Electrical/Computer Engineering, or a related field, with specialization in NLP, speech, or deep learning; or equivalent industry experience delivering production conversational AI systems.
Applied background in NLU, dialog systems, or on-device machine learning."
Required Skills & Expertise:
"LLM and retrieval foundation — the baseline for this role
5+ years of experience in ML/AI, with a strong focus on NLP, LLMs, or conversational AI.
Strong applied experience with LLMs: prompting, structured output, tool and function calling, evaluation, and retrieval-augmented generation (RAG) – together with the judgment to recognize when a model should not be used at all.
Solid command of embeddings and semantic similarity (e.g., cosine similarity, centroid versus maximum-similarity strategies, threshold tuning, and out-of-domain detection).
Strong Python with the ability to write clean, tested, reviewable code. Fluent with pytest, and Git and has CI discipline."
Edge Dialog Systems Engineering — What This Role Additionally Requires:
"Strong experience building edge conversational systems, including multi-turn dialog/state management and efficient intent/NLU pipelines using local-first, cheap-to-expensive inference strategies.
Disambiguation and repair: resolving ambiguous intent and noisy spoken references, and asking a clarifying question or re-prompting rather than committing to a confident wrong answer.
Comfort placing deterministic guardrails around a probabilistic model, including safety floors, confirmation gating, and negation handling, and experience with state-machine or workflow engines covering branching, variable capture, and resumability.
Experience running models on constrained hardware such as NPUs, mobile, or embedded targets, under real latency, memory budgets. This includes ONNX and onnxruntime, model quantization, and cross-architecture packaging for aarch64.
Practical embedded development workflow: Linux, Docker, adb, systemd services, and the ability to diagnose problems from device logs.
The ability to take ownership of an existing, non-trivial codebase and keep it healthy.
A safety-first instinct, a misheard answer on a safety-critical step is treated as a hazard, not as a metric regression.
Measurement discipline: benchmarking under realistic device conditions, curated golden datasets used as regression gates, and attention to embedding collisions and centroid drift as the command catalog grows.
Excellent problem-solving skills and strong written and verbal communication, with the ability to collaborate across engineering, product, and domain experts."
Growth Axis — Desirable Rather Than Required:
"SLM fine-tuning, including LoRA and QLoRA, instruction and format tuning, and distillation of a larger evaluator model into a smaller on-device model.
Latency and footprint optimization: INT8 and INT4 quantization, ONNX export and graph optimization, hardware-aware model selection, and profiling to reduce inference costs.
A pragmatic view of the boundary between configuration-driven adaptation and fine-tuning.
Building the data flywheel that supports this work, turning on-device session logs into evaluation sets and training data."
Bonus Qualifications:
"Speech recognition experience and comfort working downstream of noisy transcription.
Familiarity with LLM-as-a-judge evaluation.
Multilingual NLU; the system's data layer is already language-partitioned.
Industrial, field-service, or safety-critical product experience, for example in utilities, energy, or manufacturing.
GO familiarity, for integration with the on-device voice pipeline agent.
Exposure to MCP or agentic tooling.
Prior experience in a startup or a fast-paced team, building products from ground up."
Location & Type we already handled.
Now we need to output HTML fragment only.
We'll wrap sections in appropriate tags.
We'll output: