SECURITY · Security & Infrastructure
Security Engineer
Spot risks and build protection into every step of the work.
This role across the eras
Security: AI security (prompt injection, jailbreaks, the model supply chain), content security and filing compliance, and labeling of generated content.
2023–present · Read about the Large Model Era: its background, pain points, and new technology
Common tasks
The following is a composite example scenario; it does not correspond to any one company or person.
Who checks whether the system has a door that should not be open? Starting from this question, look at how a role connects needs, execution, and feedback.
Understanding today's problem
Understand what information the system handles, who has access, and where things might go wrong. Identify risks within an authorized scope, and confirm the impact with colleagues on the business side.
Moving forward with the team
Turn risks into improvements the team can carry out: access control, protection of sensitive information, log review, and recovery procedures. Work with engineering to confirm whether the approach is effective.
Delivery and continuous improvement
Review the fixes and record the risks and decisions. When an incident happens, collaborate by following the process, and gather the lessons so the same problem is less likely to happen again.
Role names help us see how work is divided; everyday collaboration is what truly connects those divisions.
How the role evolved: related papers
Papers per year in this site's sample for the arXiv categories related to this role (Cryptography and Security cs.CR). It reflects how research topics shift, not the number of people employed.
Data source: this site’s list of arXiv papers, counted by the year each paper was first published. A paper listed in several categories counts once in each line, so the lines do not add up. Not employment data.