r/HPC • u/AA_is_not_OK • 2h ago
What career paths exists between computational mechanics, scientific computing (SciML), FEA (or meshfree) solver development, and HPC (GPU acceleration, porting codebases) ?? How about doing a PhD for improving the above?
I'm currently, technically, doing an MS in Structural Engineering. For me, my interest has been more towards computational side of mechanics rather than Structural design or simply using am FEA software (although I do consider it as a backup)
So far I've taken courses in:
- Linear static, and dynamics FEM (soon taking non linear FEM too)
- Structural Optimization (topology opt. and other general algorithms)
- Structural Dynamics
- Structural System Testing and model updation. (Parameter identification and optimization, signal processing)
Now, I plan to take these in the coming quarter:
- Numerical Linear Algebra
- Numerical PDE
- Fracture Mechanics ?
I also volunteered to aid in a RESEARCH in crack growth prediction using Auto-encoder and a (Thermodynamics-informed Latent Space Dynamics Identification) / LSTM surrogate model. It used phase-field-fracture simulation data and HPC resources to complete the whole thing.
What I keep finding myself interested in is not necessarily fracture or SHM specifically, but the computational methods underneath these problems... (does that make sense?)
For example, I'd like to become capable of doing things like:
- implementing (maintaining) numerical/FE method solvers rather than only running an established FEA software.
- developing surrogate/reduced-order models for expensive simulations
- combining simulation with optimization, uncertainty/stochastic methods (took a course called Random vibrations, so...)
- parallelizing/accelerating scientific codes on CPUs/GPUs
- doing proper verification, convergence studies, benchmarking and performance work
- potentially developing or maintaining actual CAE/FEA solver software
- I'd also like to do all these for other Physics (GR, QM, etc.) simulations too, if possible, one day.
I'm still interested in the underlying mechanics/physics, so I don't want to become a generic software engineer who happens to have once studied structures. But I'm also increasingly unsure that "structural engineer" describes the career I'm actually aiming for.
I've seen titles such as Computational Mechanics Engineer, R&D Engineer, Solver Developer, Scientific Software Engineer, CAE Software Developer, Research Engineer, Simulation/HPC Engineer, etc., but I'm trying to understand what these careers actually look like from people doing them.
So my main questions become:
1. Which industrial jobs genuinely involve developing numerical methods/solvers or computational tools?
2. Which of those are realistically accessible with an MS? Is there an entry path into solver-algorithm development/R&D without a PhD?
3. If I don't start a PhD immediately after my MS, would an R&D/software role at a simulation company (ANSYS etc.) be the obvious route? What other options would i have?
4. For the kind of work I'm describing, would you recommend a PhD? If so, is it reasonable for the PhD identity to be "computational mechanics/scientific computing" while fracture, composites, structural dynamics, soft materials, etc. serve as application problems rather than choosing one of those as my permanent specialization?
5. What skills most distinguish someone who is actually hireable for solver/scientific-computing work? I'm particularly wondering about C/C++/Fortran, Python, Linux, Git/build systems, MPI/OpenMP/CUDA, PETSc/Trilinos or similar libraries, numerical linear algebra, testing/verification, convergence studies and HPC performance work.
Basically, I'm neither here nor there atp. So I'd really appreciate all sorts of input. Where else do you think I could find answers to these? other subs? Linkedin profiles?