Identity & Access Management Engineer
I build workforce identity on Okta and Microsoft Entra ID. Currently open to IAM roles.
Selected work
Five sign-in behavior signals evaluated in Okta Workflows: new device with new country, impossible travel, and anomalous velocity among them. Corporate VPN egress excluded, recently-reset accounts held back from false positives. Confirmed anomalies trigger automatic user suspension and an admin alert.
Replaced ad-hoc rules with a ring-based policy set: report-only first, then enforced per cohort. Legacy authentication blocked tenant-wide, phishing-resistant MFA required for privileged roles.
0 legacy auth sign-ins after cutover
HRIS as source of truth, SCIM provisioning downstream. Birthright access from group rules, mover changes recalculated on attribute change, leaver access revoked the same day.
Day one access for every new hire
Company name, Hyderabad
Own the Okta workforce tenant end to end. Designed the behavioral threat detection pipeline, led the adaptive MFA rollout, and cut access-request turnaround from days to minutes.
Company name, Hyderabad
Migrated SSO from ADFS to Entra ID, rebuilt Conditional Access from scratch, and automated the joiner-mover-leaver lifecycle with SCIM provisioning from the HRIS.
Company name, Hyderabad
Ran Active Directory and Exchange for a 2,000-seat environment. First taste of identity: group policy, RBAC cleanup, and the on-call pager that taught me to automate.
I am Venkatramana Manchana, an identity engineer who treats access as an engineering problem, not a ticket queue. My work sits where security policy meets developer experience: sign-in flows people do not notice, and controls attackers do.
Most of my time goes into Okta and Entra ID tenants: designing policy, automating the joiner-mover-leaver lifecycle, and wiring detection logic that responds faster than a human on call.
Hiring for an IAM role, or untangling an Okta or Entra tenant? Reach out.