What’s the one concept that took you way too long to finally understand as an engineer?

What’s more dangerous: poor documentation or poor naming?

How much of your coding today is influenced by AI tools vs your own experience?

The best backend engineering feels invisible. And that’s the point. No one praises the API that works. Or the system that scales under pressure. Or the database that returns queries in milliseconds. But behind that simplicity? • Careful tradeoffs. • Thoughtful architecture.

How do you know you’ve “leveled up” as an engineer?

If LLMs become perfect at writing code, what part of engineering can’t be replaced?

You won’t always know why something broke. But as a backend engineer, you better know how to find out. Because something will break: • A deployment fails. • An API suddenly returns 500s. • A background job uses too much memory. Great ones will know how to debug anything.

Do you still manually write SQL queries or rely entirely on ORMs?

What’s one “best practice” you’ve seen backfire in real projects?

How does your company track if a software engineer is good or not?

What’s a popular software engineering best practice you disagree with?

What’s the most important quality of a senior engineer (that isn’t technical)?

Great backend engineers aren’t built overnight. They’re built through repetition, patience, and consistency. Everyone wants results. But few are consistent enough to earn them. Because in backend engineering, consistency is the cheat code.

If coding becomes 10x faster thanks to AI, what becomes the new bottleneck?

What’s one thing AI still can’t do that makes you valuable as a developer?

Good backend engineers build features. Great ones build confidence. Confidence that the system will scale. Confidence that edge cases are handled. Confidence that if something breaks, it won’t take the app down. Because backend engineering isn’t just about building what works.

Do you think daily standups actually help engineers get more done?

Do you think pair programming is actually helpful?

Most people don’t fail to learn backend engineering. They just never start. They wait for: • The “perfect” tutorial. • The “right” course. • More free time. But the engineers who grow? They start messy. Start small. But they start.

What’s the most underrated skill for a senior engineer?

If AI keeps improving, what will backend engineers focus on 5 years from now?

Do you think a 10x engineer is a myth or anyone can achieve this?

When I hire entry-level developers, I look for just 3 things: 1. Do you have strong backend fundamentals? 2. What past projects can you share? 3. Are you someone I’d want to work with every day? If you can demonstrate these, you’ll move on to the next round. It’s not about a perfect resume.

How do you balance deep work with meetings as an engineer?

Do you think remote work makes software engineers more productive, or more distracted?

Are microservices just another way of saying "over-engineering"? lol

If you had to build an MVP in 48 hours, what stack would you choose?

and now Grok 4 is the "smartest model in the world". The AI hype cycle continues. I'm sticking with Claude Code.

What is your best advice to a junior engineer trying to break into the industry?

Which language or tool do you think is overrated in software engineering?

What’s one coding tool you refuse to work without?

If you could only use one backend framework for the next 5 years, which would it be?

Average backend engineer: “I built the API endpoint. Now it’s the frontend team’s job to figure out how to use it.” Great backend engineer: “I collaborate with the frontend team to make sure the API is clear, efficient, and scales properly.” Creating great software is a team sport.

How do you decide it’s time to move on from a job as an engineer?

Do you think certifications (like AWS or Kubernetes) are worth it for engineers?

If you could only master one: system design or algorithms - what would you choose?

What’s one thing you wish you’d known before your first software engineering job?

What does coding look like 5 years from now?

Would you rather work at a startup where you wear many hats, or a big tech company where you go deep on one thing?

If you had to pick only one for your entire career: frontend, backend, or devops?

Should junior engineers focus on a single language/framework, or learn a little of everything early on?

How much has your daily workflow changed because of AI tools this year?

What measures a software engineer the best? System design or Leetcode?

Would you rather refactor legacy code all year or write greenfield code?

What’s more important in a growing team: clean code or shipping fast?

Now that AI and LLMs are a thing. Do you think people should still specialize into either frontend or backend?

If you could only have 1 which would you choose? Cursor or Claude Code?

A senior in one tech stack might feel like a junior in another. But their actual experience isn’t tied to a tech stack. It’s defined as being language-agnostic. When you are language-agnostic, learning a new language or framework is just a matter of weeks.

Pick one of these 8 coding concepts to read over the weekend (you won’t regret it): 1. CQRS. 2. HATEOAS. 3. Clean Code. 4. API Versioning. 5. SOLID Principles. 6. Clean Architecture. 7. Rate Limiting & Throttling. 8. Event-Driven Architecture (EDA). These concepts are in high demand.

Senior developers play a crucial role as mentors for their team. Their responsibility is to create an environment that encourages: • Growth. • Learning. • Creativity. The real magic happens when these three come together.