# 3D trajectory prediction interview question

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/questions/5986/3d-trajectory-prediction
Source observed: 2026-11-04T23:11:31.703Z
Last checked: 2026-11-04T23:11:31.703+00:00
Indexed: 2026-11-06T03:49:57.698+00:00

---

# Given 3D trajectory data, manipulate/tokenize it into a usable format so you can predict the next step from the current trajectory.

We publish this as an Aced (formerly Exponent) interview question in the **Coding** category. It concerns a **Machine Learning Engineer** interview at **Waymo** and asks you to work with sample 3D trajectory data containing fewer than 100 rows.

## Question focus

The task described is to:

- Manipulate the supplied 3D trajectory data with NumPy.
- Tokenize the data into a usable format.
- Use the current trajectory to predict the next step.

The detailed company statistics for this question require an upgrade: [Upgrade](https://www.aced.io/upgrade?src=questions).

## Question details

- **Interview count:** 2 interviews
- **Role:** [Machine Learning Engineer](https://www.aced.io/questions?role=ml-engineer)
- **Company:** [Waymo](https://www.aced.io/questions?company=waymo)
- **Category:** [Coding](https://www.aced.io/questions?type=coding)
- **Reported last asked:** 9 months ago

## Interview experience

We have one shared interview experience for this question:

### Waymo — Machine Learning Engineer, Staff / L6

[Read the full Waymo interview experience](https://www.aced.io/experiences/waymo-machine-learning-engineer-interview-a6f409)

> “I applied directly on the website with no referral and went through a pretty Google-like process. The loop was a basic recruiter chat, then a surprisingly hard LeetCode-style coding screen, then a final loop with another coding round, an ML coding round, an ML system design round, and two behavioral rounds. What really stood out was that the coding bar felt basically software-engineer level, not a watered-down MLE bar, and then on top of that they still expected solid ML depth. The strangest round for me was the final coding interview because it was more practical and diagram-based than I expected, while the behavioral rounds went deeper into the technical details of my projects than most companies do. Do not under-prepare on DSA just because the title says machine learning.”

## Community answers

No community answers have been contributed yet. Sign in or create an account to submit an answer.

## Related courses

### [Machine Learning Engineer Interview Prep](https://www.aced.io/courses/ml-engineer)

![Machine Learning Engineer Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/6UfkHxUyLQVfDHSfLNQtWa/1be1539a65b4f6f15201f5b573c0a578/ML_Engineer_Interview_Prep_Course.jpeg?w=800&h=800&fm=webp&q=75)

We cover preparation for machine learning roles at Meta, Google, Amazon, Apple, Microsoft, Nvidia, and other top companies through mock interviews, frameworks, and advice from senior candidates. Topics include ML system design, core concepts, coding, and behavioral interviews.

### [Behavioral Interviews: A Practical Guide for Engineers](https://www.aced.io/courses/eng-behavioral)

![Behavioral Interviews: A Practical Guide for Engineers](https://images.ctfassets.net/x78yjrjc11pq/47qcoHjzFZXE37GoacedkB/9d8e3f4910d8b06b21e76745cd9cbff3/AdobeStock_1142146335.jpeg?w=800&h=800&fm=webp&q=75)

We help candidates prepare for senior-plus behavioral interviews at FAANG and Tier-1 companies. The course is made with staff and principal engineers from Meta, Netflix, Google, and more, with guidance on avoiding downleveling, elevating past projects, and communicating naturally.

## Submit your answer

Sign in or sign up to answer this question. Submitting an answer marks the question complete.

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F5986%2F3d-trajectory-prediction&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F5986%2F3d-trajectory-prediction). Opening a form does not execute a tool.