Senior Software Engineer

Description

Senior Software Engineer (Full-Stack Mastermind)

$200k – $220k / year

Fully remote

Description

Most software engineers write code. We're looking for someone who changes the trajectory of a product.

Do you thrive on owning a problem from the database all the way through the user experience? Can you move comfortably between designing an API, debugging a production issue, optimizing a SQL query, and improving a front-end workflow? Are you the type of engineer who sees a complicated problem, figures out what needs to happen, and ships a solution other people thought would take twice as long?

And just as importantly: are you already figuring out how AI changes the way great software gets built?

If so, read on.

I'm the Head of Engineering at RTA, and I'm looking for a Senior Software Engineer to help build and evolve Fleet360, our fleet management SaaS platform. This is a high-ownership, high-impact role. You won't just be executing tickets. You'll be shaping solutions, making architectural decisions, working across the stack, and raising the engineering bar for the people around you.

We are also serious about becoming an AI-first engineering organization. That doesn't mean blindly generating code and shipping whatever an LLM spits out. It means using AI as a force multiplier throughout the software development lifecycle: understanding unfamiliar code, exploring solutions, generating and reviewing implementations, writing tests, debugging issues, documenting systems, automating repetitive work, and dramatically increasing the speed at which a great engineer can deliver great software.

We want engineers who are actively figuring out how to work differently because these tools exist.

This role is not for everyone. If you prefer clearly scoped tasks, minimal ambiguity, staying exclusively in one layer of the stack, and steady incremental work, we'd still love to have you, just not in this seat.

This role is for engineers who see an undefined problem and feel a pull toward it, not away from it.

What we're looking for

In general, someone who:

• •Is a force multiplier. When you're on a project, the whole team moves faster and ships better. You raise the bar just by being in the room.
• •Is passionate about serving others.
• •Thinks like a product engineer, not just a programmer. You care about the outcome for the user, not simply whether your code works.
• •Owns problems end to end. Front end, API, database, integration, production issue: you go where the problem takes you.
• •Works AI-first. You actively use modern AI development tools to make yourself faster and more effective, and you're constantly experimenting with better ways to use them.
• •Knows that AI output still requires engineering judgment. You validate assumptions, understand generated code, test aggressively, and never confuse speed of generation with correctness.
• •Has strong opinions, loosely held. You push back when something is wrong, but you update your views when presented with better information. You're not trying to be the smartest person in the room. You want the team to find the right answer.
• •Is comfortable being part of a team that thrives on healthy conflict. People with thin skin need not apply. No, seriously.
• •Passionately cares about our clients, who are fleet managers, parts clerks, and automotive technicians maintaining everything from squad cars to school buses, so everyone comes home safely at the end of the day.
• •Thinks of themselves less, while not thinking less of themselves. You're other-centric, compassionate, and self-assured.
• •Takes ownership and initiative. You identify how to make our products and processes better without waiting for permission. You don't ask for a ticket to fix something obviously broken.
• •Loves to read, learn, grow, and stretch themselves. Bonus points for each book they've read by Patrick Lencioni.

What we actually require

Five things. If you have these, apply and we'll figure out the rest together.

• •5–7+ years of professional software engineering, with real ownership of production software. Not years logged, but systems you were responsible for when they broke.
• •Genuinely full stack. You may be stronger in one area, but you move between the browser, API, database, infrastructure, and third-party integrations when the work requires it.
• •Node.js and TypeScript at production scale. Well-designed APIs and services that hold up under real load.
• •Deep relational database ability. You design schemas, write and optimize SQL, diagnose performance problems, and reason about data integrity and concurrency.
• •AI-assisted development as a daily workflow, with judgment. You can break a problem down, give a coding agent useful constraints, evaluate what comes back, iterate, and steer it to a production-quality result. And you can tell when it's confidently wrong.

What strengthens your application

None of these are dealbreakers. Any of them make you more interesting to us:

• •Vue.js specifically, since it's what our front end is built on. Strong React or Angular experience translates well.
• •Browser-side application architecture: component design, state management, async behavior, performance, maintainable UX.
• •Systems design beyond features: services, event-driven patterns, distributed systems, data flows, and judgment about when complexity is and isn't justified.
• •Messaging and queues such as RabbitMQ, Kafka, or AWS SQS, used to build resilient and decoupled systems.
• •Caching and distributed application patterns, including technologies such as Redis.
• •Containerized, cloud-native applications, including Docker, AWS ECS/EKS, and Kubernetes.
• •Observability as a first-class concern: logs, metrics, traces, profiling, APM.
• •DevOps fundamentals: CI/CD, automated testing, and how software gets safely from a laptop into production.
• •Building AI-powered product capabilities: LLM APIs, tool and function calling, RAG, embeddings, vector search, structured outputs, evaluation, agents. Deep AI/ML research background is not required.
• •Communicating with precision: explaining an architectural tradeoff to a product manager and a hairy debugging session to a junior engineer without losing either of them.
• •A Bachelor's degree, especially in computer science or a related field. Not required.

Working with AI here

This is the part we care most about, so here's what we mean concretely:

• •You work agentically, not with autocomplete. You've driven multi-file refactors, migrations, and test coverage with coding agents, not just accepted single-line suggestions. You maintain the context files, rules, and prompts that make those tools work for a whole team, not only for you.
• •You review AI-generated work like code from any other contributor. Understand it, challenge it, test it, improve it, then ship it.
• •You have an eval habit. You can explain how you knew an AI feature actually got better, rather than just felt different.
• •You know when not to use a model. Our customers track DOT compliance, warranty claims, and parts inventory. Some of that must never be answered by something probabilistic, and you can tell which parts.
• •You look for engineering work to automate: test generation, debugging, code analysis, migrations, documentation, repetitive implementation, internal tooling.
• •Bring proof. A repo, an eval suite, a rules file, an agent workflow you built for your team. Anything real tells us more than another year of experience on paper.

Key responsibilities

• •Own features end to end: idea to production, across front-end interfaces, APIs, business logic, databases, integrations, and supporting infrastructure.
• •Build great user experiences: responsive, reliable, maintainable front-end functionality, with real understanding of the systems and data behind it.
• •Design and build back-end systems: scalable services and APIs in Node.js and TypeScript, with sound architectural and data-modeling decisions.
• •Work AI-first: use AI-assiste