I just fumbled a casual interview with an organization a few hours ago.
It exposed a brutal truth:
Being technically competent is no longer enough by itself.
AI has changed the "developer skillsets". It's becoming less about how fast you can write code or how much syntax you can recall and more about how well you can:
- Understand the problem
- Define clear requirements
- Architect the solution
- Use AI agents to implement it
- Review and validate the output
I was unable to impress my interviewer bcs I hadn't gone a step further by having a concrete agentic workflow to show them. A developmet workflow with AI so deep at it's core that most the work is automated and executed by agents.
I was unable to show them proper usage of agent skills, not the generic ones that come pre-written and budled as part of the cofigs of your AI IDEs, but mine, customized to my own specific needs.
I tried covering this up by talking about my private agent-resources github repo that has md files explaining how I build my nextjs apps, how I setup my services and repositories as factory functions with zod schemas and mappers to normalize db and input data and that my cursor has access to this github repository and uses a reference for my projects...
But that wasn't enough.
I believe I gave them the impression that I care abit too much about syntax and that smells of "Arcade programming which implies Slow delivery" in this AI era.
You see the pose in the cover photo above ? that's exactly how I sat down thinking about this.
That's the part I'm now paying more attention to.
I wrote a full breakdown on my blog. Link in the comments.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.