<?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 BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/interview/</link>
    <description>Recent content in Interview on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 16:51:00 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/interview/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What you need to know about the Gilded Rose interview problem</title>
      <link>https://www.bradcypert.com/what-you-need-to-know-about-the-gilded-rose-interview-problem/</link>
      <pubDate>Wed, 16 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/what-you-need-to-know-about-the-gilded-rose-interview-problem/</guid>
      <description>&lt;p&gt;A few years ago, I interviewed for a Dev Ops position at a pretty prominent CI shop in San Francisco. Part of the interview process involved a take-home code-assignment (of course). This particular assignment is known as the Gilded Rose.&lt;/p&gt;&#xA;&lt;p&gt;The Gilded Rose isn’t a fizzbuzz. It’s not “Implement a Trie” in whatever language you want. The Gilded Rose is a problem that involves adding some functionality into the worst code that a developer could ever write. I don’t mean any offense to whoever created the Gilded Rose problem, bad code is entirely the intention! They want to see how you work through a terrible codebase to add new functionality.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
