<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hiring on F. Latini - IT Engineer</title><link>https://latini.dev/tags/hiring/</link><description>Recent content in Hiring on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 01 Oct 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/hiring/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Platform Team Is Hiring for Year One</title><link>https://latini.dev/posts/your-platform-team-is-hiring-for-year-one/</link><pubDate>Thu, 01 Oct 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/your-platform-team-is-hiring-for-year-one/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Almost every platform team I meet is hiring against the job description it wrote when the team was founded: Kubernetes, Terraform, a cloud certification, &amp;ldquo;built X from scratch&amp;rdquo;. That loop selects for one thing, the ability to build infrastructure, which is exactly what year one needed and exactly what a mature platform team already has too much of. By year two the work is mostly product judgement, support that shrinks itself, teaching, migration programmes and running a production service for internal customers, and none of that is in the interview. The result is a team of excellent builders doing a job that is mostly not building, and quietly inventing builds to stay sane. The fix is not a unicorn hire. Write the job description from last quarter&amp;rsquo;s calendar instead of last year&amp;rsquo;s ambition, test for the skills the calendar actually needs, hire some of your platform engineers from among your users, and change the career ladder so the unglamorous work is promotable. Otherwise the ladder will undo every hire you make.&lt;/p&gt;</description></item></channel></rss>