Back to jobs

Member of Technical Staff, AI Engineer

Parameter HQ · San Francisco, California, United States

Live, first seen by us 46 days ago
Pay
Pay not listed
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll work on

Full posting
  • You'll build the agent systems that do the actual hacking.

  • Design and ship agent workflows in LangGraph and Temporal that plan, execute, and verify multi-step exploitation chains

  • Build the tool layer the agents operate through: HTTP clients, auth handling, browser control, cloud enumeration, payload generation

From the employer’s posting
We are not a theoretical security company. Our team has responsibly disclosed real, high-severity vulnerabilities to well-known technology companies, and our findings are the front door to most of our customer relationships. You'll build the agent systems that do the actual hacking. That means designing the reasoning loops, tool interfaces, and memory architecture that let an LLM behave like a competent offensive security researcher rather than a fuzzer with good manners. The title points at where you'll spend most of your time. Expect the rest of the week to go wherever the work is: agent systems one day, the product the next, a customer call or a report that has to go out after that. We are small enough that everyone works across every product, and we hire people who want that.
What you'll do Design and ship agent workflows in LangGraph and Temporal that plan, execute, and verify multi-step exploitation chains Build the tool layer the agents operate through: HTTP clients, auth handling, browser control, cloud enumeration, payload generation
Design and ship agent workflows in LangGraph and Temporal that plan, execute, and verify multi-step exploitation chains Build the tool layer the agents operate through: HTTP clients, auth handling, browser control, cloud enumeration, payload generation Own the eval loop. We use Braintrust and Langfuse. You'll define what “good” means for agent runs and make the number go up

Before you apply

Work authorization
Must already have the right to work in the USYou must be authorized to work in the US
Apply at Parameter ai

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 7, 202646 days ago
Recorded sightings
29
Last seen by us
Nov 21, 2026
Employer says posted
Oct 5, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 46

Up longer than most. Similar jobs usually come down between day 1 and day 15.

From 1,368 similar postings that came down. Coming down is not always a hire.

Parameter ai is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • TypeScript
  • AWS
  • GCP
Where the posting names them
- 3+ years of software engineering, with at least one year building production LLM systems (not just prototypes or demos) - Strong TypeScript. Comfortable with async, distributed systems, and long-running workflow orchestration - Real intuition for context engineering, tool design, and why agents fail in the wild
Stack TypeScript · LangGraph · Temporal · GCP · AWS Bedrock · Anthropic API · Langfuse · Braintrust · GitHub Actions · Linear · Graphite We move quickly. Our target is an offer within two weeks of first contact. Small team, high trust, extremely fast. If you want to see your work in front of customers within days, this is that.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

Full time • San Francisco, CA • $180K – $240K • 2 openings

Parameter builds AI agents that do offensive security work. Our agents run autonomous penetration tests against production applications and cloud environments, finding IDORs, broken access control, XSS, and infrastructure misconfigurations that scanners miss and that human pentest firms only look for once or twice a year.

We are not a theoretical security company. Our team has responsibly disclosed real, high-severity vulnerabilities to well-known technology companies, and our findings are the front door to most of our customer relationships.

You'll build the agent systems that do the actual hacking. That means designing the reasoning loops, tool interfaces, and memory architecture that let an LLM behave like a competent offensive security researcher rather than a fuzzer with good manners.

The title points at where you'll spend most of your time. Expect the rest of the week to go wherever the work is: agent systems one day, the product the next, a customer call or a report that has to go out after that. We are small enough that everyone works across every product, and we hire people who want that.

What you'll do

  • Design and ship agent workflows in LangGraph and Temporal that plan, execute, and verify multi-step exploitation chains

  • Build the tool layer the agents operate through: HTTP clients, auth handling, browser control, cloud enumeration, payload generation

  • Own the eval loop. We use Braintrust and Langfuse. You'll define what “good” means for agent runs and make the number go up

  • Reduce false positives, which is the single hardest problem in this space and the thing customers care most about

  • Manage inference cost and latency at scale, including prompt caching, context strategy, and model selection across Claude and Bedrock

What we're looking for

  • 3+ years of software engineering, with at least one year building production LLM systems (not just prototypes or demos)

  • Strong TypeScript. Comfortable with async, distributed systems, and long-running workflow orchestration

  • Real intuition for context engineering, tool design, and why agents fail in the wild

  • You measure things. You've built or maintained an eval harness and know why offline metrics diverge from production behavior

  • Bonus: security background, CTF experience, bug bounty history, or a track record of breaking things you were not supposed to break

Interview process

  • Intro call with a founder (30 minutes)

  • Technical deep dive on your past work (60 minutes)

  • Paid work trial or take-home, scoped to roughly one day

  • Onsite in San Francisco with the team

  • References and offer

Stack

TypeScript · LangGraph · Temporal · GCP · AWS Bedrock · Anthropic API · Langfuse · Braintrust · GitHub Actions · Linear · Graphite

We move quickly. Our target is an offer within two weeks of first contact. Small team, high trust, extremely fast. If you want to see your work in front of customers within days, this is that.

This role is onsite in San Francisco. You must be authorized to work in the US; we are not able to sponsor visas at this time.

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

San Francisco, California, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization
We move quickly. Our target is an offer within two weeks of first contact. Small team, high trust, extremely fast. If you want to see your work in front of customers within days, this is that. This role is onsite in San Francisco. You must be authorized to work in the US; we are not able to sponsor visas at this time.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.