Saronic
Commissioning Assistant Engineer, Marauder
About this role
Support the Chief Engineer in commissioning and operating autonomous vessel systems, including propulsion, auxiliary machinery, and integration with autonomy software. Develop procedures, troubleshoot marine systems, and ensure compliance with maritime regulations in a novel operational environment.
What you'll do
- Lead commissioning activities for autonomous vessels including system testing, validation, and troubleshooting
- Verify integration between machinery control systems and autonomy stack across manned, remote, and autonomous modes
- Develop and refine standard operating procedures, checklists, and technical documentation
- Perform assigned maintenance on vessel machinery under Chief Engineer direction
- Manage spare parts inventory and ordering
- Provide on-call support to address shipboard issues during assignments
What they're looking for
- USCG MMC and OICEW/Advanced Firefighting endorsements
- Maritime engineering systems knowledge, particularly electrical systems
- Jet-drive marine engine experience
- Technical documentation and procedure writing
- Problem-solving and independent troubleshooting
- Cross-functional team collaboration
- STCW compliance and maritime regulations
- Systems integration with autonomy platforms
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Saronic
Saronic builds autonomous maritime systems and vessels equipped with advanced imaging, software, and electro-mechanical components. The company is hiring quality engineers, software engineers, graphics programmers, optomechanical engineers, and manufacturing engineers to develop and manufacture reliable autonomous maritime operations.
View all jobs at SaronicLikely interview questions
- Walk us through your experience with commissioning marine systems and how you've handled integrating traditional machinery with newer control technologies.
- Tell us about a time you had to develop operational procedures from scratch—how did you approach creating documentation for processes that didn't previously exist?