So I'm currently working as a junior full stack dev in Chicago and I've been really thinking about switching over to AI engineering within the next 6 or 8 months. My math skills are pretty much stuck at high school level plus maybe a bit of logic from my CS degree, which honestly wasnt that math heavy to begin with. Ive been doing some digging online and the advice is all over the place which is making me kinda anxious about where to spend my time.
I read on some subreddits that if you dont understand multivariable calculus and linear algebra inside out you'll never survive a real interview at a place like Google or Meta but then I see these roadmap videos on YouTube that basically say you just need to know how to call APIs and use high-level libraries like Keras or PyTorch. It's super confusing because I dont want to waste three months studying derivatives if I'm just gonna be tuning hyperparameters all day. I have about $500 saved up for a bootcamp or some courses but I dont want to blow it on a theory-heavy thing if it's not actually what people use in the field every day. Like do you actually solve equations on the job or is that just for researchers? How much of that deep math do you actually use when youre building stuff for real clients...
Honestly, the massive gap between what companies ask for in interviews and what we actually do daily is pretty frustrating. I spent a fortune on high-end theory courses early on and frankly, it was mostly a waste for the engineering side of things. Most people unfortunately end up in one of two extremes: either they are just API wrappers who dont understand why their model is failing, or they are math wizards who cant write production-ready code. Based on my experience building production pipelines, here are two tips to keep you from wasting your $500:
Saw this earlier and had to jump in because your enthusiasm for switching is amazing! Quick question though, are you looking to build models from scratch or mostly integrate existing ones? Knowing the math behind weights helps you debug when your loss function goes crazy—it's a fantastic safety net so you dont break things in production! I'd grab Manning Publications Grokking Machine Learning Luis Serrano since it's super cost-effective.
> do you actually solve equations on the job or is that just for researchers? Adding my two cents here because i remember getting burned hard on a computer vision project last year. Thought i could just wing it with basic scripts, but my model kept exploding because i didnt account for certain probability distributions in the training data. Be careful with those just call the API roadmaps. If you dont get the underlying statistics, you wont know why your model is failing in production. My advice is to focus on probability and statistics more than calculus tbh. For a solid middle ground, Pearson Mathematics for Machine Learning Marc Peter Deisenroth is a lifesaver when you need to debug a custom loss function. You might want to consider that you'll be dealing with data shapes constantly. If your matrix dimensions dont align, PyTorch throws a fit and you need linear algebra to speak its language. Dont blow that $500 on a generic bootcamp yet, maybe try a targeted program like Coursera Deep Learning Specialization Andrew Ng first.