> Markdown version of [/jobs/ext/3015391-senior-developer-experience-engineer](https://www.wearedevelopers.com/jobs/ext/3015391-senior-developer-experience-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). --- # Senior Developer Experience Engineer - **Company:** Savvy Wealth - **Location:** New York, NY, United States - **Experience:** Expert - **Salary:** $180,000.0 - $235,000.0 - **Contract:** Permanent contract - **Skills:** Code Review, System Configuration, Cursor (Graphical User Interface Elements), Software Debugging, Programming Tools, Software Construction, Software Engineering - **Published:** September 20, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=63a58c9ec89c9afc ## About the Role * Exceptional with coding agents: You use Claude Code, Codex, Cursor, or similar tools for substantial work and can show how you decompose tasks, manage context, choose models, inspect failures, and consistently produce maintainable software. Faster output alone is not the bar. * Internal tools with real users: You have built developer tooling or a platform that engineers beyond your immediate team relied on. You learned from their behavior and support burden, not only from what they said they wanted. * CI or large-codebase experience: You have made a meaningful improvement to CI, testing, repository workflows, or developer productivity in a substantial, long-lived codebase. * Product judgment for internal systems: You can interview developers, separate symptoms from root causes, turn evidence into a roadmap, and say no to attractive work that will not improve the system. * Strong software engineering: You have built and operated substantial production software. We are open on language and framework, but you must be able to move from diagnosis to a durable implementation yourself. * Evaluation over intuition: You know that agent behavior is nondeterministic and changing quickly. You compare prompts, context, tools, models, and workflows against representative tasks rather than declaring success from a demo. * Cross-team influence: You can set standards and change defaults across teams without becoming a gatekeeper. You explain the evidence, earn trust, and remain accountable for the experience you create. * Pragmatic range: You are comfortable moving between platform code, repository conventions, evaluation data, developer interviews, documentation, and hands-on enablement. This is not a prompt-writing, DevRel, or framework-only role. NICE TO HAVE * Experience building cloud or remote development environments, coding-agent control planes, or secure execution sandboxes. * Experience building or operating an agentic code review system. * Experience designing agent tools, skills, context systems, memory, orchestration, or model-routing infrastructure. * Experience using DORA, SPACE, or similar frameworks without reducing developer productivity to a single metric. * Experience in financial services or another security- and compliance-sensitive environment. ## Description Savvy is hiring our first dedicated developer experience engineer. Coding agents are already part of how our engineers work, but adoption has moved faster than our ability to make their output consistently good. Wrong code and weak architectural decisions still create review burden. We are hiring someone to treat that as an engineering problem, not solve it with a longer prompt. You will own how developers across EPD interact with coding agents and with the systems around them. That includes the codebase itself, our internal skills and instructions, cloud coding workflows, agentic code review, CI, local development, testing, debugging, and delivery. You will have substantial autonomy to make cross-cutting decisions, change defaults, and set standards across the organization. This is a hands-on platform engineering role. Most of your time will be spent building software and improving the environment in which developers and agents work. You will also talk directly with engineers, study where time and quality are being lost, test your ideas against real work, and help teams adopt better ways of operating. You will join our infrastructure and harness team and partner closely with infrastructure, security, data, and product engineers., * Own developer and agent experience: Set the roadmap for how our engineers and coding agents navigate the codebase, use internal tools, run tests, review changes, and ship software. * Build the cloud coding experience: Build the developer-facing layer around our existing compute foundations, including task intake, environment setup, context, tools, permissions, observability, review, and delivery. * Improve agent output at the source: Change repository structure, interfaces, documentation, instructions, and feedback loops so agents produce correct code and sound architecture more consistently. * Engineer context deliberately: Design what agents receive up front, discover progressively, persist, compact, hand off, or discard. Choose models and reasoning effort based on evidence from the job, not habit. * Own our internal skills system: Raise the quality of our shared skills and instructions through clear contribution standards, evaluation, discoverability, progressive disclosure, maintenance, and pruning. * Fix everyday developer friction: Improve CI speed and reliability, local setup, testing, debugging, deploy workflows, and the other bottlenecks that cost engineers time. * Measure what works: Combine developer research and satisfaction data with DORA or SPACE measures and task-level agent evaluations. Inspect traces, establish baselines, and test whether changes improve correctness, reviewability, cost, latency, and human intervention. * Drive adoption: Work directly with engineers, teach effective practices, and turn successful experiments into defaults. When the root problem is the codebase or engineering process, make that case and help fix it. * Partner on safe autonomy: Work with our infrastructure and security engineers on sandboxing, credentials, approvals, auditability, and the controls needed to give cloud agents useful access without giving them unlimited access. ## Related Videos - [Using AI Without Losing Your Skills](https://www.wearedevelopers.com/videos/2045-using-ai-without-losing-your-skills) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [AI Pair Programming with GitHub Copilot at SAP: Looking Back, Looking Forward!](https://www.wearedevelopers.com/videos/1546-ai-pair-programming-with-github-copilot-at-sap-looking-back-looking-forward) - [You don't need to write the code. You need to become a verification architect and prove it's correct](https://www.wearedevelopers.com/videos/100023-you-don-t-need-to-write-the-code-you-need-to-become-a-verification-architect-and-prove-it-s-correct) - [Build a CI/CD pipeline to automate code reviews and ensure code quality](https://www.wearedevelopers.com/videos/349-build-a-ci-cd-pipeline-to-automate-code-reviews-and-ensure-code-quality) - [Developer Relations in the World of Agents - Michelle Duke](https://www.wearedevelopers.com/videos/1898-developer-relations-in-the-world-of-agents-michelle-duke) ## Related Articles - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [9 Claude Code Skills to Speed Up Your Workflow](https://www.wearedevelopers.com/magazine/740-9-claude-code-skills-to-speed-up-your-workflow) - [Dev Digest 176: Expensive Agents, Taking Over VSCode and Safer Vibe Coding](https://www.wearedevelopers.com/magazine/603-dev-digest-176-expensive-agents-taking-over-vscode-and-safer-vibe-coding) - [What’s the Difference between a Junior, Mid, and Senior Developer?](https://www.wearedevelopers.com/magazine/238-what-s-the-difference-between-a-junior-mid-and-senior-developer) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers)