25 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You split time between lab work, meetings with optical designers or telescope teams, and software development. Mornings often run experiments: align deformable mirrors, measure wavefront errors, and run control loops on Linux machines.
Afternoons go to data analysis in Microsoft Excel or C++ code review on GitHub, updating SolidWorks or AutoCAD drawings for mounts, and planning resources or schedules with management. You also write short reports or PowerPoint slides for clients or stakeholders.
Expect engineering CAD like Dassault Systemes SolidWorks and Autodesk AutoCAD for mechanical parts and mounts. For data and small databases you’ll use Microsoft Excel and sometimes Microsoft Access.
Control and simulation code is typically in C++ running on Linux, with version control on GitHub. Presentations and reports use Microsoft PowerPoint and Office.
Study optics and control theory in courses or textbooks, and practice C++ on Linux. Build small projects: control a mirror with feedback, log data into Excel, and store configs in files or Access.
Learn SolidWorks and AutoCAD by modelling mounts and lenses. Join an optics lab or hobby telescope group to see real systems, and contribute code to GitHub to show project history.
BLS (U.S. Bureau of Labor Statistics) reports for optical engineers and related occupations list a median pay around $102,440 per year, with the bottom tenth near $74,370 and the top tenth near $159,860. The BLS also estimates about 365,740 employed in related fields.
Actual pay varies by employer (university, observatory, defense, industry), location, and experience. Use the BLS numbers to get the range, then check job listings in your city.
You can use AI to prototype C++ snippets, generate documentation, or draft test procedures, but always review outputs. Control code for deformable mirrors and safety-critical routines must be tested extensively on hardware; an AI suggestion can contain subtle bugs.
For CAD and system requirements, use AI to speed routine work but validate every dimension and interface in SolidWorks/AutoCAD. Treat AI as an assistant, not a final engineer.