Stop applying to remote jobs that are already dead.
StillOpen is a remote job board that reads openings directly from each employer's own applicant tracking system (ATS), checks that each one is still listed, and closes it about 4 hours on average after the employer takes it down.

All listings

Scribe via Ashby

Senior AI Developer Experience Engineer

United States $160k–240k/yr senior
still open verified just now posted 2h ago seen just now
Apply at jobs.ashbyhq.com

This is the employer's own posting, not a copy on a job board.

What we know

Is it still open?

Confirmed still open

Last checked just now — checked against the employer's own applicant tracking system, which is the company answering directly.

We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.

Check this listing's status as JSON

How old is it?

Posted 2h ago

The date the source published, not the day we noticed it (2026-11-19). Last seen at its source just now.

Is it remote?

United States (Remote)

That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.

Who may apply?

United States

The description agrees: it names United States.

What the ad says
…Remote within the U.S., with two in-person team gatherings per year…

Pay

$160k–240k/yr

Published by the source in its own salary field. Shown in the posting's own currency and period; we never convert.

Skills named in the ad

AI AgentsAI ToolsCI/CDCursorDjangoGitHub ActionsKnowledge BaseObservabilityOpenTelemetryPythonSQLSentrySystems EngineeringTypeScript

Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.

Carried by 1 source

Our data indicates that more than 10% of this employer's remote-labelled postings mismatch their own job text.

The listing

About Scribe

Scribe is where exceptional people come to do the best work of their careers. More than 94% of the Fortune 500 use Scribe to own their specialized intelligence: the unique way their teams work, decide, and get things done. Our Specialized Intelligence platform automatically captures how work happens and turns it into a living asset for people and AI agents.

We're growing fast. Since our founding in 2019, we've reached 7 million users across 600,000 businesses. Based in San Francisco, we're a LinkedIn Top Startup, valued at over $1B, and backed by leading investors. Join us in our mission to transform how people work.

About the role

Scribe is hiring a Senior AI Developer Experience Engineer to own CI and test infrastructure, define observability standards, and build internal tooling. Our engineers already use Cursor, Codex, and Claude, with AI reviewers on every PR. You'll make that workflow faster, more dependable, and measurable, with clear human oversight.

This hands-on Senior IC role combines strong software and systems engineering with substantial autonomy and room to grow into Staff. You'll report to Rishabh Sharma and partner with Infrastructure, which owns continuous deployment and the production observability platform.

A note from your hiring manager

I lead AI-Native Engineering at Scribe, and DevEx is the team that makes every other engineer here faster and more confident: the path from an engineer's intent to production code they trust. That path runs through CI, feedback loops, shared standards, and the agentic workflows that increasingly write and review our code. Our engineers already work agent-first; the hard problem now is making the system underneath them fast, trustworthy, and measurable as traffic, headcount, and agent-generated code all grow by an order of magnitude. You'd own real parts of that system from day one, on a team that publishes its numbers and shuts down its own experiments when they don't work.

— Rishabh

Why This Role Matters

AI-assisted development depends on fast feedback, trustworthy validation, and useful context. When CI is slow or flaky, agents wait on it too, and they wait badly. When instrumentation is inconsistent, nobody can tell why something failed. This role improves software quality and developer experience while maintaining delivery velocity, using evidence from engineering workflows and developer feedback to decide what to improve and how to scale adoption.

You will tackle practical engineering challenges:

  • Workflow Reliability: How do we make CI and agent workflows fast, recoverable, and easy to diagnose?

  • Standards as Defaults: How do we turn shared engineering conventions into checks, libraries, and agent instructions, so the right way is the easiest way?

  • Evidence & Impact: How do we use telemetry and developer feedback to understand failures and evaluate whether our tools are actually useful?

What You'll Own

  • CI & Test Infrastructure. Own the speed and trustworthiness of CI on our main monorepo, from first push to deploy handoff: shard balancing, caching and fixtures, flake detection and quarantine, test discovery, and runner economics. Infrastructure owns continuous deployment; you're their most demanding partner.

  • Observability Standards. Define how Scribe instruments its software, and make the right way the default way: what goes to error tracking versus tracing, the context every event carries, and how errors join to traces. You turn these conventions into shared libraries, automated checks, and agent instructions so humans and agents follow them without having to remember, and you guard against cost and noise so the tooling stays within budget and useful. Owning teams run their own alerts and service targets; you make sure they're built on a consistent foundation.

  • Agent Workflows & Guardrails (shared with the DevEx team). Co-own our engineering bots (ReviewBot, BugTriage) and the deterministic checks that catch problems before human review. Make sure every system we run has a second operator, a runbook, and an adoption number reported alongside its quality number.

  • Developer Environment. Make the first ten minutes of any task cheap: local setup, worktrees, seeded databases, onboarding. When an engineer's environment breaks, you're who they want to hear from.

What Success Looks Like

Within 6 months:

  • CI: You've set baselines and delivered measured improvements: a sharply lower main-branch failure rate, faster required checks, and every test file either running in CI or explicitly waived.

  • Observability standards: A written standard is in place and enforced in code, not just documented. Errors join to traces, events carry consistent context, and error-tracking spend alerts before it hits a cap.

  • Shared ownership: Every system DevEx operates has at least two people who can run it.

Within 12 months:

  • Developer experience: Engineers rate build-and-test as a strength, not the weakest part of their workflow.

  • Standards by default: New services and agent-written code meet the observability standard by default, and compliance is measurable per team, never per person.

  • Evidence-driven delivery: You've taken at least one project from a written proposal with pre-set success and stopping criteria to a published result, whether it shipped or was shut down. Delivery velocity held steady or improved throughout.

The Ideal Profile

You combine strong engineering judgment with a practical understanding of how engineers work. You build useful tools, evaluate them with evidence, and help teams adopt and maintain them.

  • Earn Adoption: Understand engineers' needs and build tools teams choose to use because they improve daily work.

  • Work from Evidence: Establish baselines, combine operational data with developer feedback, and change direction when results warrant it. Define and defend useful metrics.

  • Measure Systems Responsibly: Use DevEx metrics to improve tooling, workflows, and team outcomes, without scoring or ranking individual engineers.

  • Experiment with Clear Boundaries: Define success measures and stopping criteria before trials, and be willing to stop approaches that do not deliver value.

  • Standards as Code: You'd rather ship a check, a wrapper, or a default than a policy doc, and you measure whether conventions are actually followed.

  • Internal Product Judgment: Take tooling from design through rollout, and turn recurring needs into documentation, templates, and reusable agent skills teams can maintain.

  • Build for Shared Ownership: Create understandable, documented systems that other engineers can operate, maintain, and improve.

  • Enjoy the Support Side: You like helping engineers get unstuck, and you treat recurring support requests as product signals rather than interruptions.

Must-Have Skills

  • Build & Test Systems Depth: Deep, hands-on experience owning test, lint, build, or CI infrastructure in a substantial codebase, in at least one ecosystem (TypeScript, Go, Python/Django, or similar), and enough systems judgment to learn the others. You can diagnose slow pipelines, flaky tests, and broken development environments.

  • Systems Engineering & Instrumentation: You design, build, and maintain dependable internal tools and integrations, and have hands-on experience instrumenting production systems with error tracking, tracing, and logs (e.g., Sentry, Honeycomb, OpenTelemetry), deep enough to set conventions others follow.

  • Practical AI Engineering: You use agentic coding tools daily and critically, and have built or adapted at least one AI development workflow that other engineers adopted, including context management, validation, and failure handling.

  • Evidence & Measurement: You can define a metric, defend it under pushback, and tell when it's being gamed. You're comfortable with SQL and analyzing operational data.

Bonus

  • Experience with Temporal or similar workflow orchestration engines for AI/agentic pipelines.

  • Deep experience with GitHub Actions internals or optimizing large test suites through sharding, caching, and test isolation.

  • Experience customizing agent harnesses or building reusable integrations for AI development workflows.

  • Experience designing developer experience measurement frameworks that combine operational data with developer feedback.

  • Experience in Series B–D startups or core platform/infrastructure teams in growing technology companies.

How We Interview

  • Our loop is a set of work samples, not puzzles.

  • In the agentic round and the take-home, you'll use AI tools, and we look at how you delegate, verify, and explain.

  • One round is a short paid take-home: a maintainer-facing analysis of a public repository, which you then defend live.

  • Every round is scored against the same five areas: engineering systems depth, agentic systems judgment, evidence and measurement, developer empathy and adoption, and platform stewardship.

Compensation & location

Remote within the U.S., with two in-person team gatherings per year.

All full-time employees receive equity in Scribe. Final offers depend on experience and scope.

Benefits

  • Healthcare Coverage – Comprehensive health, dental, and vision plans, including two $0/month medical plan options for employees

  • Equity – Ownership in what we're building

  • 401(k) Plan – through Vestwell

  • Flex Benefit – $500/year for home office equipment, productivity tools, learning & development or fitness/wellness

  • Commuter Benefits – $100/month for SF based employees

  • PTO – Flexible paid time off and company holidays

  • Parental Leave – Paid leave to support growing families

  • Wellness & Family Support – Free Talkspace membership, One Medical access (location-dependent), and Kindbody discounts for family planning

At Scribe, we celebrate our differences and are committed to creating a workplace where all employees feel supported and empowered to do their best work. Scribe is proud to be an Equal Opportunity Employer.

Our Worker Privacy notice can be found here.

Apply at jobs.ashbyhq.com