Okta is the dominant enterprise identity platform — and its India team of approximately 2,500 engineers in Bengaluru and Hyderabad is building the core of that platform. The Auth0 acquisition in 2022 brought a significant engineering team into Okta's India fold, and the combined organisation now works on everything from workforce identity to customer identity (CIAM) to AI-powered threat detection. OKTA stock has had a turbulent few years — a significant drop in 2022-23 followed by recovery — and that volatility makes the RSU tax and timing strategy particularly consequential for Indian employees. This guide covers the full picture.
Okta in India: Offices, Cities & Scale
Okta's India footprint is concentrated in Bengaluru, where approximately 2,000 employees work on core platform engineering. The Bengaluru team covers Okta's two primary product lines: Workforce Identity Cloud (the original Okta product for enterprise SSO, MFA, and lifecycle management) and Customer Identity Cloud (the Auth0 product, which was separately maintained pre-acquisition and has been increasingly integrated post-merger). Engineers in Bengaluru own significant feature surface area — this is not offshore development support but product engineering with global scope.
Hyderabad houses approximately 500 employees in engineering, IT, and support functions. The Hyderabad presence grew partly through the Auth0 acquisition and partly through organic hiring as Okta's India engineering footprint expanded.
Okta's January fiscal year end is relevant for grant timing. The company typically issues annual refresh grants in April-May following the January FY close. New hire grants are issued at or near the joining date. One important post-acquisition nuance: Auth0 employees who transitioned to Okta had their RSU grant structures adjusted — some retained Auth0 vesting terms on legacy grants while receiving Okta RSU grants on new hire. If you joined through the Auth0 path, verify your specific grant terms with Okta's HR portal rather than assuming standard Okta mechanics.
- →Bengaluru (~2,000): Core platform engineering across Workforce Identity and Customer Identity (Auth0)
- →Hyderabad (~500): Engineering, IT, support — including post-Auth0 acquisition employees
- →Auth0 India employees transitioned to Okta compensation structure post-2022 acquisition
- →January fiscal year — refresh grants typically April-May
- →Product engineering ownership is genuine — not offshore development support
Department Mix
Okta India is a software engineering-heavy organisation, with approximately 70% of India headcount in product engineering roles. The Auth0 CIAM (Customer Identity and Access Management) engineering team is a significant bloc — Auth0 built a developer-first identity platform and many of those engineers who are now in the Okta India org came from Auth0's more engineering-intensive culture.
Zero Trust and security engineering are growing functions. Okta's ZTNA (Zero Trust Network Access) product line, including its recent acquisitions (Spera Security, Atko/Oktane integration tools), has created additional engineering headcount in India. AI/ML for identity security — anomaly detection, adaptive authentication, bot detection — is an emerging cluster.
Customer success and technical support engineering forms a secondary cluster. Given that Okta's customers are often large enterprises deploying Okta for tens of thousands of employees, technical account management and implementation engineering are meaningful functions that India teams support. Sales is not a significant India function — Okta's enterprise sales is primarily US and Europe based.
- →~70% software engineering (Workforce Identity, Customer Identity/Auth0, ZTNA)
- →Auth0 engineering team is a culturally distinct, developer-focused cohort within Okta India
- →AI/ML for identity security (anomaly detection, adaptive auth) is a growing function
- →Technical account management and implementation engineering are secondary clusters
Who Gets RSUs: Levels & Amounts
Okta's RSU programme in India starts meaningfully at SWE L3 (Software Engineer Level 3 equivalent) — roughly equivalent to 3-5 years of experience. Entry-level engineers and some L2 positions may receive token grants or no equity. L3 is where equity becomes a real compensation component.
At L3 (Software Engineer), new hire grants are typically $30,000–$60,000 over four years. At L4 (Senior Software Engineer), grants step up to $70,000–$130,000. L5 (Staff Engineer) sees new hire grants of $130,000–$250,000. Principal Engineers and above receive $250,000+ in new hire equity, with executive-level equity for Director and VP roles that are based in India.
Auth0 employees who transitioned to Okta have compensation structures that reflect their seniority at Auth0 — they were not systematically re-levelled down. In some cases, experienced Auth0 engineers received Okta grants that are at the higher end of their level range as a retention measure post-acquisition.
Annual refresh grants are issued based on performance. An L4 at "meets expectations" typically receives $20,000–$35,000 in refresh. "Exceeds" ratings push L4 refreshes to $40,000–$65,000. Okta's equity philosophy has historically prioritised retention of senior technical talent, so senior engineers have seen meaningful refreshes particularly during the Auth0 integration period.
- →L3+ is meaningful RSU eligibility threshold
- →L3 new hire: $30,000–$60,000 over 4 years
- →L4 new hire: $70,000–$130,000 over 4 years
- →L5 (Staff) new hire: $130,000–$250,000 over 4 years
- →Auth0 legacy employees received competitive Okta grants as retention post-acquisition
Understanding Your Vest Schedule
Okta uses quarterly vesting with a one-year cliff. The cliff means your first vest occurs on the one-year anniversary of your grant date (25% of the grant), followed by 6.25% vesting each subsequent quarter through the fourth year. For employees who came from Auth0, your Okta grant date is typically the closing date of the acquisition or your transition date — verify this in the Equity Edge Online (or Morgan Stanley at Work) portal.
Okta's fiscal year ends in January, and the annual refresh cycle runs in April-May. If you received an out-of-cycle grant (e.g., a retention grant or a promotion equity bump), it will have its own grant date and its own four-year vest schedule. Multiple overlapping grants from different grant dates create a multi-track vest pipeline where you're receiving vests from different grants in the same quarter.
On each quarterly vest, shares are processed through the equity plan platform (Morgan Stanley at Work / Equity Edge). TDS is withheld via sell-to-cover, and net shares are deposited in your account. The TDS amount should reflect the perquisite value (vest-date OKTA price × units × SBI TT rate × applicable marginal rate). Check this on every vest — if Okta's TDS calculation is based on a flat rate that doesn't account for your full surcharge exposure, you may be under-withheld.
For employees who received Auth0 RSUs that converted to Okta RSUs at acquisition: the conversion happened at a fixed ratio based on the acquisition price, and your cost basis for Indian tax purposes starts from the date of conversion (when you received Okta RSUs), not from your original Auth0 grant date. Confirm this with your CA.
If you are an Auth0 legacy employee, your effective equity grant history at Okta is complex — you may have multiple grant dates, different vesting terms on legacy vs new grants, and a conversion-date cost basis for the converted RSUs. Reconstruct your full equity history carefully before filing your ITR — errors here compound over multiple years.
- →Quarterly vest, 1-year cliff — standard US tech company structure
- →Auth0 transition grants may have a different effective start date — verify in equity portal
- →Multiple overlapping grant tracks after 2+ years of tenure
- →TDS withheld via sell-to-cover; verify amount accounts for full surcharge exposure
- →Auth0-to-Okta RSU conversion: cost basis starts from conversion date, not original Auth0 grant date
The Tax Reality
Okta India RSUs create the standard two-stage Indian tax liability: perquisite tax on vest and capital gains on sale. OKTA's stock volatility (it dropped from $250 to $65 in 2022-23 before recovering) means the rupee values involved vary significantly year to year, requiring careful advance tax management.
On vest, the full market value of vested shares (units × OKTA closing price on vest date × SBI TT USD/INR rate) is added to your salary income and taxed at marginal rate under Section 17(2). For L4 engineers in Bengaluru, effective rates including surcharge and cess are typically 34-39% depending on total income. The perquisite value is reflected in Form 12BA and Form 16 — verify this matches E*TRADE/Morgan Stanley records.
Capital gains begin from vest date. Cost basis per lot: vest-date OKTA price × SBI TT rate in INR. STCG (within 24 months): slab rate, typically 30%+. LTCG (after 24 months): 12.5% without indexation (check current rules). For employees who received RSUs during OKTA's 2022-23 low period (around $65-90 range), shares held since then have significant gains — the LTCG vs STCG calculation for those lots is very material.
US withholding on vest: claim credit via Form 67 before ITR. Schedule FA: report OKTA holdings and Morgan Stanley at Work account annually. Advance tax: mandatory for employees with quarterly vests exceeding ₹10,000 in quarterly tax liability. OKTA has quarterly earnings in March, June, September, December — earnings beats can create unexpected vest value spikes that require advance tax adjustment.
Most-missed mistake: selling OKTA shares immediately after vest to "lock in gains" without checking the 24-month LTCG status of each lot. If you vested shares in March 2024 when OKTA was at $90 and OKTA is now at $120, those shares reached the 24-month LTCG mark in March 2026. Selling in December 2025 would trigger STCG on a ₹20 lakh gain — waiting 3 months saves ₹3+ lakh in tax. These calculations are always worth doing.
- →Vest taxed as perquisite at marginal rate (~34-39% for L4 in Bengaluru)
- →STCG within 24 months: 30%+; LTCG after 24 months: 12.5%
- →Employees with 2022-23 low-price lots have large gains — LTCG optimisation very valuable
- →Form 67 before ITR; Schedule FA annually; advance tax each quarter
- →OKTA earnings volatility can create unexpected vest value spikes — adjust advance tax dynamically
What Employees Typically Do
Okta India employees — particularly those from the Auth0 legacy cohort — tend to be developer-ecosystem savvy and more aware of equity mechanics than the average IT services employee. Blind and internal Slack channels have active equity discussions, and comp transparency norms from the startup world (Auth0 was startup-culture before acquisition) persist in the combined Okta India org.
The 2022-23 drawdown was a formative experience. Engineers who held OKTA from $200+ down to $65 — watching six-figure USD positions shrink by 70% — are more likely to be systematic sellers now. "I'll never hold a single stock past a 20% gain again" is a sentiment that surfaces frequently among this cohort. Meanwhile, engineers who joined during the trough and saw recovery are more bullish on holding.
The Auth0 vs Okta cultural dynamic affects equity behaviour. Auth0 engineers came from a startup culture where equity was a primary wealth vehicle and they were more engaged with their cap table. These engineers typically think more carefully about sell timing and tax implications. Okta-native hires in India, especially those from larger IT companies, are sometimes less engaged with their equity management.
L5+ engineers (Staff and above) with 3+ years of tenure at Okta can have ₹60-120 lakh in total RSU exposure across vested holdings and unvested pipeline — a scale that warrants proper financial planning rather than ad-hoc decisions.
- →Auth0 legacy cohort is more financially engaged with equity — startup culture influence
- →Post-2022-23 drawdown, many engineers have systematic sell rules
- →New joiners during 2023 trough have strong buy-and-hold conviction based on recovery
- →L5+ engineers may have ₹60-120 lakh total RSU exposure — needs formal financial planning
The Smart Approach
The 24-month LTCG calendar is the highest-leverage tool available to Okta India employees. Given OKTA's price history — significant drawdown followed by partial recovery — many employees have shares with varied cost bases. Build a lot tracker: vest date, OKTA vest price, INR cost basis, 24-month date, current market value, STCG if sold today, LTCG if held to threshold. For lots near the 24-month mark, the calculation often shows ₹2-5 lakh in tax savings from waiting a few months. That's time well invested.
For Auth0 legacy grants: reconstruct the full timeline. When did your Auth0 RSUs convert to OKTA RSUs? What was the OKTA share price on conversion date? That is your cost basis for those lots. Any gains from OKTA appreciation post-conversion are taxable as capital gains. Any pre-conversion gains are treated as perquisite income at the conversion date (this is complex — involve a CA with experience in acquisition-related equity).
Advance tax planning: OKTA earnings are volatile. Model a low-case and high-case scenario for annual vest value and plan advance tax payments conservatively. If OKTA beats earnings in Q3 and the stock spikes, your Q3 vest value will be higher than projected — top up advance tax payment before the December 15 deadline.
Diversification: OKTA competes in a crowded identity space. Microsoft's Entra ID is a formidable bundled competitor, and any large enterprise customer consolidating on Microsoft can affect Okta's net retention. Keep OKTA below 20% of liquid net worth, and systematically diversify into index funds on a quarterly schedule.
- →Build lot-by-lot LTCG tracker — typically ₹2-5 lakh tax savings per lot by waiting to threshold
- →Auth0 legacy employees: reconstruct conversion date and cost basis carefully with a CA
- →Model low and high vest value scenarios for advance tax planning
- →Top up advance tax in December if Q3 earnings beat increases vest values
- →Keep OKTA below 20% of net worth; diversify quarterly into index funds
- →File Form 67 before ITR; report Schedule FA annually
Concentration Risk
Okta's risk profile is defined by competitive dynamics in enterprise identity. Microsoft Entra ID (formerly Azure AD) is an active and aggressive competitor — Microsoft bundles identity capabilities with its Microsoft 365 enterprise agreements, making it difficult for CISOs to justify a separate Okta spend when Azure AD covers basic SSO needs. Okta has defended its position by emphasising multi-cloud, multi-vendor identity (its competitive moat), but enterprise procurement cycles favour bundled Microsoft deals.
The 2023 security breach (a hack of Okta's customer support system) was a significant reputational event that slowed enterprise deal flow for several quarters. Customer identity (Auth0 business) faces competition from AWS Cognito, Auth0 clones, and open-source alternatives. Any sustained competitive pressure in either segment would compress OKTA's revenue growth and therefore its stock multiple.
OKTA fell from $260 to $65 between 2021 and 2023 — an 75% drawdown. This happened not because Okta's business failed but because the combination of rising interest rates (compressing high-multiple SaaS valuations) and the security breach created a double compression. Your equity could see a similar scenario even without a fundamental business failure.
A 35% OKTA drawdown from current levels would erase years of equity compensation for employees with concentrated positions. The 2022-23 episode showed that high-multiple SaaS stocks can reprice quickly even when the company is operationally intact. Don't let paper gains become paper losses — diversify systematically.
- →Microsoft Entra ID is the primary competitor — bundled with M365, formidable for SMB and mid-market
- →2023 security breach caused multi-quarter sales cycle disruption — reputational risk is real
- →OKTA fell 75% in 2021-23 despite intact business — high-multiple SaaS valuation risk
- →Net retention rate below 115% would signal competitive pressure and trigger re-rating
Getting Money Home: FX & Repatriation
OKTA sale proceeds from Morgan Stanley at Work can be repatriated under LRS (up to $250,000 per financial year). Quarterly repatriation aligned with quarterly vest dates is the most practical cadence. For each quarterly repatriation, file 15CA/15CB with your CA for amounts over $5,000. Budget ₹2,000-5,000 per quarter in CA fees.
FX cost on traditional bank SWIFT transfers: 1.5-2.5% above SBI TT rate. On $50,000/year of repatriation, that's $750-$1,250 in unnecessary FX cost. Rovia's 0% FX markup eliminates this drag. Keep records of the SBI TT rate on every vest date and sale date — these feed into your ITR cost basis and Schedule FA calculations. Morgan Stanley at Work provides annual statements that your CA needs for the foreign assets and capital gains schedules.
- →LRS: $250,000/year — quarterly cadence aligned with vest schedule
- →Bank FX spread of 1.5-2.5% costs $750-1,250/year on $50K repatriation
- →15CA/15CB for each remittance over $5,000; ~₹2,000-5,000 in CA fees per quarter
- →Keep SBI TT rate records for every vest date and sale date for ITR accuracy
Stock Sentiment
Okta India employee sentiment reflects the stock's own recent history — cautiously optimistic after a painful 2022-23 period, with more experienced employees having a healthier relationship with selling than they did before the drawdown. Internal Slack channels and Blind have active OKTA discussions, with the Auth0 cohort particularly engaged given their pre-acquisition equity experience.
The primary internal narrative in 2025-2026 is around Okta's AI identity security proposition — using machine learning to detect compromised credentials, adaptive authentication, and identity threat detection. Engineers working on these features are excited about the technical challenges and see alignment between the product direction and the market need. This positive product sentiment supports the "hold" instinct for many engineers.
The Microsoft Entra competition is a frequent topic. Engineers whose customers or former colleagues have switched to Microsoft identity products are aware of the competitive headwinds and factor this into their equity outlook. This segment of the India population is more likely to be systematically diversifying.
Departure patterns at Okta India show spikes after full 4-year vest and after mid-career engineers are passed over for promotion to L5. The CIAM (Customer Identity/Auth0) engineering cohort has relatively higher mobility — they came from a startup culture and are more comfortable with job transitions. Bengaluru's identity and security startup ecosystem has grown as a destination for departing Okta engineers.
- →Post-2022-23 drawdown created more sell-conscious behaviour, especially among Auth0 cohort
- →AI identity security features driving positive internal product sentiment
- →Microsoft Entra competition is a known concern — affects bullish vs bearish cohort split
- →Auth0/CIAM cohort has higher mobility — more departure activity than Okta-native hires
- →4-year vest completion and missed L5 promotion are the primary departure triggers
This guide is for informational purposes only and does not constitute financial, tax, or investment advice. Figures are estimates based on publicly available information. Always verify with a SEBI-registered financial advisor and a CA familiar with foreign asset taxation.