<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Certification on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/certification/</link><description>Recent content in Certification on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 29 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/certification/index.xml" rel="self" type="application/rss+xml"/><item><title>My 4-Step Study Plan for Passing the AWS Solutions Architect – Associate</title><link>https://severinbucher.com/posts/my-4-step-study-plan-for-passing-the-aws-solutions-architect-associate/</link><pubDate>Mon, 29 Sep 2025 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/my-4-step-study-plan-for-passing-the-aws-solutions-architect-associate/</guid><description>&lt;p>As a web engineer doing full-stack work, I&amp;rsquo;ve spent years inside the AWS ecosystem. EC2, DynamoDB, Redis, Lambda, API Gateway, and S3 are part of my daily toolkit. I was comfortable building and deploying on them, but I also knew there was a lot of AWS I&amp;rsquo;d never touched and a lot of architectural reasoning I&amp;rsquo;d never had to do explicitly.&lt;/p>
&lt;p>So this year I set myself a goal at work: pass the AWS Certified Solutions Architect – Associate exam. I wanted to go deeper on the services I only knew at the surface and get better at designing whole systems rather than wiring up the parts I already knew. I passed the SAA-C03 on my first attempt with a score of 903/1000, and this is the plan that got me there over about nine months.&lt;/p></description></item></channel></rss>