What the work actually involves

This is authoring work, not production design. You write realistic engineering problem statements — a bracket redesign under a given load case, a feeder protection coordination study, an airfoil trade at a fixed Reynolds number — and then solve them yourself to a documented, reproducible standard. Each task needs explicit inputs, stated assumptions, constraints, operating conditions, output metrics, and acceptance criteria that a grader (human or model) can apply without guessing. A meaningful share of your hours will be spent reviewing other engineers' submissions: checking whether their mesh, time step, boundary conditions, or convergence claims actually support the number they reported.

The posting is worded around electrical engineering in places and CAD/simulation generally in others; in practice the project spans all three domains and staffing is by specialisation. Tool coverage is deliberately broad, including open-source stacks — FreeCAD, CalculiX, Gmsh, ParaView, OpenFOAM/SU2, XFoil, AVL, OpenVSP, OpenRocket on the aero/mech side; KiCad, ngspice, Qucs-S, FEMM, openEMS on the electrical side — alongside commercial tools such as CATIA, SolidWorks, ANSYS, Maxwell, COMSOL, Altium, ETAP, PowerFactory, PSCAD, OpenDSS and LTspice/PSpice. Python or MATLAB scripting for automation and result processing is preferred rather than required.

What the screen is looking for

Turing's stated bar is 10+ years in CAD engineering and simulation-focused organisations, with deep practical expertise in at least one specialisation rather than shallow familiarity across many. Expect the screen to push on specifics: which solver, which element formulation, how you validated a result analytically before trusting it, and what you did when the simulation and the hand calculation disagreed. Engineers who describe tools they have watched colleagues use tend to surface quickly under follow-up. A PhD in mechanical, electrical, or aerospace engineering and prior work at recognised aerospace or engineering firms are listed as preferred, not mandatory.

Logistics

  • Contractor assignment, 8 weeks, with an expected start the week after selection
  • Minimum 20 hours/week, up to 40, with at least 4 hours of daily overlap with US Pacific time
  • Remote and largely asynchronous outside the overlap window; no medical or paid leave
  • Pay band is not disclosed in this listing; Turing sets rates by domain and seniority and discusses them during screening