<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HackerRank on Dylan's Log</title><link>https://j75689.github.io/blog/tags/hackerrank/</link><description>Recent content in HackerRank on Dylan's Log</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 25 Oct 2026 15:00:00 +0800</lastBuildDate><atom:link href="https://j75689.github.io/blog/tags/hackerrank/index.xml" rel="self" type="application/rss+xml"/><item><title>Deleted, Yet Still There: Notes from HackerRank Orchestrate</title><link>https://j75689.github.io/blog/posts/hackerrank-ghost-data/</link><pubDate>Sun, 25 Oct 2026 15:00:00 +0800</pubDate><guid>https://j75689.github.io/blog/posts/hackerrank-ghost-data/</guid><description>&lt;p&gt;I recently joined HackerRank Orchestrate (October 2026), a 24-hour challenge. It was my first time, and all I knew beforehand was that agent-assisted coding was allowed, which felt pretty novel. The problem was called &lt;strong&gt;Ghost Data Still Exists&lt;/strong&gt; (&lt;a href="https://github.com/interviewstreet/hackerrank-orchestrate-october26"&gt;challenge repo&lt;/a&gt;). The setting is a commerce platform: a user asks for their account to be deleted, the deletion workflow reports &amp;ldquo;complete&amp;rdquo;, but their data is still scattered across database replicas, logs, support attachments, search indexes, the analytics platform and backups. Worse, some sync jobs and backup restores write deleted data back.&lt;/p&gt;</description></item></channel></rss>