Perception Engineer - Defense (All-Domain)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Learn more at applied.co."? That's maybe not needed but it's not boilerplate; it's info about company. Might keep? It's part of description but not a section. We can keep in a paragraph maybe under About the role? The instruction: "Prefer a few substantive sections over many thin ones." We need to decide which sections to include. We have content: - About The Role: description of role, tasks. - Responsibilities: list of tasks (bulleted). The posting includes "At Applied Intuition Defense, You Will ..." with bullet-like sentences. Those are responsibilities. - Requirements: "We’re Looking For Someone Who Has ..." includes education/experience, proficiency, etc. Also travel requirements, security requirements. - Qualifications: maybe overlapping with requirements. Could combine. - Skills: maybe list of technical skills: transformers, vision-language models, diffusion models, video model training pipelines, PyTorch, edge deployment, agentic coding, Python/C++, GitHub Copilot, Cursor, remote software development, large datasets, learning new software. - Benefits: The posting mentions compensation includes base salary, equity, benefits: health, dental, vision, life and disability insurance, 401k with match, learning and wellness stipends, paid time off. Also note benefits subject to change. - Pay: Compensation Range: $160K - $220K. - Schedule: The posting mentions "We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions". That's schedule info. Thus we can include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications not needed if covered. We must not include placeholder text like "commensurate with experience". Not present. We must not repeat job title. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include the content exactly as given, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the info, not omit details. We can keep the same wording but maybe restructure into lists. We must not create sections with filler/placeholder text. Ensure each section has real content. Let's extract details. About the role: The paragraph after "About The Role": "The Perception Engineer role at Applied Intuition Defense is a hands-on, full-stack, high tempo position where you will be part of an expert team rapidly pursuing the second (99%) and third nine (99.9%) of perception model performance across maritime, land, air-to-surface, and surface-to-surface domains, in EO and IR. We develop our own custom detector and classifier architectures, we’ve developed our own comprehensive MLOps tooling allowing us to rapidly iterate at the scale of millions of images and videos, we make our own industry-leading labeling software, and we manage in-house labeling on a daily basis. We do all of this using frontier AI and large token budgets. If something needs to be built to get the job done, we will build it. If you have extensive modeling experience with transformers, vision-language models, diffusion models, and video model training pipelines, we need you. If you have deployed production ML models into the real world or optimized them heavily, we need you." We'll put that in

  . Responsibilities: The bullet list after "At Applied Intuition Defense, You Will". It includes multiple sentences each starting with a verb. We'll turn each into

• . List: - Develop perception models that find and classify targets with an error rate of (the text cut off? Actually "Develop perception models that find and classify targets with an error rate of" seems incomplete; maybe missing a number. But we must preserve as is. It says "Develop perception models that find and classify targets with an error rate of". Probably incomplete but we keep. - Deploy perception models to Jetson Orin+ boards and optimize models for better-than-realtime performance. - Build large foundation models for high-accuracy assisted data labeling. - Build tooling across the entire perception stack: labeling tools, simulation. - Work with the best and most competitive AI talent in the world through collaboration with Applied Intuition self-driving staff. - Scale up datasets using a variety of state-of-the-art data generation techniques including simulation, diffusion, and generative AI. - Create and maintain highly optimized models and inference software providing model results at maximum attainable frames per second (FPS) on Jetson-like hardware. - Collaborate across the hardware, sensor, tracking, autonomy, and testing teams to ensure seamless deployment in on-site DoD testing and demonstration events. We'll keep exactly as given. Requirements: The section "We’re Looking For Someone Who Has ..." includes: - MS or PhD in Computer Engineering, Robotic Engineering, Computer Science, or equivalent OR 5+ years of relevant experience working with simulation, machine learning, and ML infrastructure. - Proficiency in training ML models in PyTorch on multi-machine, multi-GPU systems. - Experience in optimizing and deploying machine learning models to edge devices. - Strong experience with agentic coding with proven experience in Python and/or cpp. - Experience leveraging modern AI-powered development tools (e.g., GitHub Copilot, Cursor) to accelerate the creation of robust, well-tested systems. - Adeptness with remote software development, the ability to handle and process large datasets, and a capacity to learn new software and algorithms as needed with little supervision. Then "Travel Requirements": Must be willing to travel as projects require, usually for SW/HW integration and/or demonstrations; estimated average travel is 2-5 days every other month (10-20%). Then "Interested candidates should also inquire about relocation assistance to Applied Intuition Defense facilities near Destin, FL, Washington, D.C., or San Diego, CA". Then "Security Requirements": Must be a U.S. Citizen; Must hold or be eligible to obtain and maintain a U.S. security clearance; plus link. We can include travel and relocation and security under Requirements or maybe separate but we can keep within Requirements as list items. Skills: Could extract technical skills: transformers, vision-language models, diffusion models, video model training pipelines, PyTorch, edge device optimization, agentic coding, Python/C++, GitHub Copilot, Cursor, remote software development, large dataset handling, learning new software, simulation, diffusion, generative AI, Unreal Engine, NVIDIA Omniverse, Blender, 3D asset creation, Transformer-based model optimization for edge devices, SIL/HIL, COTS hardware (NVIDIA Jetson, Raspberry Pi5). Also maybe "foundation models", "MLOps tooling", "labeling software". But we should not invent; we can list those explicitly mentioned in the posting. We have "Nice To Have" section with additional skills: PhD in CV/ML, 5+ years building perception models on real-world hardware, background in generating datasets using simulation engines like Unreal Engine, NVIDIA Omniverse, Blender, or 3D asset creation tools, experience with deeply optimizing Transformer-based models for edge devices like NVIDIA Jetson boards, familiarity with SIL and HIL including integration and test experience on common COTS hardware devices (e.g., NVIDIA Jetson, Raspberry Pi5). We can include those under Skills. Benefits: The paragraph: "Compensation at Applied Intuition for eligible roles includes base salary, equity, and benefits. Base salary is a single component of the total compensation package, which may also include equity in the form of options and/or restricted stock units, comprehensive health, dental, vision, life and disability insurance coverage, 401k retirement benefits with employer match, learning and wellness stipends, and paid time off. Note that benefits are subject to change and may vary based on jurisdiction of employment." We'll put that in

  under Benefits. Pay: "Compensation Range: $160K - $220K". Also earlier mention about base salary being a component; but we have explicit range. Schedule: The paragraph about in-office expectation 5 days a week, flexibility, occasional remote work, morning meetings from home, leaving earlier, not apply to contractor positions. We'll put that. We must not include boilerplate like EEO, equal opportunity, etc. Remove those paragraphs. Also remove "Learn more at applied.co." maybe not needed but it's not boilerplate; but it's not part of any section; we could include it in About the role paragraph? It's a separate sentence after company description. Might be considered part of company overview; we could keep it in About the role? But it's not about the role. The instruction: "Prefer a few substantive sections over many thin ones." We could include a short paragraph about company under maybe no heading? But we must not create headings without content. Could we just omit that sentence? It's substantive info about company but not required for role. However we must preserve ALL substantive information; we cannot omit it. So we need to include it somewhere. Perhaps we can include it in a paragraph before the sections, not under a heading. The instruction says output only HTML fragment; we can have a leading

  with company overview. That's acceptable. Thus structure:

  Applied Intuition, Inc. is powering the future of physical AI. Founded in 2017 and now valued at $15 billion, the Silicon Valley company is creating the digital infrastructure needed to bring intelligence to every moving machine on the planet. Applied Intuition services the automotive, defense, trucking, construction, mining and agriculture industries in three core areas: tools and infrastructure, operating systems, and autonomy. Eighteen of the top 20 global automakers, as well as the United States military and its allies, trust the company’s solutions to deliver physical intelligence. Applied Intuition is headquartered in Sunnyvale, California, with offices in Washington, D.C.; San Diego; Ft. Walton Beach, Florida; Ann Arbor, Michigan; London; Stuttgart; Munich; Stockholm; Bangalore; Seoul; and Tokyo. Learn more at applied.co. We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions

  But note that the schedule paragraph is duplicated; we already have schedule info later. We might want to keep schedule section separate and not duplicate. However we must preserve all info; we can keep it in schedule section and not duplicate in the intro. The intro includes company overview and also schedule expectation; we could split: keep company overview in intro, and schedule details in Schedule section. The sentence about in-office expectation appears twice? Actually the text: "We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day