Vigyata.AI
Is this your channel?

Will AI Replace My Job as a Software Engineer?

710 views· 30 likes· 12:24· Jun 9, 2024

🛍️ Products Mentioned (1)

As a software engineer do I feel like my job is slowly being replaced by AI? Do I feel future proofed and how has my role as a software engineer change as a result? Follow me on IG: @techwithluca Brand/Collab Email: techwithluca@gmail.com 📌 Software Engineer Tech Essentials: https://tinyurl.com/bdhywpj4 tags: future of software engineering with ai,software engineering 2024,software engineering day in the life,How Did Generative AI Change My Role As A Software Engineer,highest paying jobs in tech,tech jobs without coding,career in tech,learning to code,how to get into tech,non coding tech jobs,should I work in tech,should i become a software engineer,how to work in tech,working in tech industry,non technical interview questions,tech roles that dont require coding Disclaimer: This video is not officially endorsed by the employer. The views, opinions, and experiences expressed herein solely belong to the subject and do not represent those of the employer. 00:00 Intro 02:17 What is my day to day like now? 05:12 Focusing on product quality 06:13 UNIT TESTING made easier 07:50 Do I feel like my job is future proof? 11:39 TLDR and summary

About This Video

In this video I break down the honest question a lot of us have right now: “Will AI replace my job as a software engineer?” I’m a full-stack engineer at a big company, and I’ve watched generative AI go from a hype train to something that actually changes my day-to-day. Internally, we use our own ChatGPT/Copilot-style tooling (a lot of big companies do this because they don’t want to expose their codebase), and I use it constantly—especially in VS Code for code completion, boilerplate, and even documentation. The biggest shift is that I’m still writing code, but I’m spending less energy on repetitive setup and more energy on product quality: UI/UX decisions, edge cases, data modeling, and architectural design. I’ll prompt for a React component or an API pattern, then I review it like an engineer—not blindly copy/paste—because the output quality depends heavily on how you describe the problem. The other huge win is unit testing: I can paste a function and ask for Jest tests, then refine the structure to match real scenarios. Do I feel “future-proof”? Not magically. The tools boost efficiency, but expectations and stress go up too, and the models still aren’t at the quality bar of a strong engineer. My takeaway: AI makes good engineers more powerful, and the differentiator becomes judgment—scalability, maintainability, and what matters long-term.

Frequently Asked Questions

🎬 More from Tech with Luca