Information security

From watching alerts to deciding which risks the company accepts.

← All paths

The steps

Entry

Experienced

Senior

Lead / Principal

Manager

Security analyst
Security Engineer
Senior Security Engineer
Security Architect
Security managerPeople management

PromotionLateral move or track changeEach step links to its full detail below.

#	Step	What changes here	Jump	Skills
1	Security analystEntry · Individual contributorNo active openings	Moves from handling alerts to understanding why they happen.	—	Log analysis Cybersecurity fundamentals Security operations
2	Security EngineerExperienced · Individual contributorNo active openings	Builds the controls instead of only reviewing them.	PromotionJump: Moderate	Vulnerability management Cloud infrastructure Identity and access management Threat modeling
3	Senior Security EngineerSenior · Individual contributorNo active openings	Decides where the effort goes, because it never covers everything.	PromotionJump: Moderate	Threat modeling Cryptography fundamentals Incident response Security compliance
4	Security ArchitectLead / Principal · Individual contributorNo active openings	Security enters at design time rather than afterwards.	PromotionJump: Moderate	Regulatory compliance System design Technical communication Threat modeling Security compliance
5	Security managerManager · People managementNo active openings	Answers to leadership for risk, not for tooling.	PromotionJump: Moderate	Team leadership Security awareness training Risk & compliance Budget ownership

What makes the differenceAlso asked for

This describes moves that happen, not a recommended sequence or the only way to get there.

How this path was built

A structured starting point: it describes how this function is organized in technology companies, not a survey of Costa Rican employers. The skills at each step come from the platform’s curated vocabulary. Each version goes through industry review before it replaces this one.

Evidence as of: August 16, 2026
Reviewed on: August 16, 2027