How Can I Find Tech Work That Still Involves Real Coding?

If you want maximum hands-on work, look for teams building infrastructure, embedded systems, developer tools, databases, networking software, or performance-sensitive backend services. Those areas tend to require more direct coding and understanding of how systems behave, although no job can guarantee that every project will stay free of automation.

You may need to separate what you do for work from what you do to keep growing technically. Build substantial side projects without relying on AI, create your own development environment, and use them to practice the concepts you care about. That can also give you a portfolio for moving into a more hands-on role later.

It’s also worth being honest about what you want from employment. Companies will increasingly choose tools and workflows based on productivity, not on whether every engineer enjoys writing code. If the current role leaves you unhappy, start applying elsewhere while building projects that demonstrate the kind of low-level and architecture work you want to do.

AI can still be useful for going deep technically if you treat it like a pair programmer rather than an answer machine. Ask it to explain execution models, inspect library source code, compare tradeoffs, and walk through every generated change. For example, debugging thread scheduling or I/O behavior in a real codebase can become a much more focused learning exercise than searching for disconnected examples.

This situation isn’t necessarily a dead end. Business requirements, solution design, and reviewing generated code are traditionally responsibilities that more senior engineers take on. You can use the time to study architecture and system design, then deliberately implement parts of the solution yourself. Practice outside work and personal projects will keep your coding skills sharp while giving you more options.