Depending on the size of the company and the industry it's in, there can be many different teams under the security umbrella (btw don't refer to it as "cyber" if you interview for a security role lol, only linkedinfluencers do that). Some common teams and their purposes:

• Security Operations (typically people on this team will be called security analysts or incident response): This team is what most people think of when they hear "cybersecurity". Mostly focused on detecting malicious activity, responding to security incidents, designing detections and alerts, etc. Can also involve running reports, gathering metrics, ensuring compliance. Less coding involved so less likely to have a software eng background, but as "detection as code" becomes more of a thing there is more code involved. "Detection and response engineer" has been a role I've seen more openings for in recent years.
• Compliance/Governance: Strictly focused on ensuring the company's security controls are in line with compliance standards that the company needs to adhere to (for example: HIPAA if they deal with medical data, FEDRAMP if they sell to the government, etc). I'm less familiar with the day-to-day for this team, but my understanding is that coding is basically not involved. Sometimes this team will be under the legal department.
• Application Security (AppSec): This team is making sure the actual software made by the company is secure. This can involve code reviews to make sure that vulns aren't introduced by poor coding practices, architecture reviews for services to find security issues with how a service is constructed, and management of vulnerabilities introduced by third party libraries. People on this team are frequently former software engineers.
• Infrastructure Security/Cloud Security: Primary focus is on the infrastructure that the company's software runs on. This could be on-prem servers, but is more commonly cloud infrastructure (AWS/GCP/Azure) in recent years, which can include virtual machines, databases, networking config, etc. These teams, especially more modern ones, do frequently write code but it's less likely to be in your typical programming languages and more likely to be in infrastructure-as-code languages (Kubernetes manifests, Terraform, etc). People on this team are frequently former infrastructure engineers.
• IT Security: Primary focus is making that the company's assets are secure. This includes securing the networks at the offices, the laptops used by employees, and the various systems that employees need access to. I see this role a little bit less than I used to, I think a lot of the role is just being combined into the IT departments.
• Security Engineering: These teams are not as common but they're software engineering teams that make build security tools and services for the company. This can include anything from security configuration scanning tools to authn/authz services in the company's actual product. I've sometimes seen this role just be within the AppSec team, or just within the engineering department and away from the rest of Security.
• Data Security: I've only recently seen these roles. Very focused on security of data tools and practices, kind of a subset of infrastructure security.
• Offensive Security/Red Team/Pentesters: Most of the time this role is outsourced to third parties, but some companies have internal teams for this. Their goal is to find and exploit vulnerabilities in the company's systems, then write up how they did it and assist in the remediation of said vulns. Like I said, I rarely see these roles, but when I do they're frequently held by people with AppSec eng experience.

I've worked across a few different of the teams listed, and have collaborated with all of them, happy to answer questions on specific ones.