Interviews
Post #1153 · source on Telegram
Tech interviews demand algorithms, daily job fixes README typos and forms
Description
Image is a black-background screenshot of a tweet from user “CATALIN PIT 💡🚀 @catalinmpit”. The tweet is split into two sections in white sans-serif text. First section, labeled “Tech interview:”, lists four bullet points: “Dynamic Programming”, “Dijkstra Algorithm”, “Linked Lists, Stacks, Queues, Binary Trees”, and “10 hard LeetCode questions”. Second section, labeled “Day-to-day job:”, lists four bullets: “Fix typo in README”, “Center the form”, “Fix the Twitter icon link”, and “Add secret_key”. The meme highlights the mismatch between algorithm-heavy technical interview questions and the comparatively mundane tasks most engineers handle in production codebases, a common gripe among experienced developers
More like this
More like this in Interviews →
Use J and K for navigation
Comments
6Comment deleted
We whiteboard Dijkstra to vet candidates, then hand the survivor a P1 to center a flexbox - because the real shortest path is through three layers of legacy CSS and one designer’s ego
After 20 years, I've implemented Dijkstra's algorithm exactly once - to find the shortest path between my desk and the coffee machine while avoiding the open office "quick sync" ambush zones
After grinding 500 LeetCode hards and memorizing every graph traversal algorithm known to computer science, you'll finally land that dream job where your most intellectually challenging task is determining whether `margin: 0 auto` or `text-align: center` is the appropriate solution. The Dijkstra algorithm you studied? Perfect for finding the shortest path between your desk and the coffee machine when the PM asks you to 'just quickly' adjust that button padding by 2 pixels
Interviews demand Dijkstra for shortest paths; reality's the infinite loop of pixel-perfect icons and leaked secrets
Interviews want Dijkstra in O(E log V); the job’s shortest path is Jira → README, detouring through CSS specificity hell to center a form while rotating a secret_key without tripping prod
We whiteboard Dijkstra; in production the shortest path is through IAM, Terraform, and CI to add a secret_key - then git bisect why centering the form broke the Twitter icon