In which area of programming will we need to do the least amount of layout work?

I'd argue that we'll need to do the least amount of layout work in the realm of backend development, specifically when building RESTful APIs.

Here's why: when you're crafting an API, your primary focus is on defining endpoints, handling requests and responses, and ensuring data integrity. The layout aspect is largely irrelevant, as the API will be consumed by other services or clients, which will handle the presentation layer. You're more concerned with the business logic, data modeling, and API security, rather than worrying about how the data will be visually represented.

In contrast, frontend development, whether it's for web or mobile, requires a significant amount of layout work. You need to consider user experience, responsive design, accessibility, and visual aesthetics, which can be time-consuming and labor-intensive. Even with the help of CSS frameworks and UI libraries, layout work is an essential part of building a user-friendly interface.

Now, I know what you're thinking: "What about scripting languages like Python or Ruby, where we're building command-line tools or scripts?" Well, in those cases, layout work is often minimal or non-existent, as the output is typically text-based or focused on data processing.

So, if you want to minimize layout work, focus on building robust, scalable, and secure APIs, and let the frontend developers worry about making it look pretty!

Well, in embedded, of course, in the code for microcontrollers.  Also device drivers, memory managers in operating systems... - what is called "system programming", that is, programming at the operating system level.
If you really don't want to have anything to do with visualization programming - then you should go there. Because even in the sections of artificial intelligence, in data analysis, you will have to draw something, but at such a low level - no longer. People of such specialties are quite narrow specialists, however, you are unlikely to find vacancies for juniors quickly.

In any programming sphere, barring web development. It's akin to front-end work, yet in disparate languages and environments, like Swift for iOS or WPF for Windows apps. There, the term 'layout' doesn't fly. For a surefire no-go on anything remotely similar, consider systems with minimal or no UI, such as embedded systems or high-performance computing. Think mission-critical apps in aerospace or power grid management.