The Future of IT Jobs in India | Why I Won’t Force My Kids Into IT

Summary of Main Arguments / Commentary

• AI is already reducing headcount needs in IT work. The speaker cites community examples where teams using AI coding tools (e.g., Claude) complete work that would otherwise require 30–35 people, but is being done by ~8. Similar effects are mentioned for testing (e.g., a 5-person team doing work that could require 15 without such tools). The speaker argues this productivity impact is spreading across development, testing, and business analysis.

• Hiring demand is not growing proportionally. While AI increases output per worker, it does not create many new jobs, contributing to a market imbalance: high supply of candidates, weaker demand from companies.

• Companies are moving to an “AI-first” strategy, slowing hiring. The speaker claims companies can be selective (“pick and choose”), undercut offers, and slow down recruitment, making it harder for candidates to get even initial calls.

• This may be only the beginning. As software that generates software improves further, the speaker suggests the low-demand/high-supply problem will continue and intensify.

Recommended Responses / Actions

1. Differentiate yourself—your competition isn’t only AI tools, it’s other people.

   • Become a top-tier specialist in your role (project manager, tester, support, etc.).
   • Add industry/domain expertise (e.g., insurance, production, banking).
   • Learn and master the AI tools used by your company/client, so you’re not seen as resisting AI.
   • Strengthen communication and influence (confident speaking, defending opinions, negotiating).

2. Be financially cautious. Reconsider big purchases (especially luxury real estate) if they rely on expectations of future salary increases that may not materialize in a buyer’s market.

3. Do not push children into CS by default. Steer kids toward computer science only if there’s genuine interest and relevant skills, since the market for beginners may change by the time they graduate.

4. Diversify if both partners work in the same tech area. If one technology or domain becomes less valuable, both careers could be affected—so spreading specialties is advised.

5. Adjust expectations about salary jumps. Don’t assume frequent large raises via job changes; companies may negotiate harder when demand is low.

6. Build a larger safety net. Increase emergency reserves (e.g., aiming for ~1 year instead of 6–9 months), since job searches may take longer.

7. Avoid emotional, reactive decisions. Resolve workplace issues thoughtfully, take breaks, and avoid radical moves without strong financial security.

Presenters / Contributors

• The speaker/host (name not provided in the subtitles).