> Markdown version of [/jobs/ext/2522479-full-stack-engineer](https://www.wearedevelopers.com/jobs/ext/2522479-full-stack-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Full-Stack Engineer - **Company:** David Joseph & Company - **Location:** San Francisco, CA, United States - **Experience:** Experienced - **Salary:** $200,000.0 - $300,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Operational Databases, Large Language Models, Backend, Data Layers - **Published:** August 9, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=ff0bcb6576eb5ca6 ## About the Role * 3-7 years of full-stack engineering experience, comfortable owning systems from the data layer through the UI * Hands-on experience building with LLMs or AI agents (or a clear, demonstrated drive to ramp fast) * A track record of shipping and scaling production systems end to end * Comfortable working directly with customers to understand needs and solve real problems (~30% of the role) * Strong problem-solving in fast-moving, ambiguous environments * Clear, direct, persuasive communication across technical and non-technical audiences * Based in San Francisco or open to relocating; in-office 5 days a week, * Prior work on evals, observability, or agent behavior-monitoring products * Strong engineering pedigree from a respected product company; top-tier infrastructure experience is a bonus * Prior forward-deployed or solutions engineering experience * Early-stage / 0-to-1 startup experience as an early hire * A technical edge beyond delivery - coding competitions, research, or similar * Founder background or a clear founder-to-be trajectory * Full-stack comfort with real backend and infrastructure depth ## Description This is a genuine full-ownership product-engineering role, not spec implementation. You'll talk to customers, decide what to build, build it, and iterate until it's great - across the entire stack, from the data layer to the UI. Expect to work on agent-investigation interfaces, verification and evaluation platforms, and a developer SDK. About 30% of the role is customer-facing. What you'll be doing * Build interfaces that make large-scale, parallel agent investigations legible - turning thousands of production traces and a wide range of failure signals into a single actionable answer. * Build the platform for verifying agent changes: simulated environments for stateful evals, trajectory replay, and monitors for unintended behavior. * Make long, multi-step reasoning trajectories understandable in minutes. * Own the improvement loop end to end, turning production data into datasets, judges, and regression checks. * Build and maintain the SDK and a terminal-first developer experience. * Own core platform infrastructure: workspaces, permissions, billing, usage, and limits. Tech stack: Full-stack (data layer through UI), SDK development, terminal-first tooling, agent/LLM infrastructure. ## Related Videos - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Why Your AI Agent Keeps Hallucinating Your Data: Building Deterministic Context Layers](https://www.wearedevelopers.com/videos/2055-why-your-ai-agent-keeps-hallucinating-your-data-building-deterministic-context-layers) - [Databases on Kubernetes: Why you should care](https://www.wearedevelopers.com/videos/74-databases-on-kubernetes-why-you-should-care) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) - [You are not an AI developer](https://www.wearedevelopers.com/videos/1148-you-are-not-an-ai-developer) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [What Are Large Language Models?](https://www.wearedevelopers.com/magazine/304-what-are-large-language-models) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)