Five authors who work inside the companies selling this technology write a career book in three stretches: the landscape and what changes about work, a technical tour through architectures, retrieval over documents and agents, and finally career moves, the job search and sustained growth.
What I took from it
The map of roles, which is the valuable part. They separate, precisely, jobs the market blurs together: the person who builds systems around models, the one who researches, the one who defines product, the one who designs the conversation, the one who answers for risk and governance, the one who advises. Seeing the profiles apart, with the evidence each is asked for, organises a decision most people make by drift.
The shift from models to systems. The work stopped being about picking the model and became designing everything around it, which is where the pilots that never reach production fail. It is the sentence that best explains why an architect belongs in this at all.
And a point about the career ladder: if entry-level tasks get automated, the way you prove capability changes, and what is left is evidence you built yourself. That confirmed a priority I already had, which is publishing verifiable work instead of collecting certificates.
What I left out
The whole technical stretch. It is not bad, but it summarises subjects that have books of their own, and one chapter is not enough for any of them. And there is a bias worth keeping in mind: the career map they draw is the one that exists inside large technology companies, with their levels and their hiring pipelines. Translated to a market where you talk to the owner of the company, half that advice does not apply.