Security Engineer

CONTEXT

Our client, a major player in its sector, operates a security foundation that must remain dependable every hour of every day. Identity, authentication, and infrastructure protection are not abstract ambitions here; they are the quiet mechanisms that allow teams, partners, and users to work with confidence. The organization is strengthening its security solutions through a hands-on engineering role that sits between operations and improvement. The mission starts with a simple promise: keep the existing security stack reliable, then make it more resilient, more observable, and easier to evolve. The engineer will join a team where technical judgment matters, where procedures are written to be used, and where security advice is expected to be clear enough for technical and non-technical colleagues alike. In this context, the role is not only about responding to tickets; it is about understanding how identities flow, how sessions are trusted, how infrastructure exposes risk, and how small configuration choices can become major safeguards when handled with care.

ACTIVITIES

• Operate and maintain day-to-day security solutions, ensuring availability, performance, and correct configuration across identity and infrastructure components.
• Analyze security requirements and translate them into concrete configurations, procedures, and technical controls that teams can adopt without friction.
• Manage identity and access management components, including authentication flows, identity lifecycle tasks, and access policies.
• Configure and maintain security tools, monitor systems, investigate anomalies, and document operational runbooks and escalation paths.
• Contribute to improvement projects around OAuth, OpenID Connect, authentication patterns, and infrastructure hardening.
• Provide technical security advice to project teams and stakeholders, explaining trade-offs and helping them design safer solutions.
• Participate in architecture and design discussions, review proposed integrations, and identify security gaps before they reach production.
• Share knowledge with colleagues through documentation, peer support, and practical guidance that raises the overall security baseline.

EXPECTED ACHIEVEMENTS

• Security solutions run reliably, with fewer surprises, faster diagnosis, and clearer ownership of operational tasks.
• Identity and access management becomes more robust, more coherent, and better aligned with real business needs.
• Authentication and infrastructure security projects deliver measurable improvements without disrupting daily operations.
• Teams across the organization make better security decisions because advice is timely, practical, and grounded in the actual environment.
• Procedures and monitoring practices become durable knowledge assets rather than one-off fixes.
• The organization gains a stronger security posture while preserving the usability and continuity that its users depend on.

ENVIRONMENT

• Identity and access management tooling, authentication protocols, and security platforms.
• OAuth and OpenID Connect patterns for modern application and API access.
• Infrastructure security controls, monitoring, logging, and operational runbooks.
• Ticketing, documentation, and collaboration tools used to support distributed technical teams.
• A hands-on engineering culture with a balance between operational duties and project work.
• Security by design principles, clear procedures, and continuous improvement practices.