GNC Engineer III
maybe under About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location can be a short
. About the job you’re considering: paragraph describing solving challenging controls and localization problems etc. That's about the role. Then "Your Role:" bullet list of duties. Then "Your Skills and Experience:" list of qualifications/skills. Then compensation range: base compensation range $82,082- $193,440. Also mention variable incentives etc. Benefits: description of benefits package. We need sections: About the role (maybe combine location and description). Responsibilities (list of duties). Requirements (maybe education/experience). Qualifications (maybe similar). Skills (maybe programming languages). Benefits. Pay. Schedule (if any schedule info? Not present). So we should not include Schedule section because no info. We must not create sections with filler like "not specified". So omit Schedule. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Requirements and Qualifications? The instruction: prefer a few substantive sections over many thin ones. But we need to follow headings list: they gave examples but we can include only those with content. We could have About the role, Responsibilities, Requirements & Qualifications (maybe combine), Skills, Benefits, Pay. But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings exactly as given. We can decide to include each if we have content.
Let's extract content:
About the role: The introductory paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." plus location Mendon, Utah. Also "About the job you’re considering: Solve challenging controls and localization problems using state-of-the-art techniques. Develop simulations to prove controls designs. Work with a team of engineers to implement and validate controls solutions on unmanned ground vehicles (UGVs). Designs, develops, and supervises all aspects of electrical control systems, equipment, and machinery. May be responsible for the installation and technical support of controls products. Familiar with concepts, practices, and procedures within the GNC realm. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Relies on experience and judgment to plan and accomplish goals. Performs a variety of complicated tasks. May report to an executive or a manager. A wide degree of creativity and latitude is expected."
That's a lot; we can keep as prose.
Responsibilities: The "Your Role:" list items.
Let's list them:
- Design and develop controls and localization algorithms for ground vehicles.
- Model mechanical and electrical systems to simulate derived controls solutions.
- Aid in the testing and debugging of implemented controls solutions.
- Document designs and analysis in company report format.
- Synthesize controls solutions to problems of interest to the company.
- Simulate mechanical, electrical, etc. systems to verify derived controls solutions.
- Aid in the testing and debugging of implemented controls solutions. (duplicate? appears twice)
- Document important results in company report format.
- Advise and assist GNC Engineers as needed.
- Publish research in conference proceedings and journals.
- Provides technical leadership in the controls area.
- Assists in writing proposals that require controls solutions.
- Patent novel controls methods.
We should deduplicate duplicates: "Aid in the testing and debugging of implemented controls solutions." appears twice; we can keep one. Also "Document designs and analysis in company report format" and "Document important results in company report format" are similar but distinct; keep both.
Requirements: Education: Bachelor's degree in Mechanical Engineering, Electrical Engineering, Robotics, Automation Engineering, Computer Science, Information Technology, or a related engineering discipline.
Also maybe experience: Strong programming skills in C, C++, C#, Python, Visual Basic, and Microsoft embedded Visual C++. Experience with software development, object-oriented programming, and embedded systems development. Hands-on experience with robotics systems, robotics software, and ROS (Robot Operating System). Knowledge of automation, robotics, mechatronics, and industrial control systems. Experience working in engineering design, system integration, testing, and technical problem solving. Ability to collaborate with cross-functional engineering teams throughout the design, development, and implementation lifecycle.
These could be under Requirements or Qualifications. We'll split: Requirements = education + experience? Qualifications = skills? But we have Skills section separate.
Let's decide:
- Requirements: Education (Bachelor's degree ...) and maybe experience (software development, OOP, embedded, robotics, ROS, automation, mechatronics, industrial control systems, engineering design, system integration, testing, problem solving, collaboration). That's a lot.
- Qualifications: maybe not needed separately; but we could treat Qualifications as same as Requirements? To avoid thin sections, we could combine Requirements and Qualifications into one section called "Requirements". But the instruction says we can include sections only when posting has real specific content. It didn't forbid combining headings; but they gave examples of headings we can use. It didn't say we must use each heading exactly; we can choose to include only those we need. So we could have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That seems sufficient.
Skills: Strong programming skills in C, C++, C#, Python, Visual Basic, and Microsoft embedded Visual C++. (maybe also mention object-oriented programming, embedded systems development). But we already included programming skills in Requirements; we could move programming languages to Skills.
Better: Requirements: Education and core experience (robotics, ROS, automation, mechatronics, industrial control, engineering design, system integration, testing, problem solving, collaboration). Skills: Programming languages (C, C++, C#, Python, Visual Basic, Microsoft embedded Visual C++), OOP, embedded systems development.
Benefits: description of benefits package.
Pay: base compensation range $82,082- $193,440 plus note about variable incentives etc.
We must not include fluff like "commensurate with experience". The posting includes variable incentives etc; we can include that as part of Pay section.
Now produce HTML.
We need to wrap each section in heading then content: for prose use
, for lists use
- .
Location: we can include a short
after About the role heading maybe. Let's craft:
About the role
Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world.
Location: Mendon, Utah
About the job you’re considering: Solve challenging controls and localization problems using state-of-the-art techniques. Develop simulations to prove controls designs. Work with a team of engineers to implement and validate controls solutions on unmanned ground vehicles (UGVs). Designs, develops, and supervises all aspects of electrical control systems, equipment, and machinery. May be responsible for the installation and technical support of controls products. Familiar with concepts, practices, and procedures within the GNC realm. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Relies on experience and judgment to plan and accomplish goals. Performs a variety of complicated tasks. May report to an executive or a manager. A wide degree of creativity and latitude is expected.
Then Responsibilities:Responsibilities
- Design and develop controls and localization algorithms for ground vehicles.
- Model mechanical and electrical systems to simulate derived controls solutions.
- Aid in the testing and debugging of implemented controls solutions.
- Document designs and analysis in company report format.
- Synthesize controls solutions to problems of interest to the company.
- Simulate mechanical, electrical, etc. systems to verify derived controls solutions.
- Document important results in company report format.
- Advise and assist GNC Engineers as needed.
- Publish research in conference proceedings and journals.
- Provide technical leadership in the controls area.
- Assist in writing proposals that require controls solutions.
- Patent novel controls methods.
Requirements
- Bachelor's degree in Mechanical Engineering, Electrical Engineering, Robotics, Automation Engineering, Computer Science, Information Technology, or a related engineering discipline.
- Experience with software development, object-oriented programming, and embedded systems development.
- Hands-on experience with robotics systems, robotics software, and ROS (Robot Operating System).
- Knowledge of automation, robotics, mechatronics, and industrial control systems.
- Experience working in engineering design, system integration, testing, and technical problem solving.
- Ability to collaborate with cross-functional engineering teams throughout the design, development, and implementation lifecycle.
Skills
- Strong programming skills in C, C++, C#, Python, Visual Basic, and Microsoft embedded Visual C++.
Benefits
Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include:
- Paid time off based on employee grade (A‑F), defined by policy: Vacation: 12‑25 days, depending on grade.
- Company paid holidays.
- Personal Days.
- Sick Leave.
- Medical, dental, and vision coverage (or provincial healthcare coordination in Canada).
- Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada).
- Life and disability insurance.
- Employee assistance programs.
- Other benefits as provided by local policy and eligibility.
Pay
The base compensation range for this role in the posted location is: $82,082‑$193,440.
In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.
Note: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned, vested, or payable until it becomes due under the terms of applicable plans or agreements and is subject to Capgemini’s discretion, consistent with applicable laws.
We should not include Schedule section. Check for any boilerplate: we removed EEO, disclaimer, etc. We kept some compensation disclaimer but that's part of Pay section; it's substantive? It's a disclaimer about compensation; maybe we can keep as it's part