Senior / Staff AI Model Engineer
for headings. Use - for lists. Use
for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Include sections only if posting has real specific content.
We need to parse the posting.
Job description: "Back to jobs New Senior / Staff AI Model Engineer Remote Clear Street is modernizing the brokerage ecosystem..." etc.
We need sections: About the role (maybe from "The Role" paragraph). Responsibilities (list of duties). Requirements (list). Qualifications maybe same as Requirements? The posting includes "Requirements" and "Bonus Experience". Also "Tech Stack". Also "We Offer" includes salary, benefits.
We need to decide sections: About the role (intro). Responsibilities (the bullet list under "The Role"). Requirements (the list under "Requirements"). Bonus maybe part of Requirements or separate? Could be "Preferred Qualifications". But we can include as part of Requirements or separate "Preferred Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Qualifications if there is distinct content. The posting includes "Tech Stack" which could be Skills. Also "Bonus Experience" could be Qualifications.
Pay: The posting includes "We Offer The Base Salary Range for this role is $200,000 - $500,000." So we have Pay section.
Benefits: The posting includes "At Clear Street, we offer competitive compensation packages, company equity, 401k matching, gender neutral parental leave, and full medical, dental and vision insurance. In-office benefits include lunch stipends, fully stocked kitchens, happy hours, a great location, and amazing views." So Benefits.
Schedule: Not mentioned (remote). No explicit schedule. So we should not create Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info. Let's extract.
First, About the role: The paragraph after "The Role". It says: "You will own the reliability and quality bar for an AI copilot embedded in an trading platform used by sophisticated investorsYou will design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement)You will develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corporaYou will build automated quality gates and regression workflows that block releases when key metrics degradeYou will partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behaviorYou will own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performanceYou will design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processesYou will develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users"
We need to split into sentences for readability. We'll put in
.
Responsibilities: Could be the same as above? Actually the "The Role" paragraph enumerates responsibilities. So we can treat that as Responsibilities list. Could also separate "About the role" as a brief overview. But we have limited distinct content. Perhaps we can make About the role a short summary: "Senior / Staff AI Model Engineer responsible for ensuring reliability and quality of an AI copilot embedded in a trading platform." Then Responsibilities list the bullet points.
But we must not invent or summarize away detail. We can keep the responsibilities as list items directly from the paragraph. That preserves detail.
Thus:
About the role
Senior / Staff AI Model Engineer responsible for owning the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors.
Then Responsibilities: list each duty.
We need to extract each duty as separate bullet.
From the paragraph, we can split by "You will". Let's list:
- own the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors
- design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement)
- develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corpora
- build automated quality gates and regression workflows that block releases when key metrics degrade
- partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behavior
- own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performance
- design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processes
- develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users
That's 8 bullets.
Now Requirements: The section "Requirements" includes bullet-like sentences.
Let's extract:
- At least Eight (8) years of experience shipping production software; strong proficiency with any programming language
- Strong knowledge of computer science fundamentals, testing methodology, and systems design
- Experience building evaluation frameworks, test harnesses, and benchmark suites for complex systems (LLMs/agents/search/retrieval/ranking/recommenders)
- Experience running model improvement cycles: dataset curation, labeling/QA, offline experimentation, and deploying changes with measurable impact on benchmarks
- Ability to define metrics, build measurement pipelines, and drive engineering/product decisions from data
- Comfort working across the stack: debugging model/tooling failures, instrumenting services, and partnering with frontend/product on UX patterns that improve safety and trust
- High degree of self-motivation and willingness to jump into unfamiliar areas to solve problems
That's the list.
Now Bonus Experience: Could be under "Preferred Qualifications" or "Qualifications". We'll create a section "Qualifications" for bonus.
Bullet list:
- Experience with fine-tuning, preference optimization, distillation, or prompt/compiler-style techniques for improving tool-use reliability
- Experience creating domain-specific benchmarks and adversarial suites (e.g., “known-bad” scenarios) for high-stakes applications
- Deep experience with trading across asset classes, margin types, etc.
- Experience with Rust and performance-sensitive services
- Experience designing incident response and SLOs for ML/AI systems
Now Skills: Could be Tech Stack: Rust, TypeScript, Postgres, React (Web), React Native (Mobile), observability/telemetry tooling, LLM APIs + model serving, eval/training pipelines.
We'll put under Skills as list.
Now Pay: Base Salary Range $200,000 - $500,000. Also note that it's base salary only, does not include bonuses or equity. We'll include that.
Now Benefits: list as per text.
Now we need to ensure we don't include boilerplate like "Create a Job Alert", application instructions, EEO, etc. We removed those.
Now output HTML fragment only.
We'll structure:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
Pay
...
Benefits
...
We should not include Schedule.
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive info: Did we miss any? The "Tech Stack" includes also "observability/telemetry tooling, LLM APIs + model serving, eval/training pipelines". We included.
The "We Offer" also mentions "competitive compensation packages, company equity, 401k matching, gender neutral parental leave, and full medical, dental and vision insurance. In-office benefits include lunch stipends, fully stocked kitchens, happy hours, a great location, and amazing views." We captured as benefits list.
Also note "Our top priority is our people..." etc. That's fluff; maybe we can omit as it's not specific substantive? It's generic culture statement. Might be considered boilerplate? It's not required to preserve; but it's substantive? It's about culture. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The culture statements could be considered substantive but they are generic. However they are not boilerplate like EEO. Might be okay to keep? But we have no section for culture; we could add a under Benefits or separate section "Culture". But not in allowed headings. We could incorporate into Benefits as a paragraph. But the instruction says only use those headings; we can still add
outside headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other elements, but we should follow the pattern. Probably better to keep only those sections. The culture statement is not essential to job description; we can omit as it's fluff. It's not required to preserve. I'd omit.
Also "We believe that modern workplaces succeed..." etc. Omit.
Now ensure we didn't include any navigation or application instructions.
Now produce final HTML.
Let's craft.
Be careful to escape any HTML inside content? Not needed.
We'll output:
About the role
Senior / Staff AI Model Engineer responsible for owning the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors.
Responsibilities
- own the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors
- design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement)
- develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corpora
- build automated quality gates and regression workflows that block releases when key metrics degrade
- partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behavior
- own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performance
- design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processes
- develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users
Requirements
- At least Eight (8) years of experience shipping production software; strong proficiency with any programming language
- Strong knowledge of computer science fundamentals, testing methodology, and systems design
- Experience building evaluation frameworks, test harnesses, and benchmark suites for complex systems (LLMs/
for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Include sections only if posting has real specific content. We need to parse the posting. Job description: "Back to jobs New Senior / Staff AI Model Engineer Remote Clear Street is modernizing the brokerage ecosystem..." etc. We need sections: About the role (maybe from "The Role" paragraph). Responsibilities (list of duties). Requirements (list). Qualifications maybe same as Requirements? The posting includes "Requirements" and "Bonus Experience". Also "Tech Stack". Also "We Offer" includes salary, benefits. We need to decide sections: About the role (intro). Responsibilities (the bullet list under "The Role"). Requirements (the list under "Requirements"). Bonus maybe part of Requirements or separate? Could be "Preferred Qualifications". But we can include as part of Requirements or separate "Preferred Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Qualifications if there is distinct content. The posting includes "Tech Stack" which could be Skills. Also "Bonus Experience" could be Qualifications. Pay: The posting includes "We Offer The Base Salary Range for this role is $200,000 - $500,000." So we have Pay section. Benefits: The posting includes "At Clear Street, we offer competitive compensation packages, company equity, 401k matching, gender neutral parental leave, and full medical, dental and vision insurance. In-office benefits include lunch stipends, fully stocked kitchens, happy hours, a great location, and amazing views." So Benefits. Schedule: Not mentioned (remote). No explicit schedule. So we should not create Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract. First, About the role: The paragraph after "The Role". It says: "You will own the reliability and quality bar for an AI copilot embedded in an trading platform used by sophisticated investorsYou will design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement)You will develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corporaYou will build automated quality gates and regression workflows that block releases when key metrics degradeYou will partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behaviorYou will own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performanceYou will design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processesYou will develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users" We need to split into sentences for readability. We'll put in
. Responsibilities: Could be the same as above? Actually the "The Role" paragraph enumerates responsibilities. So we can treat that as Responsibilities list. Could also separate "About the role" as a brief overview. But we have limited distinct content. Perhaps we can make About the role a short summary: "Senior / Staff AI Model Engineer responsible for ensuring reliability and quality of an AI copilot embedded in a trading platform." Then Responsibilities list the bullet points. But we must not invent or summarize away detail. We can keep the responsibilities as list items directly from the paragraph. That preserves detail. Thus:
About the role
Senior / Staff AI Model Engineer responsible for owning the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors.
Then Responsibilities: list each duty. We need to extract each duty as separate bullet. From the paragraph, we can split by "You will". Let's list: - own the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors - design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement) - develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corpora - build automated quality gates and regression workflows that block releases when key metrics degrade - partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behavior - own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performance - design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processes - develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users That's 8 bullets. Now Requirements: The section "Requirements" includes bullet-like sentences. Let's extract: - At least Eight (8) years of experience shipping production software; strong proficiency with any programming language - Strong knowledge of computer science fundamentals, testing methodology, and systems design - Experience building evaluation frameworks, test harnesses, and benchmark suites for complex systems (LLMs/agents/search/retrieval/ranking/recommenders) - Experience running model improvement cycles: dataset curation, labeling/QA, offline experimentation, and deploying changes with measurable impact on benchmarks - Ability to define metrics, build measurement pipelines, and drive engineering/product decisions from data - Comfort working across the stack: debugging model/tooling failures, instrumenting services, and partnering with frontend/product on UX patterns that improve safety and trust - High degree of self-motivation and willingness to jump into unfamiliar areas to solve problems That's the list. Now Bonus Experience: Could be under "Preferred Qualifications" or "Qualifications". We'll create a section "Qualifications" for bonus. Bullet list: - Experience with fine-tuning, preference optimization, distillation, or prompt/compiler-style techniques for improving tool-use reliability - Experience creating domain-specific benchmarks and adversarial suites (e.g., “known-bad” scenarios) for high-stakes applications - Deep experience with trading across asset classes, margin types, etc. - Experience with Rust and performance-sensitive services - Experience designing incident response and SLOs for ML/AI systems Now Skills: Could be Tech Stack: Rust, TypeScript, Postgres, React (Web), React Native (Mobile), observability/telemetry tooling, LLM APIs + model serving, eval/training pipelines. We'll put under Skills as list. Now Pay: Base Salary Range $200,000 - $500,000. Also note that it's base salary only, does not include bonuses or equity. We'll include that. Now Benefits: list as per text. Now we need to ensure we don't include boilerplate like "Create a Job Alert", application instructions, EEO, etc. We removed those. Now output HTML fragment only. We'll structure:About the role
...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Pay
...
Benefits
- ...
under Benefits or separate section "Culture". But not in allowed headings. We could incorporate into Benefits as a paragraph. But the instruction says only use those headings; we can still add
outside headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other elements, but we should follow the pattern. Probably better to keep only those sections. The culture statement is not essential to job description; we can omit as it's fluff. It's not required to preserve. I'd omit.
Also "We believe that modern workplaces succeed..." etc. Omit.
Now ensure we didn't include any navigation or application instructions.
Now produce final HTML.
Let's craft.
Be careful to escape any HTML inside content? Not needed.
We'll output:
About the role
Senior / Staff AI Model Engineer responsible for owning the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors.
Responsibilities
- own the reliability and quality bar for an AI copilot embedded in a trading platform used by sophisticated investors
- design and build evaluation systems that measure correctness, safety, latency, and regression risk across market analysis, portfolio/risk reasoning, and trading workflows (including order placement)
- develop and maintain benchmarks: curated “golden sets,” scenario suites, stress/adversarial cases, and continuously refreshed market/regime-based test corpora
- build automated quality gates and regression workflows that block releases when key metrics degrade
- partner with engineering and product to define safe tool/action contracts (deterministic previews, confirmations, auditability) and ensure predictable assistant behavior
- own model improvement loops tied to evals: data collection/labeling strategies, error taxonomy, prompt/tooling changes, and when appropriate, fine-tuning or preference optimization to measurably improve benchmark performance
- design and operate monitoring + incident response for AI: telemetry, alerting, RCA, and “fix-forward” processes
- develop a deep understanding of trading concepts (margin, shorting, portfolio margin, risk, execution) and how to express them accurately and understandably to users
Requirements
- At least Eight (8) years of experience shipping production software; strong proficiency with any programming language
- Strong knowledge of computer science fundamentals, testing methodology, and systems design
- Experience building evaluation frameworks, test harnesses, and benchmark suites for complex systems (LLMs/