← Back to Directory

Anchorage Digital

Mid-sized

Screna has 3 Anchorage Digital interview write-ups. The most reported round is the technical phone screen (3).

3 interview notes · updated Jul 2026

Anchorage Digital·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed at Anchorage Digital for a backend or software engineering role. The technical round was basically one meaty design problem about building a leaderboard, which sounds straightforward but has a lot of moving parts once they start asking about complexity and real-world scale.
  • Design a leaderboard system that supports score updates, top-k retrieval, element deletion, and rank lookup. Walk through the data structures you'd use, time and space complexity, and any real-world optimizations.

“I went with a sorted set approach pretty quickly, something like a balanced BST or a skip list under the hood, which covers most operations in O(log n).”

View Post

Anchorage Digital·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Anchorage Digital and got a coding question around implementing a print method for a custom file system. Pretty focused on how you model and traverse the data structure.
  • Implement a print() method that displays the entire file system in its current state, where each block is shown in sequence (e.g. [] -> [] -> [] for three empty blocks).

“The output format made it look simpler than it was.”

View Post

Anchorage Digital·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a Software Engineer role at Anchorage and got a coding question about implementing a print method for a toy in-memory file system. Pretty self-contained problem but there were a few edge cases worth thinking through carefully.
  • You're given a simple in-memory file system represented as an ordered list of disk blocks, where each block holds zero or more file records. Implement a method that prints the current state of the file system: blocks in order, each wrapped in square brackets, contents comma-separated, and blocks joined by ' -> ' with no trailing arrow.

“The core logic isn't hard but I spent a minute overthinking the joining part.”

View Post