In partnership with
What skill should you learn in 2026?
How do you find the answer?
Should you ask ChatGPT…
An AI influencer…
A random guy on Reddit…
Or me, your second favourite tech creator?
My answer: none of the above. Remember, we are all strangers who say things based on our own interests.
But I do know a reliable source to get the answer (assuming your goal of learning to code is to get a job as a developer)
Which is… drum roll...
The JOB BOARDS.
Almost every job listing gives you a list of skill requirements.
I actually haven't been through them for a while, so let's go through a couple together:
DISCLAIMER: I'm browsing the job listing website in my country. Your country's situation might differ. In fact, they might not want humans anymore. Who knows.
The keyword I searched is "Software engineer."
First one we have...
Senior Software Engineer
Skills:
Building client-facing web-based applications using multiple software development process models (e.g., Agile, Prototype, Iterative, Waterfall) and following the SDLC for web apps.
Utilize best and scalable development tools such as Amazon Web Services, Kubernetes, Docker, Spring, Node.js, RDBMS, MongoDB, and others as driven by the commercial needs of the business.
Leverage existing open-source frameworks/APIs, build new APIs, and create system architecture to implement business logic, including integration with databases for data management.
Entrepreneurial, self-motivated, passionate, resourceful, and driven to satisfy the needs of the customer.
Weird, don't see Loop Engineering in this list. Maybe this company still uses fax machines.
Here comes the next:
Software Engineer (Equity-based)
Skills:
Architect, build, and maintain the Buddy Flutter application for iOS and Android.
Establish the mobile codebase standards: architecture patterns, state management, testing, and code review practices.
Implement UI from design files at high fidelity and build a reusable, documented design system across mobile and web.
Build and maintain web frontend surfaces in TypeScript/React.
Build and integrate backend APIs supporting app functionality.
Own the full release pipeline: CI/CD, versioning, store submissions, and post-release monitoring.
Instrument the product for analytics and user feedback, and use that data to inform what gets built next.
The rest of the listings look similar.
I’m actually surprised by how little the requirements changed and how rarely AI skills are mentioned. After some digging, I finally found some one-line requirements in some jobs:
Use AI coding assistants (E.g., GitHub Copilot, ChatGPT, Claude) to accelerate development and improve code quality.
Proficient in AI development tools and vibe coding practices to boost development speed, streamline implementation and iterate solutions efficiently while maintaining consistent code quality and standards. (I have no idea what this means)
With that said. There is a brand new job title called AI engineer, which essentially is a mix of Machine Learning + SWE, which usually includes skills like Python, APIs, ML frameworks, AWS, RAG, etc.
If this is your thing, by all means go for it.
But for everyone else, what do you need to know about the skill you need to learn?
Well, basically the same web technologies companies have been using for the last ten years.
What about AI?
When the recruiter asks you what AI coding tools you use, just answer this:
I'm an AI expert who is proficient in all major AI coding tools, including Copilot, Gippidy, and Claude.
And watch some Fireship videos the day before the interview.
You will probably be fine.
- Fee from Anime Coders
PS: I wanted to write this article because lots of people are feeling lost because of how fast technology is moving. Also, I’m not even sure what I cover is valuable anymore. But now I think I have the answer to that. Hopefully you have yours too.
For product teams moving at AI speed.
AI makes it easier to ship anything, even bad ideas. The hard part is knowing which ideas are worth building.
Jira Product Discovery brings your ideas, customer insights, and priorities into one place, so your team can decide what to ship and move forward with confidence.
Capture ideas, prioritize with evidence, and build living roadmaps your team can rally around—all while staying connected to delivery in Jira, so everyone can see what’s being built and why.
Better product decisions in the AI era.
