# Inside Motive’s engineering interview (fleet tech, ex-KeepTruckin)

Source: https://www.techinterview.org/post/3233477511/motive-interview-guide/
Updated: 2026-09-24 · techinterview.org

Motive, the fleet-management and physical-operations company that was called KeepTruckin until 2022, runs a long engineering loop: a recruiter screen, two data-structures coding rounds, a practical API-building exercise, a system-design round, and one or two rounds with the hiring manager or a director. Candidates report five to seven conversations spread over roughly two months. The coding questions sit in LeetCode easy-to-medium range, with union-find and REST-data-processing problems both showing up in recent reports. Motive stayed private in September 2026 after taking $1.3B from General Catalyst and pulling its IPO filing, so treat any equity offer as illiquid and ask hard questions about it.

If you searched "Motive interview" and half your results were about the abstract noun, here is the company you probably mean. Motive is the San Francisco firm building an AI platform for physical operations: trucking fleets, field-service crews, construction sites, and the vehicles and workers those businesses run every day. It was founded in 2013 as KeepTruckin, a name a lot of drivers still use, and [rebranded to Motive in 2022](https://en.wikipedia.org/wiki/Motive_(company)). Shoaib Makani has been CEO the whole way.

The company matters more than its category might suggest. In September 2026 Motive raised more than $1.3 billion in growth financing from General Catalyst and [withdrew its previously filed S-1](https://gomotive.com/motive-secures-more-than-1-3-billion-in-growth-financing-from-general-catalyst/), choosing to stay private and spend hard on AI instead of going public. It reported annual recurring revenue past $600 million, growing about 30% year over year, with [revenue from its larger customers growing faster still](https://www.freightwaves.com/news/motive-1-3-billion-growth-financing). For a candidate, that mix of real revenue and fresh capital, with no near-term IPO, shapes both the questions you get and the equity you are offered.

Motive's product surface is wide, and the interview reflects it. The platform covers vehicle and equipment tracking, an AI dashcam for driver safety, compliance tooling for Hours-of-Service and electronic logging, fleet maintenance, and a spend-management product built around the Motive Card. Engineering splits across full-stack web and mobile, applied AI on the safety and telematics data, and hardware and firmware for the cameras and vehicle gateways. Which loop you get depends heavily on the team you are talking to. The rounds below describe the general software loop; public write-ups don't break out the applied-AI or the mobile and frontend loops in detail, so if you're targeting one of those, ask your recruiter which rounds swap in.

## The interview loop, as candidates describe it

Motive doesn't publish its process, so the shape below is reconstructed from recent candidate reports on Glassdoor, 1point3acres, and engineers writing up their own loops, not an official spec. Treat the exact round count as approximate. Reports range from five to seven separate conversations, and the whole thing can take up to two months, which is slow by current startup standards. If you're interviewing elsewhere in parallel, plan around that.

The pieces that show up consistently: a recruiter or hiring-manager screen up front, two coding rounds focused on data structures and algorithms, a practical coding round where you build something real against an API, a system-design or high-level-design round, and a hiring-manager or director round that is mostly behavioral. A senior loop (Sr. SDE and up) weights the design round and the manager conversation more heavily. A new-grad or mid-level loop leans on the two algorithm rounds.

| Motive round | Format | What it screens for |
| --- | --- | --- |
| Recruiter / hiring-manager screen | 30-45 min call | Background fit, motivation, level calibration |
| Coding round 1 (algorithms) | Live LeetCode easy-to-medium | Data structures, clean implementation, edge cases |
| Coding round 2 (algorithms) | Live LeetCode easy-to-medium | Algorithms; union-find and similar have been reported |
| Practical coding / machine coding | Build against a REST API in a bare environment | Fetching and processing real data, code structure |
| System / high-level design | Whiteboard or shared doc, senior-weighted | Designing data-heavy systems shaped like Motive's own |
| Hiring manager / director | Behavioral, 45-60 min | Ownership, communication, team fit |

## What the coding rounds actually ask

The algorithm rounds sit in LeetCode easy-to-medium range, not the brutal hard-problem gauntlet some larger companies run. Candidate write-ups on [Glassdoor](https://www.glassdoor.com/Interview/Motive-Software-Engineer-Interview-Questions-EI_IE1018424.0,6_KO7,24.htm) and 1point3acres describe a classic [union-find problem with path compression](/post/3233474181/coding-interview-union-find-disjoint-set-deep-dive-path-compression-union-by-rank-connected-components-kruskal-accounts-merge/), the kind of connected-components question that maps neatly onto grouping vehicles, accounts, or events. What they're watching is whether you reach for the right structure and implement it cleanly.

The other commonly reported round is more practical: spin up a minimal environment, then write code that fetches data from a REST API and processes it. If your day job is buried inside a framework and you haven't written a from-scratch HTTP call and JSON parse in a while, rehearse that until it's boring. They want to see you handle real inputs, not recite an algorithm.

Nothing exotic here. Working through [the standard coding patterns](/algorithm-patterns-cheat-sheet/) and staying fluent with [time and space complexity](/big-o-cheat-sheet/) covers the algorithm rounds. The practical round rewards people who write and run code every day rather than people who only study for interviews.

## System design, shaped like the product

No single design prompt shows up across reports, so prepare for problems that look like Motive's own systems rather than a canned "design Twitter." Think about ingesting a firehose of GPS and sensor pings from hundreds of thousands of vehicles, the event pipeline behind a dashcam safety alert that has to fire in near real time, or modeling Hours-of-Service as a state machine that stays correct on a device that lost signal for an hour and has to reconcile later.

Bring the usual muscles: partitioning a high-volume write path, handling out-of-order and duplicate events, and deciding what to compute at ingest versus at query time. For the GPS firehose I'd reach for an append-only log like Kafka over a plain task queue, because you want ordered, replayable events per vehicle that several consumers (alerting, storage, analytics) can read independently, not one worker draining a queue once. A worked [fleet-management and vehicle-tracking design](/post/3233462882/system-design-fleet-management-vehicle-tracking/) and the broader [system design guides](/system-design-interview-guides/) hub both cover those patterns, and it helps to have real opinions rather than a memorized diagram. Any interviewer at a company with hardware in the field can smell a rehearsed answer that ignores those messy realities.

## The hardware and firmware track

Motive builds its own dashcams and vehicle gateways, so there's an embedded and firmware org behind the SaaS. Public candidate reports mostly cover the software loop above, so I won't invent embedded-round details that aren't documented. If you're interviewing for a firmware or device role, expect a different shape: C and C++, tight memory budgets, and debugging stories from the physical device that the software loop never asks for. Ask your recruiter to walk you through the exact rounds for that team, because they won't match the SaaS loop.

## The manager and behavioral rounds

The hiring-manager and director rounds are a resume walkthrough plus the usual ownership and conflict questions, with a real "why Motive" thread running through them. This is a company selling to trucking and logistics operators, not another dev-tools startup, so having a genuine answer for why physical operations interests you goes further than it would elsewhere. Have a couple of tight [STAR-format stories](/post/3233460379/behavioral-interview-questions-2026-star-method-amazon-leadership-principles-and-winning-answers/) ready about shipping something end to end and about a time you owned a messy production problem.

## Comp, and why the equity question is different here

I won't quote a number, because Motive doesn't publish ranges and the real figure depends on level, team, and location. Pull current data points from levels.fyi and Glassdoor, then run the offer through a [total-comp calculator](/total-comp-calculator/) before you negotiate. One wrinkle specific to this company: Motive built a large engineering team outside the US (a sizable office in Pakistan dating to the KeepTruckin days, plus India), so a single "Motive comp band" means nothing across those markets. Compare within your own geography or you'll anchor on the wrong number. Public reports don't consistently say whether US roles sponsor work visas or whether the Pakistan and India roles are local-hire only, so if you need sponsorship, confirm it with your recruiter early.

The equity conversation deserves more attention than usual. By staying private and withdrawing the S-1, Motive told you there's no liquidity event coming soon. Your options or RSUs are real but illiquid, possibly for years. Ask whether the company runs tender offers or secondary sales for employees, what the current 409A valuation is relative to the last preferred round, and how far the strike price sits below that. [Negotiating](/post/3233474669/salary-negotiation-2026/) a private-company offer comes down to the cash and the equity terms, not a headline valuation you can't cash out.

## How to prep without wasting a month

Given the two-month timeline, front-load the algorithm rounds so they're behind you early, then keep them warm with a light rotation while the later rounds get scheduled. A [study plan](/study-plan/) keeps that from turning into aimless grinding. Spend real time reading about the product and the space; a candidate who can talk about ELD compliance or fleet safety data stands out against one who clearly learned the company name that morning. If you want a feel for how physical-world companies run their loops, the [Applied Intuition guide](/post/3233477460/applied-intuition-interview-guide/), the [Waymo interview guide](/post/3233476865/waymo-interview-loop-safety-round/), and the rest of the [company guides](/companies/) are useful comparisons.

Strong Motive candidates stand out by how they reason about messy real-world data: a truck that dropped signal for an hour, a dashcam event that fired twice. Raw LeetCode speed matters far less. Bring that instinct into every round and the rest is just execution.