u/Tecr

Took this yesterday and wanted to write down my impressions while they’re still fresh, mostly for my own reference but figured it’s worth sharing since there isn’t a lot of detailed writeup out there yet.
Quick context: I have 4 to 5 years of experience working with AI systems, so take the difficulty rating with that in mind. I also use Claude Code to build production grade systems on a daily basis.

Overall difficulty
Moderately easy. Not a walk in the park, but noticeably easier than the Architect Foundations exam. If you’ve already cleared Foundations, my honest advice is don’t overthink it, just go straight for the Professional exam.
Roughly how the questions broke down for me:
• About 40% you’ll know the answer immediately, no real analysis needed
• The remaining 60% require you to actually read the full scenario paragraph carefully and think through the tradeoffs before answering

The trap to watch out for
A few questions are structured in a sneaky way. They’ll ask something like “what would you do at this step of the process” and then follow up with “what would you do before this process.” It’s easy to lose track of which process they’re actually asking you to evaluate your options against, since the actual process under discussion is usually stated in the first line of the question, not repeated in the follow-up. Read the setup line twice before you commit to an answer.

Topics that show up a lot
• Tradeoffs and use cases for MCP and other tool integrations, when to use an API directly versus wrapping it
• Agentic orchestration versus single-shot execution, and how to decide between them for a given workflow
• Few-shot versus single-shot prompting, including some scenarios that get fairly nuanced
• System decomposition, this comes up a lot and is worth being genuinely comfortable with
• Prompt design for production systems, not just “write a good prompt” but how prompts are structured and maintained at scale
• AI governance and how to apply it in practice, not just define it
• Architectural tradeoffs specific to highly secure or regulated environments

Bottom line
You need real architectural understanding of how these systems work end to end, but the exam doesn’t go as deep as Foundations does. If you’ve got production experience with agentic systems or RAG pipelines, you’re already most of the way there. The main things to actually study are the governance and security tradeoff scenarios, since those are less intuitive than the technical tooling questions.
Happy to answer questions in the comments if anyone’s prepping for this one.

And to everyone who asks why I took this- this is important in my field and it is important for me to certify my knowledge and my expertise with the certifications so that the clients that I work for understand that I am not only knowledgeable about my field, but I’m also interested in keeping up with the latest certification within my field.

Took this yesterday and wanted to write down my impressions while they’re still fresh, mostly for my own reference but figured it’s worth sharing since there isn’t a lot of detailed writeup out there yet.
Quick context: I have 4 to 5 years of experience working with AI systems, so take the difficulty rating with that in mind. I also use Claude Code to build production grade systems on a daily basis.

Overall difficulty
Moderately easy. Not a walk in the park, but noticeably easier than the Architect Foundations exam. If you’ve already cleared Foundations, my honest advice is don’t overthink it, just go straight for the Professional exam.
Roughly how the questions broke down for me:
• About 40% you’ll know the answer immediately, no real analysis needed
• The remaining 60% require you to actually read the full scenario paragraph carefully and think through the tradeoffs before answering

The trap to watch out for
A few questions are structured in a sneaky way. They’ll ask something like “what would you do at this step of the process” and then follow up with “what would you do before this process.” It’s easy to lose track of which process they’re actually asking you to evaluate your options against, since the actual process under discussion is usually stated in the first line of the question, not repeated in the follow-up. Read the setup line twice before you commit to an answer.

Topics that show up a lot
• Tradeoffs and use cases for MCP and other tool integrations, when to use an API directly versus wrapping it
• Agentic orchestration versus single-shot execution, and how to decide between them for a given workflow
• Few-shot versus single-shot prompting, including some scenarios that get fairly nuanced
• System decomposition, this comes up a lot and is worth being genuinely comfortable with
• Prompt design for production systems, not just “write a good prompt” but how prompts are structured and maintained at scale
• AI governance and how to apply it in practice, not just define it
• Architectural tradeoffs specific to highly secure or regulated environments

Bottom line
You need real architectural understanding of how these systems work end to end, but the exam doesn’t go as deep as Foundations does. If you’ve got production experience with agentic systems or RAG pipelines, you’re already most of the way there. The main things to actually study are the governance and security tradeoff scenarios, since those are less intuitive than the technical tooling questions.
Happy to answer questions in the comments if anyone’s prepping for this one.

And to everyone who asks why I took this- this is important in my field and it is important for me to certify my knowledge and my expertise with the certifications so that the clients that I work for understand that I am not only knowledgeable about my field, but I’m also interested in keeping up with the latest certification within my field.

To be clear, I’m a techie and I love to get my hands on new tech. I have been wearing smart watches for 12 years now with my first being the LG G Watch many years ago.

Quite recently, I wanted to only wear my nicer watches instead of my daily which was an Apple Watch Series 7 that I scratched up quite a bit. Now - look wise anyday, my stainless steel bracelet, Seikos and Tissots can’t be matched, however during this time I did miss my data and having the need to carry my Apple Watch in the bag to track my workouts.

So I felt, why not look into Fitbit Air which is a 99$ solution to well, most of my problems - no extra watch to carry, I get my data while still holding onto my nice watch. I saw the UI - turned away - looked at Whoop and the reviews from the user community here (not the ones in which someone is crying about how bad it is because I feel people more likely are to complain than write something nice about it) and got a Whoop.

First off - if you’re complaining about the price or the subscription, this is probably not for you. It is also something major to be able to look over as a lot of my friends and colleagues found it weird that I’m paying for something I don’t own while also not getting much more out of it, well that’s up to me but anyway.

Now the second and final part - my experience. I wore it everyday, except the shower, and I found results to be interesting. A lot of the reading is very much depending on the HRV, which the Apple Watch or any of my previous watches never pointed out to me but in reality it’s telling you how you feel based off mainly your HRV. HRV go down -> no good. HRV go up -> good. Other than that I failed to see how it could really add any value to my life (or at least 250$/y of value).

For my workouts - it was mostly useless and told me to keep it to a certain strain which is a bit hard to quantify for the human mind. The muscle strain feature is nice but to actually get value out of it you’re going to have to work with something which isn’t very intuitive to work with in the first place.

For my swim, it is just a glorified heart beat tracker since my Apple Watch was doing most of the heavy lifting with the laps and tracking.

For running, it doesnt have a GPS so it can only really tell you how much of your body battery you used up, which then again, is really depending on how much I ate before or after.

For sleep, unless you’re partying hard every night or have insomnia I think it mostly records that you had a good sleep. Minus if you drink or have a hard day, which I could predict without the watch telling me anyway.

All in all, the value that I was looking for - was genuinely not there, and if there was any at all, I could get it from a 99$ Fitbit Air that does all of the above without a lock in.

All of the other gimmicks packed in, it might be a package for someone. Healthspan isn’t going to do you much as it’s hard to believe that I cut a year off of my actual age within a week of training.

I think in the current market, it’s tough for a company like Whoop but there’s a lot more corelations they need to be making to bring a real valuable unit.

Oh and a bonus - the AI is completely dumb.

It was a nice learning experience but I think I’ll live without one just as happily with my old Apple Watch for workouts.