20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You’ll split time between design, testing, and meetings. Morning might be schematic work in AutoCAD or Visio, writing C++ or Java test code, then running hardware tests in the lab.
Afternoons are often prototype checks, recording test data in Excel, reporting results, and coordinating with manufacturing or firmware teams on Git and Linux systems.
Use AI to draft ideas or generate test scripts, but never let it replace verification. Always review generated schematics, code, or test plans against engineering principles and safety standards.
Keep sensitive schematics out of public tools. Use approved, local AI tools or enterprise accounts with access controls, and store final data and results in secured systems (Git, company servers).