PlainID Engineering Analyst

⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for a PlainID Engineering Analyst with a contract length of "unknown," offering a pay rate of "unknown." Key requirements include 8+ years in IAM solutions, hands-on experience with REST APIs, PostgreSQL, and Splunk.
🌎 - Country
United States
πŸ’± - Currency
$ USD
-
πŸ’° - Day rate
480
-
πŸ—“οΈ - Date discovered
June 4, 2025
πŸ•’ - Project duration
Unknown
-
🏝️ - Location type
Unknown
-
πŸ“„ - Contract type
Unknown
-
πŸ”’ - Security clearance
Unknown
-
πŸ“ - Location detailed
United States
-
🧠 - Skills detailed
#REST (Representational State Transfer) #Azure #IAM (Identity and Access Management) #Kubernetes #API (Application Programming Interface) #POSTMAN #Splunk #Deployment #REST API #PostgreSQL #Databases #JDBC (Java Database Connectivity) #LDAP (Lightweight Directory Access Protocol) #Monitoring
Role description
β€’ 8+ years of exclusive experience as a SME in implementing Identity and access management solutions such as Azure AD, Okta for any large enterprises and in those 2 years of experience as a PlainID engineering lead is must. β€’ Must have hands-on experience in designing, configuring, and testing access control policies by defining suitable dynamic identity groups, applications, assets, and conditions based on the business requirements for access control β€’ Experience on how REST API works and how to test the APIs using testing tools such as Postman is must. β€’ Experience in integrating PlainID with data sources using protocols such as LDAP, JDBC and REST API is also must β€’ Experience in managing PostgreSQL databases is necessary. β€’ Experience in handling the authorization logs using Splunk log management solution is must as well. β€’ Following experience are a plus.. β€’ Deploying PlainID Authorization Agents in Kubernetes cluster using helm charts and / or supporting similar hybrid deployments. β€’ Scanning and fixing the vulnerabilities in the PlainID deployment using the monthly and out-of-band releases. β€’ Controlling user access to PlainID admin / PAP portal. β€’ Monitoring the health of the PlainID processes and troubleshooting incidents and problems reported based on the severity / SLA defined