<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Interview on Ricky</title><link>https://linzeyan.github.io/categories/interview/</link><description>Recent content in Interview on Ricky</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 22 Dec 2025 08:40:00 +0800</lastBuildDate><atom:link href="https://linzeyan.github.io/categories/interview/index.xml" rel="self" type="application/rss+xml"/><item><title>Rainman Engineering Culture: Eight Interview Questions to Spot Excellence</title><link>https://linzeyan.github.io/posts/2025/20251222-rainman-eng-culture/</link><pubDate>Mon, 22 Dec 2025 08:40:00 +0800</pubDate><guid>https://linzeyan.github.io/posts/2025/20251222-rainman-eng-culture/</guid><description>&lt;ul>
&lt;li>&lt;a href="https://deusyu.app/posts/rainman-eng-culture/" target="_blank" rel="noopener">Rainman Engineering Culture: Eight Interview Questions to Spot Excellence&lt;/a>&lt;/li>
&lt;/ul>
&lt;ol>
&lt;li>CI/CD tools: collaborative GitLab/GitHub, or gate-heavy Gerrit/Jenkins?&lt;/li>
&lt;li>Approval flow: how many boss sign-offs does a merge request (MR) need?&lt;/li>
&lt;li>Environment isolation: separate Dev/Test/Prod environments, and can you switch/deploy with one click?&lt;/li>
&lt;li>Deployment chain: from code to user-visible, how many steps? Automated or manual?&lt;/li>
&lt;li>Monitoring: do alerts point to root cause, or are engineers digging through logs at night?&lt;/li>
&lt;li>Config management: centralized with canary/gradual release, or scattered across code with manual edits?&lt;/li>
&lt;li>Test coverage: a reliable automated &amp;ldquo;immune system,&amp;rdquo; or treat bugs as features and let users test in production?&lt;/li>
&lt;li>Rollback: when production blows up, can you roll back within 5 minutes, or stay up all night with the team?&lt;/li>
&lt;/ol></description></item></channel></rss>