Use static or dynamic variables in my codes? What would be more efficient or better seen in the job market?

The labor market has nothing to do with this (the market sees other things, for example conceptualizing things correctly to understand what it is doing and thus produce adequate results, it does not look at a specific point, but the general attitude and capacity of the person). I am responding because the core of the question does not seem to be this.

Variables are not dynamic or static. The closest to this term is the variable being considered static because it is a class variable, as opposed to being an instance variable, in the background the right concept is to be class variable, static is a term used in code only. >

What you're talking about is the objects themselves, they can be statically, automatically, or dynamically allocated.

Static allocation is very simple and occurs at application startup. It's not what you probably think it is. The object already does "part of the code".

What you probably think is static is the automatic allocation that occurs in what is called stack (which can use pointer as well, it is a mistake to associate lifespan or location allocation with the use of pointer). This allocation is always preferable because it costs very cheaply, the release is automatic and so you do not have to worry about managing your life time in a complex way, among other advantages.

Dynamic allocation (occurs in heap and so pointer usage is mandatory since the variable is not there) is used when there is no other way. When you need a longer or less predictable life time, or when it takes up a lot of space.

See more at:

• Performance of heap and stack data access and object allocation
• When should I choose whether to use a pointer when creating an object?
• What prevents an array from being booted with a variable size in C?
• What makes an object eligible to be allocated on the stack?
• How does malloc organize memory?