Add CV guidance and humanoid robotics context notes for Hexagon applications
This commit is contained in:
164
02_Projects/CV Guidance - Hexagon Applications.md
Normal file
164
02_Projects/CV Guidance - Hexagon Applications.md
Normal file
@@ -0,0 +1,164 @@
|
||||
# CV Guidance - Hexagon Applications
|
||||
|
||||
**Created:** 2026-03-11
|
||||
**Status:** Draft
|
||||
**Related:** [[Hexagon Role Analysis]], [[Job Hunt]]
|
||||
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
Concrete, actionable CV tailoring guidance for Hexagon Robotics applications. Focus on motion planning role (primary) and mission control role (secondary).
|
||||
|
||||
---
|
||||
|
||||
## CV Structure Recommendation
|
||||
|
||||
### 1. Headline (if used)
|
||||
**For Motion Planning:** "Senior Robotics Engineer | Motion Planning & Autonomous Navigation"
|
||||
**For Mission Control:** "Senior Software Engineer | Robotics Systems Architecture & Integration"
|
||||
|
||||
### 2. Summary (3-4 lines max)
|
||||
|
||||
**Motion Planning:**
|
||||
"Senior robotics engineer with 5+ years leading motion planning, localization, and autonomous navigation systems. Specialized in real-time trajectory optimization, MPC, and planning under dynamic constraints. Transitioning expertise from aerial platforms to humanoid robotics with focus on whole-body motion planning."
|
||||
|
||||
**Mission Control:**
|
||||
"Senior software engineer with proven track record architecting and integrating complex autonomous systems. Led development of end-to-end drone platform integrating perception, planning, and control. Experienced in production-quality robotics software, CI/CD, and cross-team coordination."
|
||||
|
||||
---
|
||||
|
||||
## Experience Bullet Rewrites
|
||||
|
||||
### Motion Planning Emphasis
|
||||
|
||||
**Current:** (whatever exists about motion planning on CV)
|
||||
|
||||
**Enhanced versions:**
|
||||
|
||||
1. **Global/Local Planning:**
|
||||
- "Designed and implemented hierarchical motion planning stack combining global path planning (A*, RRT*) with local trajectory optimization for real-time obstacle avoidance."
|
||||
|
||||
2. **Real-time MPC:**
|
||||
- "Developed MPC-based trajectory tracking running at 100Hz with hardware-in-loop validation, achieving <5cm tracking error in dynamic environments."
|
||||
|
||||
3. **Planning under uncertainty:**
|
||||
- "Integrated probabilistic obstacle prediction into planning pipeline, enabling safe navigation in partially observable environments."
|
||||
|
||||
4. **Transfer to humanoid:**
|
||||
- "Architected planning system with extensibility to legged platforms; familiar with whole-body planning concepts and contact-rich manipulation."
|
||||
|
||||
### Mission Control / Integration Emphasis
|
||||
|
||||
1. **System Architecture:**
|
||||
- "Architected modular flight software stack with clean interfaces between perception, planning, and control layers, enabling rapid integration and testing."
|
||||
|
||||
2. **Integration Leadership:**
|
||||
- "Led integration of multi-sensor fusion stack (IMU, camera, LiDAR, GPS) with state estimation and control, reducing integration bugs by 40%."
|
||||
|
||||
3. **Production Quality:**
|
||||
- "Established CI/CD pipelines, automated regression testing, and simulation-to-real workflows for safety-critical autonomous systems."
|
||||
|
||||
4. **Cross-team Coordination:**
|
||||
- "Coordinated development across perception, planning, and control teams; defined interfaces and integration milestones."
|
||||
|
||||
---
|
||||
|
||||
## Keywords to Include
|
||||
|
||||
### Motion Planning Role (Primary)
|
||||
- Motion planning (global/local, sampling-based, optimization-based)
|
||||
- MPC (Model Predictive Control)
|
||||
- Trajectory optimization
|
||||
- Collision avoidance
|
||||
- Real-time systems
|
||||
- ROS2
|
||||
- C++ / Python
|
||||
- State estimation / SLAM (secondary but relevant)
|
||||
- Legged locomotion (learning objective)
|
||||
- Whole-body planning (learning objective)
|
||||
- Manipulation planning (learning objective)
|
||||
|
||||
### Mission Control Role (Secondary)
|
||||
- System architecture
|
||||
- Integration
|
||||
- Orchestration
|
||||
- Mission control
|
||||
- Behavior trees / state machines
|
||||
- Distributed systems
|
||||
- CI/CD
|
||||
- Production-quality software
|
||||
- Cross-team coordination
|
||||
- ROS2
|
||||
- C++ / Python
|
||||
|
||||
---
|
||||
|
||||
## Keywords to De-emphasize
|
||||
|
||||
### For Motion Planning Role
|
||||
- Hardware design (not relevant)
|
||||
- Business development (not relevant)
|
||||
- Frontend/web development (not relevant)
|
||||
|
||||
### For Mission Control Role
|
||||
- Deep learning specialization (overemphasis could signal ML focus over systems)
|
||||
- Pure simulation work without real-robot validation
|
||||
|
||||
---
|
||||
|
||||
## Cover Letter Points
|
||||
|
||||
### Motion Planning (Primary)
|
||||
|
||||
**Paragraph 1:** "I've spent the last 5 years building motion planning systems for autonomous drones, from global path planning to real-time MPC-based trajectory tracking. Your Motion Planning Engineer role is exactly the kind of deep technical work I'm looking for."
|
||||
|
||||
**Paragraph 2:** "At [previous company], I led the planning stack development for [platform]. Key achievements: [2-3 specific accomplishments with metrics]."
|
||||
|
||||
**Paragraph 3:** "I'm transitioning to humanoid robotics because the whole-body planning problem is the next frontier in motion planning. The challenge of coordinating locomotion and manipulation under contact constraints is where I want to build expertise."
|
||||
|
||||
### Mission Control (Secondary)
|
||||
|
||||
**Paragraph 1:** "I've spent the last 5 years building integrated autonomous systems, from perception to control. Your Mission Control role matches my experience architecting the orchestration layer that ties robotic subsystems together."
|
||||
|
||||
**Paragraph 2:** "At [previous company], I architected the flight software stack integrating perception, planning, and control. Key achievements: [specifics]."
|
||||
|
||||
**Paragraph 3:** "I'm interested in Hexagon because [specific reason about humanoid robotics and Zurich]."
|
||||
|
||||
---
|
||||
|
||||
## Gaps to Address
|
||||
|
||||
### For Motion Planning Role
|
||||
- **Legged locomotion:** Acknowledge gap; show learning plan (e.g., "Currently studying whole-body motion planning for legged systems through [resources]")
|
||||
- **Manipulation planning:** Highlight any arm/gripper experience; if none, show awareness of the domain
|
||||
- **Contact-rich planning:** New area; position as learning opportunity
|
||||
|
||||
### For Mission Control Role
|
||||
- **Behavior trees / SMACC:** Research and mention awareness
|
||||
- **Distributed systems:** Expand any multi-process/multi-node architecture experience
|
||||
|
||||
---
|
||||
|
||||
## Pre-Application Checklist
|
||||
|
||||
- [ ] Update CV with motion planning emphasis
|
||||
- [ ] Tailor summary for each role
|
||||
- [ ] Add specific bullet rewrites for planning/integration experience
|
||||
- [ ] Review LinkedIn profile alignment
|
||||
- [ ] Prepare cover letter points
|
||||
- [ ] Research Hexagon Robotics recent news for talking points
|
||||
- [ ] Prepare questions about team structure, technical stack, growth trajectory
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- Be honest about gaps; show learning trajectory
|
||||
- Concrete specifics > generic claims
|
||||
- Metrics and outcomes wherever possible
|
||||
- Tailor slightly for each role (motion planning vs mission control have different emphasis)
|
||||
|
||||
---
|
||||
|
||||
**Tags:** #job-hunt #cv #hexagon #career
|
||||
Reference in New Issue
Block a user