Claude prompts for robotics and embodied AI engineer job searches

I am applying for the robotics / embodied AI engineer role below. Rewrite my resume to match it using only experience that is already on my resume. Do not invent robots, sensors, frameworks, deployments or success rates. The posting may ask for perception, planning, control, learned policies, simulation, ROS, real hardware experience or field deployment; for each requirement, find the closest real evidence in my resume, and if there is none, put it under "Gaps" rather than writing it in. Output: a table with the columns requirement, evidence, rewritten bullet; a revised one-page resume in plain text where each bullet names the platform, what I built, and the measured result, stated honestly as real hardware or simulation; and the Gaps list with one honest sentence per gap. Keep every job, title and date unchanged.

Job description:
[paste job description]

My resume:
[paste your resume]

Write a cover note of at most 120 words for the robotics / embodied AI engineer role below. Use only facts from my resume and my notes. No invented results, no "passionate", no "revolutionize". Structure: one sentence that shows I understand the robot and the environment this team works in (the task, the hardware, the constraints; take it from the job description), two sentences on the most relevant system I have built and what it did on real hardware or in simulation, with a number if I have one, and one closing sentence with a specific ask. Then give a 50-word version for a LinkedIn message. Sentence case, plain words, no exclamation marks.

Job description:
[paste job description]

My resume:
[paste your resume]

Why this team, in my words:
[two or three lines]

Act as the interviewer for a 45-minute robotics / embodied AI engineer technical screen at the company below. Ask one question at a time and wait for my answer. Cover, in order: one coding question in Python or C++ (for example a transform between frames, a simple path search on a grid, or filtering a noisy sensor stream), two fundamentals questions drawn from the job description (for example the difference between a Kalman filter and a particle filter, how a PID controller fails, the sim-to-real gap and how to narrow it, how to collect demonstrations for a learned policy, or how to define success for a manipulation task), one question about a system on my resume, and one debugging scenario (the robot succeeds in simulation and fails on hardware; what do you check first). After each answer, score it 1 to 5, give a strong answer, and name the one thing I should have said. End with three topics to review tonight.

Job description:
[paste job description]

My resume:
[paste your resume]

Run a robotics system design interview with me for the role below. Pick a problem that fits the company (for example picking items from bins in a warehouse, navigating a hospital corridor, or a learned policy for a household task) and describe it in two sentences. Guide me one stage at a time, waiting for my answer: the task specification and what success means, the sensors and their failure modes, perception, state estimation, planning and control and where learning fits, the data needed and how to collect it, simulation and its limits, safety and what the robot does when uncertain, latency and compute on the robot, testing on hardware and the metrics, and how to find and fix failures after deployment. After each stage, point out what an experienced robotics engineer would have raised that I missed. Finish with a one-page summary in my corrected words. Do not give the full answer up front.

Job description:
[paste job description]

What I know about the robot and the task:
[a few lines]

Help me prepare behavioral answers for a robotics / embodied AI engineer interview using only the situations I describe below. Do not add details; if a story is missing an outcome or a number, ask me for it. First list the eight questions most likely for this role and company (a system that worked in simulation and failed on hardware, a safety incident or near miss, a hardware delay that changed the plan, disagreeing with a teammate about an approach, a demo deadline, a mistake you owned, working with mechanical or electrical engineers, and debugging something intermittent). Then map each to one of my stories and write an answer of 150 to 200 words in the shape situation, action, result, what I would do differently. Flag where the same story is used twice so I can spread them out.

Job description:
[paste job description]

My stories, rough notes are fine:
[three to five real situations]

Turn my notes below into a portfolio write-up of 500 to 700 words about a robotics project, first person, plain language, aimed at a hiring manager. Use only what is in my notes. Where something important is missing (the task, the platform and sensors, the success metric and its number, how many trials on real hardware versus simulation, the failure cases, what I owned versus the team), insert a placeholder in square brackets and list the placeholders at the end. Structure: the task and its constraints, the hardware, the approach and what I tried first, the results stated honestly as simulation or hardware with trial counts, the failures and what they taught me, and what I would do next. Suggest a title, a two-sentence README summary, three honest resume bullets, and what a 30-second video of the system should show.

Project notes:
[paste notes, commit messages, lab notebook or a rough description]

I have an offer for a robotics / embodied AI engineer role. Below are the offer details, my current compensation, any competing offers and what I have found from public sources. Help me evaluate and negotiate honestly; do not invent market data, and tell me what to look up if you need a number I have not given. Output: (1) a table of four-year total compensation under a cautious and an optimistic equity assumption; (2) which components are most negotiable for this kind of company (hardware startup, large company, research lab) and why; (3) a short script for the call that asks for a specific number with a reason tied to my experience, in a collaborative tone; (4) questions to ask before accepting, including the level, vesting, hardware and lab access, travel or field expectations, the state of the platform, runway if it is a startup, and how success is measured. Under 500 words.

Offer:
[base, bonus, equity and vesting, signing bonus, location]

My situation:
[current compensation, competing offers, constraints]

Write a 30/60/90-day plan for me as a new robotics / embodied AI engineer on the team below. Keep it realistic: I have to learn the platform, the safety procedures, the codebase, the simulation setup and the people before changing anything. Days 1 to 30: operating the robot safely, running the existing stack end to end, reading the failure logs and incident history, and meeting the hardware, software and operations people I will depend on. Days 31 to 60: a first contribution, for example a reproducible test on hardware, a simulation fix that closes a sim-to-real gap, or a measured improvement in one subsystem. Days 61 to 90: a measurable project with a success metric and risks. For each block, give three to five outcomes rather than activities and one question to ask my manager in week one. Mark assumptions I should verify. Under 450 words.

Job description:
[paste job description]

What I learned about the team in interviews:
[notes]

Give me a failure-analysis drill for a robotics / embodied AI engineer interview at the company below. Describe a realistic failure in three or four sentences (for example a mobile manipulator that drops objects in one corner of the warehouse, or a policy that succeeds in 90 percent of trials in simulation and 40 percent on hardware). Then ask me, one at a time and waiting for each answer: what I would look at first and why, how I would separate perception, state estimation, planning, control and hardware causes, what logs or data I would want, what experiment would isolate the leading hypothesis, how I would confirm a fix without fooling myself, and what I would change in testing so this class of failure is caught earlier. After each answer, tell me what I missed and give the version a strong candidate would give. Finish with a short checklist I can reuse for any failure question.

Job description:
[paste job description]

What I know about the robot and the task:
[a few lines]