<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Career on Alex Here - Blog</title><link>https://blog.alexhere.me/tags/career/</link><description>Recent content in Career on Alex Here - Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Apr 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://blog.alexhere.me/tags/career/index.xml" rel="self" type="application/rss+xml"/><item><title>What I Learned About Infra Interviews Last Weekend</title><link>https://blog.alexhere.me/2026/04/14/what-i-learned-about-infra-interviews-last-weekend/</link><pubDate>Tue, 14 Apr 2026 10:00:00 +0700</pubDate><guid>https://blog.alexhere.me/2026/04/14/what-i-learned-about-infra-interviews-last-weekend/</guid><description>&lt;p&gt;Last Saturday I met up with a senior of mine who&amp;rsquo;d been grinding away at their infrastructure interview prep. We chatted and he started walking me through what he&amp;rsquo;d been studying—different scenarios, real interview questions he&amp;rsquo;d encountered, the whole process.&lt;/p&gt;
&lt;p&gt;I was honestly surprised by how realistic everything was. These weren&amp;rsquo;t textbook &amp;ldquo;what is TCP&amp;rdquo; questions. The scenarios had constraints, trade-offs, incomplete information. Just like actual industry production.&lt;/p&gt;
&lt;p&gt;What hit me hardest was realizing how hard this actually is. I&amp;rsquo;d assumed infra interviews were about knowing your tools and protocols. But watching my senior work through these scenarios, I saw how much it demands—systems thinking under pressure, knowing what to ignore and what to investigate first. It&amp;rsquo;s not just knowledge. It&amp;rsquo;s judgment.&lt;/p&gt;</description></item></channel></rss>