Back to jobs

Applied AI Engineer

San Francisco · Seattle, WA, USA

Actively hiring, first seen by us 23 hours ago
Pay
Pay not listed
Work setting
Hybrid — work setting source
Location type: Hybrid
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
  • Own AI features end-to-end, from defining correctness with users to production iteration

  • Turn permitting documents and city regulations into structured, reliable outputs

  • Build evaluation and observability to measure LLM quality and regressions

  • Direct and review AI agent-driven implementation work while owning quality

  • Mentor engineers and set standards for building with LLMs

From the employer’s posting
Own AI-powered features end-to-end—from talking to users and defining what “correct” means for a permitting workflow
Turn unstructured permitting documents, city regulations, and jurisdiction workflows into structured, reliable outputs
Build the evaluation and observability foundation that lets us ship LLM-powered features with confidence
Build with AI agents as a daily practice—directing, reviewing, and shipping agent-driven work at high velocity
Raise the bar for the engineers around you in how they build with LLMs, through design review, mentorship

Before you apply

Sponsorship
Visa sponsorship not confirmed — sponsorship source
Will you now or in the future, require Visa sponsorship to work in the US?
From the employer’s application form

What you’ll bring

All qualifications

Core experience

  • 4+ years of software engineering experience, with a substantial portion building production LLM or ML systems
  • Experience with document understanding at scale—OCR, layout-aware parsing, or vision-language models over scanned PDFs, drawings, or forms
  • Experience designing evals and otherwise making LLM-powered features reliable in production
  • Experience fine-tuning models or building data pipelines to produce training and eval sets from real-world usage
  • Ability to architect durable systems while making pragmatic tradeoffs
  • Experience in construction tech, govtech, proptech, or another domain where the hard part is messy real-world documents and processes
Qualification wording
4+ years of software engineering experience, with a substantial portion building production LLM or ML systems
Experience with document understanding at scale—OCR, layout-aware parsing, or vision-language models over scanned PDFs, drawings, or forms
Experience designing evals and otherwise making LLM-powered features reliable in production
Experience fine-tuning models or building data pipelines to produce training and eval sets from real-world usage
Ability to architect durable systems while making pragmatic tradeoffs
Experience in construction tech, govtech, proptech, or another domain where the hard part is messy real-world documents and processes

About Pulley

Pulley’s mission is to help America’s most important industries break ground faster.

In the employer’s words · Read in context · Company website ↗

Apply at Pulley

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 2026today
Recorded sightings
2
Last seen by us
Nov 19, 2026
Employer says posted
Sep 21, 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 0

Early. Similar jobs usually come down between day 2 and day 14.

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

Pulley 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
  • React
  • GCP
Where the posting names them
- Experience in construction tech, govtech, proptech, or another domain where the hard part is messy real-world documents and processes - Experience with modern full-stack development—we use TypeScript, React, and Google Cloud—and an appetite for working in the application code that puts AI features in front of users - Startup experience at the stage where you helped build the team, not just the product

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 ↗

About Pulley

Pulley’s mission is to help America’s most important industries break ground faster. We’re building the development system that drives projects from concept to construction, so businesses can deliver projects sooner and bring critical infrastructure online faster.

Trusted by Amazon, Starbucks, JLL, Meta, and other leading enterprises, Pulley has supported more than $21 billion in construction projects across all 50 states. Our work spans national retail rollouts, complex data center builds, major logistics facilities, and other development where every week of delay matters.

Our AI-native permitting service combines AI agents, regulatory intelligence, and a nationwide team of licensed experts to get commercial projects approved up to 70% faster. Now, Pulley is building towards a world where every step of development can happen in a matter of days.

Backed by investors including CRV, Susa Ventures, and Fifth Wall, we’re bringing together exceptional people who love solving hard problems to make the path to construction faster and more predictable.

What You'll Do

In this role, you will build the intelligence behind the product that gets stuff built. Permitting runs on messy inputs—scanned plan sets, jurisdiction code, reviewer comments, application forms that differ in every city—and turning that into something fast, structured, and trustworthy is the core technical problem at Pulley. As a senior-level AI engineer, you will:

  • Own AI-powered features end-to-end—from talking to users and defining what “correct” means for a permitting workflow, through prompt and pipeline design, evals, deployment, and iteration in production

  • Turn unstructured permitting documents, city regulations, and jurisdiction workflows into structured, reliable outputs—extraction, classification, retrieval, and agentic workflows over documents that were never designed to be machine-readable

  • Build the evaluation and observability foundation that lets us ship LLM-powered features with confidence: define ground truth, measure quality and regressions, and know when a model change is actually an improvement

  • Build with AI agents as a daily practice—directing, reviewing, and shipping agent-driven work at high velocity while owning the quality bar

  • Make technical and product decisions that have direct impact on our customers and their projects

  • Raise the bar for the engineers around you in how they build with LLMs, through design review, mentorship, and the standards you set in your own work

Who You Are

  • You thrive in ambiguity—you’d rather define the right problem than execute a spec, and you’re energized rather than paralyzed when the path isn’t laid out

  • You’re product-minded: you care whether the thing you built actually solved the customer’s problem, and you’ll talk to users to find out

  • You’re rigorous about what “working” means—you don’t trust a demo, you trust an eval, and you build the measurement before you build the feature

  • You have strong opinions about quality and velocity and don’t treat them as a tradeoff—you look for the tools, abstractions, and processes that buy both

  • You default to ownership: when something is broken or missing, your instinct is to fix it, not to file it as someone else’s problem

Need to Have

  • 4+ years of software engineering experience, with a substantial portion building production LLM or ML systems

  • Track record of owning an LLM-powered product surface end-to-end: requirements through production, including the unglamorous parts—data quality, eval design, cost and latency, failure handling

  • Deep hands-on experience with large language models in production—prompting, retrieval-augmented generation, structured extraction, tool use and agentic workflows, and knowing when each is the wrong tool

  • Experience designing evals and otherwise making LLM-powered features reliable in production

  • Real experience building with AI coding agents—not just autocomplete; you’ve shipped work where agents did substantial implementation under your direction

  • Ability to architect durable systems while making pragmatic tradeoffs

  • Based in the San Francisco Bay Area and willing to work in person 4 days a week

Nice to Have

  • Experience with document understanding at scale—OCR, layout-aware parsing, or vision-language models over scanned PDFs, drawings, or forms

  • Experience fine-tuning models or building data pipelines to produce training and eval sets from real-world usage

  • Experience in construction tech, govtech, proptech, or another domain where the hard part is messy real-world documents and processes

  • Experience with modern full-stack development—we use TypeScript, React, and Google Cloud—and an appetite for working in the application code that puts AI features in front of users

  • Startup experience at the stage where you helped build the team, not just the product

  • Experience mentoring engineers or leading technical direction across teams

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

Seattle, WA, USA

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

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

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.