Interviews
Post #3383 · source on Telegram
When “hard worker” means making every single task unnecessarily difficult
Description
The image is a screenshot of a tweet UI that shows a retweet banner reading "Nathan Usher Retweeted." Beneath it is the profile of Nathan Usher (@thenatewolf) with a small gray wolf icon howling at a yellow moon and a blue verification badge. The tweet text reads: "Interviewer: would you call yourself a hard worker?" followed by a line break and "Me: absolutely. I make almost everything harder than it has to be." A faint timestamp ("23/10/2016 00:48") appears at the bottom. The humor relies on self-deprecation and a pun on “hard worker,” poking fun at developers who over-engineer or complicate tasks - an all-too-common theme in technical interviews and hiring conversations
More like this
More like this in Interviews →
Use J and K for navigation
Comments
7Comment deleted
Hard worker? I containerised a cron job, wired it through Kafka, and wrote a 20-page ADR to justify the architecture - just so marketing could run grep once a day
The real hard work isn't implementing the solution - it's convincing the team why your custom-built, microservice-based, event-sourced, CQRS pattern with blockchain audit trail is absolutely necessary for what could have been a simple CRUD app with a Postgres database
This perfectly captures the senior engineer's curse: we've seen so many edge cases and architectural disasters that we instinctively add three layers of abstraction, implement the Strategy pattern, and write a custom DSL for what could've been a simple if-statement. We're not just hard workers - we're hard-mode workers, turning every JIRA ticket into a distributed systems problem
Absolutely - like deploying Kubernetes for a static site, complete with Istio and blue-green rollouts no one needs
Interviewer: “Are you a hard worker?” Me: I once turned a 5-line cron into a multi‑region, event‑sourced microservice with Kafka and a Helm chart - accidental complexity is my cardio
Asked if I’m a hard worker, I said I can turn a one-line Bash script into a hexagonal, event‑sourced CQRS microservice with Kafka and Terraform - then ship it as the MVP
This Comment deleted