<?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 Professional Blog</title><link>https://alister.github.io/tags/interview/</link><description>Recent content in interview on Professional Blog</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Sun, 03 May 2026 15:56:49 +0100</lastBuildDate><atom:link href="https://alister.github.io/tags/interview/index.xml" rel="self" type="application/rss+xml"/><item><title>A Good Tech-Test Interview</title><link>https://alister.github.io/blog/2026/good-tech-test-interview/</link><pubDate>Sun, 03 May 2026 15:56:49 +0100</pubDate><guid>https://alister.github.io/blog/2026/good-tech-test-interview/</guid><description>A couple of days ago, I had a second interview for a job - after an initial conversation with a tech-lead of the company. I wanted to write a post about it, and praise it as a really good example.
What makes it good is that it wasn&amp;rsquo;t just a pop-quiz about things, and certainly not a leetcode style coding test, but with some real code that the company uses, and that the job deals with on a pretty much daily basis at the core of the company.</description></item></channel></rss>