Staff Software Engineer

Work Truck Solutions•Chico, CA

16d•$180,000 - $230,000•Remote

About The Position

Work Truck Solutions is the operating system for the commercial vehicle industry. We are the only platform that connects the entire ecosystem: OEMs, upfitters, dealerships, and fleet buyers. By digitizing complex inventory data (chassis + upfits) and streamlining the supply chain, we don’t just help dealers sell trucks; we ensure American businesses get the mission-critical vehicles they need to work. We are a team of innovators, disruptors, and problem-solvers dedicated to one mission: removing the friction from the commercial vehicle industry. We are profitable, growing, and aggressively scaling our technology to remain the undisputed authority in this space. This is a remote Staff Software Engineer role, our senior individual-contributor track, and the bar is high. A senior engineer is measured by the work they ship; a staff engineer is measured by what the team ships because of them. You are the person others look to when the problem is hard, the requirements are unclear, or the stakes are real. You set technical direction that reaches beyond a single team, choose the patterns others build on, and take the ambiguous, high-impact work that has no obvious owner and drive it to done. Our engineering team is moving to an agentic way of working, where much of our code is written by AI agents under human review. You will help lead that shift. You know how to build and maintain the skills, agents and context that make AI agents useful on a real codebase, and you set the standards that keep what they produce correct, secure and maintainable. You define how the team builds with AI, not just which tools it uses. This role is backend focused. You will spend most of your time in .NET and SQL Server, and you will know the frontend well enough to own a feature end to end. You will work day to day inside a software development team of 4-5 engineers, but your influence extends across teams. You make the engineers around you better through the standards you set, the reviews you give, and the way you teach. You have a bias toward action: you would rather ship something real, learn, and correct than debate an abstraction for a week.

Requirements

Backend-focused engineer, and .NET is required.
Expert in .NET (C#, .NET Core, ASP.NET Web API) and SQL Server.
Working foundation in frontend development.
Staff-level track record. Years of building and operating production systems, with a clear history of raising the bar on the teams you have been part of.
AI development process experience (required). You know what skills and agents are, and you have built and maintained them for a real codebase and team. You can talk about that work in specifics: skills, agent configurations, rules or MCP integrations you wrote, how you kept them current as the code changed, and a time AI-generated code went wrong and how you caught it. You have a point of view on where these tools help, where they get in the way, and how to review what they produce.
Full-stack range. Backend is your home, but you can own a feature from the database to the UI.
Strong Git workflow. Branching, pull requests, and code reviews are second nature.
Years of building and operating production-grade systems in .NET (C#, .NET Core, ASP.NET Web API).
Demonstrated ownership of scalable, fault-tolerant, performance-critical systems.
Strong experience designing API architectures (REST and/or GraphQL) with attention to versioning, maintainability, and real-world tradeoffs.
Proven ability to handle complex system challenges, including: Concurrency, data consistency, and race conditions. Caching strategies (Redis, in-memory) and invalidation. Asynchronous processing and queue-based architectures.
Deep expertise in SQL Server: Schema design and data modeling. Query optimization, indexing, and performance tuning. Sound judgment on when to use an ORM versus direct SQL.
Experience with distributed systems and integrations, including: Event-driven architectures (queues, pub/sub). Resilient integrations (retries, idempotency, failure handling).
Strong understanding of security fundamentals (JWT, OAuth, RBAC).
Experience with observability and production operations: logging, monitoring, debugging, and root cause analysis.
Experience deploying and operating systems in Azure (App Services, Functions, Service Bus, Redis) preferred.
Experience designing and maintaining CI/CD pipelines (GitHub Actions, Azure DevOps, or similar).
Experience building production web applications with React and/or Svelte / SvelteKit.
Proficiency in JavaScript and TypeScript.
Comfortable with component patterns, application state, and integrating UIs with REST/GraphQL APIs.

Nice To Haves

NodeJS experience is a plus.
Experience building LLM-powered product features, such as tool use, retrieval, or evaluations of AI output.

Responsibilities

Technical leadership across teams. Own the technical direction for your domain and influence it across teams. Make architecture decisions end to end, advocate for the better way to do things, and mentor engineers well beyond your own squad.
Lead AI-driven development. Build and maintain the skills, agents, rules and context (such as MCP servers and the documentation agents read) that let the team build with AI. Use AI coding agents (Cursor, Claude Code or similar) to speed up delivery and to refactor and migrate code at scale.
Set the standard for AI-generated code. Define how agent-written pull requests are reviewed and tested, including agentic testing, so that speed does not cost correctness, security or maintainability.
Raise the team’s AI fluency. Teach engineers to work this way through pairing, code review and shared tooling. Evaluate new tools and measure whether they actually help.
Drive the hard, ambiguous work. Take the projects that lack a clear owner or a clean spec, define the plan and the tradeoffs, and lead them to a shipped result.
High-quality output. Build secure, scalable, high-performance applications with a strong focus on maintainability and clean architecture, and set the standard the team builds to.
Lead through writing and specs. Write clear technical specifications to frame and lead a project. Establish the performance metrics for your domain, and make sure observability and reliability are designed in, not bolted on.
Set and enforce quality. Own coding standards and lead peer code reviews. Use reviews and pairing to teach, not just to gate.
Collaboration. Communicate clearly with a distributed team, surface issues early, and work fluently with both technical and non-technical partners.