MongoDB RSUs in India: The Complete Tax & Wealth Guide

MongoDB in India: Offices, Cities & Scale

MongoDB's India presence is anchored in Bengaluru with approximately 1,500 employees doing core engineering work on the Atlas platform, Ops Manager, MongoDB Compass, and developer tools. This is product engineering, not a support or localisation hub — Bengaluru engineers own feature surface area in Atlas, the company's flagship cloud database-as-a-service offering that drives the majority of MongoDB's revenue growth.

Mumbai houses around 300 employees primarily in sales and GTM functions — the team responsible for driving MongoDB's enterprise cloud adoption across Indian companies. This is a revenue-generating function with a different compensation structure including sales commissions and OTE (on-target earnings) components. Hyderabad adds another 300 employees in engineering and support functions.

MongoDB's India operation has grown significantly as Atlas revenue has scaled. The company closed its fiscal year ending January 2026 with Atlas representing over 70% of total revenue, and the India engineering team is central to building the features — vector search, Atlas Stream Processing, serverless clusters — that support this growth. MongoDB's India headcount growth has been relatively aggressive compared to peers in the developer tools space, partly because engineering talent quality in Bengaluru is competitive at lower relative cost than San Francisco.

• →Bengaluru (~1,500): Core Atlas platform engineering, Ops Manager, Compass, developer tools
• →Mumbai (~300): Enterprise sales and GTM for India market
• →Hyderabad (~300): Engineering support and sustaining engineering
• →Atlas platform represents 70%+ of total revenue — India engineers build core Atlas features
• →India headcount growing rapidly in line with Atlas revenue expansion

Department Mix

MongoDB India is primarily a software engineering organisation. Engineering represents approximately 65-70% of India headcount, with teams organised around Atlas product areas (Atlas Clusters, Vector Search, Atlas Data Federation, Atlas App Services), developer tools (Compass, VS Code extension, language drivers), and infrastructure/reliability engineering.

Sales and customer success in Mumbai form a distinct functional cluster — roughly 15% of total India headcount — operating on a different compensation model than engineering. Sales employees have base salary + commission + RSU equity (at qualifying levels), while engineering is base + bonus + RSU.

Data science, ML engineering, and AI product development are growing functions as MongoDB builds AI-native database features (Vector Search, Atlas AI, natural language query interfaces). These roles are increasingly part of the RSU-eligible senior technical population. Support engineering and technical account management form a smaller cluster focused on enterprise customer retention.

• →~65-70% software engineering (Atlas platform, dev tools, infra/reliability)
• →~15% sales and customer success (Mumbai-heavy, commission-based)
• →ML/AI engineering growing as MongoDB builds AI-native database features
• →Sales employees have different compensation structure (OTE + equity) from engineering

Who Gets RSUs: Levels & Amounts

MongoDB's RSU eligibility in India starts at SWE 2 (Software Engineer 2) and above. SWE 1 new graduates may receive token equity grants in some cases, but meaningful grants begin at SWE 2. MongoDB is known in the developer infrastructure space for equity grants that are at the higher end of the range — competitive with larger companies at equivalent levels.

At SWE 2, new hire grants typically range from $30,000–$60,000 over four years. At SWE 3 (Senior Software Engineer), grants step up to $70,000–$130,000. Staff Engineers (SWE 4) see new hire grants of $130,000–$250,000. Principal and Distinguished Engineers receive grants commensurate with their level, often $250,000+.

Annual refresh grants at MongoDB are meaningful and tied to performance. A SWE 3 at "meets expectations" might receive $25,000–$40,000 in annual refresh equity. "Exceeds" ratings push refreshes to $50,000–$80,000 at SWE 3. MongoDB has historically been willing to compete aggressively on refreshes to retain senior engineers, particularly as the Bengaluru tech market has become more competitive.

MongoDB's equity is denominated in USD, and grants are made in units of shares (not dollar amounts). The number of units is calculated based on MDB's stock price at grant date. If MDB has moved significantly since your grant, your accumulated unit count reflects an earlier price point — which can mean your unvested pipeline is worth substantially more (or less) than your grant value in USD terms.

• →SWE 2+ are minimum qualifying level (some SWE 1 token grants exist)
• →SWE 2 new hire: $30,000–$60,000 over 4 years
• →SWE 3 new hire: $70,000–$130,000 over 4 years
• →Staff Engineer (SWE 4) new hire: $130,000–$250,000 over 4 years
• →Refresh grants competitive — MongoDB retains aggressively at SWE 3-4 level

Understanding Your Vest Schedule

MongoDB uses quarterly vesting with a one-year cliff, the same structure common across US tech companies. A grant issued in March 2025 has its cliff vest in March 2026 (25% of the total grant), followed by quarterly vests of 6.25% each through March 2029.

MongoDB's fiscal year ends in January. Annual refresh grants are issued in the April-May timeframe following the January fiscal year close and board compensation review. This timing means that for most India employees, the refresh grant date is in Q1-Q2 of the US fiscal year (which starts February 1). After 2-3 years at MongoDB, you have multiple overlapping grant tracks — new hire grant plus 2-3 annual refreshes — all vesting quarterly. This creates a steady quarterly cash flow of RSU income that requires consistent advance tax planning.

The equity plan is managed through E*TRADE (Morgan Stanley at Work). On each quarterly vest date, TDS is withheld via sell-to-cover: enough MDB shares are liquidated to cover estimated Indian income tax, and the net shares land in your brokerage account. You should verify the TDS amount withheld each quarter and compare it with your actual liability — high earners with surcharge exposure may find TDS is under-withheld, creating an advance tax obligation.

MongoDB stock can be volatile — as a growth software company with high multiples, it reacts sharply to earnings beats and misses. This means the actual rupee value of a quarterly vest can vary significantly from what you projected at the start of the year, requiring dynamic adjustment of advance tax estimates.

• →Quarterly vest, 1-year cliff
• →Fiscal year January end — refresh grants typically April-May
• →Multiple overlapping grant tracks after 2+ years of tenure
• →Equity plan via Morgan Stanley at Work (E*TRADE)
• →MDB stock volatility means actual vest values can vary significantly from projections

The Tax Reality

MongoDB India RSUs create perquisite tax on vest and capital gains on sale. Given MDB's premium SaaS valuation and above-average grant sizes, the rupee tax exposure is material for senior engineers.

On each quarterly vest, the market value of vested MDB shares (units × MDB closing price on vest date × SBI TT USD/INR rate) is treated as salary income under Section 17(2). This is added to your regular salary and taxed at marginal rate. For SWE 3-4 in Bengaluru, effective rates including surcharge and cess typically range from 34-39% depending on total income. Your Form 16 should reflect this perquisite value — verify it matches what E*TRADE/Morgan Stanley records show.

Capital gains start from vest date. The cost basis per lot is the vest-date MDB price in INR (price × SBI TT rate). Shares sold within 24 months: STCG at slab rate (30%+ for most SWE 3+). Shares sold after 24 months: LTCG at 12.5% without indexation (verify with CA for rules applicable in your tax year). The LTCG vs STCG difference is particularly pronounced for MDB because the stock has moved significantly over the past few years — the gain on older lots is large, making the tax differential very material.

Claim US withholding credits via Form 67 before ITR submission. Report MDB holdings in Schedule FA — every year, even if you haven't sold. Advance tax payment is mandatory for all employees with quarterly vests that generate meaningful tax liability. Estimate your total income at the start of each FY and set up advance tax payments; adjust each quarter based on actual vest values.

For employees who received grants when MDB was trading at significantly different prices (the stock has been as low as $140 and as high as $450 in recent years), the cost basis spread across different lots creates complex tax optimisation opportunities that are worth working through with a CA.

• →Vest taxed as perquisite at marginal rate (~34-39% for SWE 3-4 in Bengaluru)
• →STCG (within 24 months): slab rate 30%+
• →LTCG (after 24 months): 12.5% without indexation
• →Large cost basis spread across lots due to MDB's stock price volatility
• →Form 67 before ITR; Schedule FA annually; advance tax each quarter

What Employees Typically Do

MongoDB India engineers tend to be young, relatively financially aware, and influenced by the developer community's active discussion of compensation and equity. TeamBlind threads about MongoDB comp packages are frequently referenced, and there is a reasonably high baseline of awareness about RSU mechanics compared to, say, a pharma services company.

The most common pattern is selling a significant portion of shares on or shortly after vest — often within the same week — to cover expenses, pay down a home loan, or reinvest in Indian markets. This immediate-sell pattern is understandable given MDB's volatility, but it nearly always triggers STCG at full marginal rates, which is suboptimal for shares that have appreciated significantly.

The 24-month LTCG opportunity is underutilised. A SWE 3 holding shares from a vest 20 months ago, with a ₹15 lakh unrealised gain on that lot, saves approximately ₹2.6 lakh in tax by holding 4 more months. Most engineers would wait 4 months for ₹2.6 lakh — but they haven't done the calculation.

Engineers at SWE 4+ with 3+ years of tenure sometimes have surprisingly large accumulated positions — ₹50-100 lakh in MDB held in E*TRADE — that they haven't actively managed, partly from inertia and partly from bullish conviction on Atlas growth.

• →High developer community awareness of equity mechanics compared to other India RSU populations
• →Immediate-sell on vest is common — mostly triggering avoidable STCG
• →24-month LTCG threshold is underutilised despite the meaningful tax savings
• →SWE 4+ employees often have large unmanaged positions from inertia and Atlas conviction

The Smart Approach

The first step is identifying which lots are within the 6-month window before the 24-month LTCG mark. For a quarterly-vest employee, you have a new lot every 3 months. Systematically, lots from 18-23 months ago should be held until the 24-month mark before selling, unless there is a compelling reason to sell earlier (stock valuation concerns, immediate cash need).

Build a lot tracker: date, units, MDB vest price, INR cost basis, 24-month date, current gain, tax due if sold today (STCG) vs at 24 months (LTCG), and the rupee saving from waiting. When that spreadsheet shows ₹2-5 lakh savings from waiting a few months, the decision becomes obvious.

For advance tax: at the start of April each year, estimate your annual vest value using current MDB price as a baseline. Add to your salary, calculate marginal tax, and set up advance tax instalments. MDB earnings are in March, June, September, December (quarterly) — major price moves happen around these dates. Adjust your advance tax estimate after each earnings event.

Diversification for MongoDB employees: MDB trades at 20-30x revenue in growth mode — any slowdown in Atlas net revenue retention rate or a macroeconomic headwind to cloud spending can reprice the stock 20-30% quickly. If MDB represents more than 20% of your liquid net worth, redirect quarterly vest proceeds systematically into diversified equity. Don't wait for a "high" or "low" — use a quarterly schedule.

For repatriation, wire proceeds quarterly from Morgan Stanley at Work to India. 15CA/15CB required for amounts over $5,000. Use low-spread FX. Keep all E*TRADE transaction records for ITR purposes.

• →Identify lots within 6 months of 24-month LTCG date — hold until threshold unless compelling reason to sell
• →Build lot tracker showing STCG vs LTCG saving for each lot
• →Set up advance tax instalments in April based on annual vest value estimate
• →Adjust advance tax after each MongoDB quarterly earnings event (March/June/September/December)
• →Keep MDB below 20% of net worth; redirect quarterly vest proceeds to diversified equity
• →File 15CA/15CB per quarter; use low-spread FX for repatriation

Concentration Risk

MongoDB's entire investment case is built on Atlas cloud database revenue growth. If Atlas net revenue retention rate (NRR) — which measures how much existing customers spend in subsequent years — declines, the growth story weakens and the stock re-rates sharply. Atlas NRR has been above 120% historically; if it drops toward 110% or below, expect a significant valuation compression.

Competitive risks are real: Google Firestore, AWS DynamoDB, and Azure Cosmos DB are actively competing for the same developer mindshare. PostgreSQL's ecosystem (Supabase, Neon, PlanetScale) has grown significantly and competes at the lower end of MongoDB's customer base. Any sustained market share loss in the developer database space would affect revenue growth rates and the stock multiple.

The India-specific dimension: MongoDB's India engineering is building Atlas. If Atlas growth slows and MongoDB cuts costs — which it has done in prior cycles — India is often one of the higher-risk regions for headcount reductions. Your job security and your MRVL holdings are correlated to the same business outcome.

• →Atlas NRR decline below 115% would trigger significant stock re-rating
• →PostgreSQL ecosystem (Supabase, Neon) growing as a competitive threat
• →AWS/Google/Azure cloud database competition intensifying at enterprise level
• →India headcount is correlated to Atlas growth — job and RSU value are correlated

Getting Money Home: FX & Repatriation

MDB sale proceeds sit in your Morgan Stanley at Work account until you initiate a wire transfer. Under LRS, you can repatriate up to $250,000 per financial year. For SWE 3-4 employees with meaningful vest values, quarterly repatriation (aligned with quarterly vests) is the most practical cadence.

FX spread on traditional bank SWIFT transfers: 1.5-2.5% above SBI TT rate. On $60,000/year of repatriation, that's $900-$1,500 in FX costs. Rovia's 0% markup eliminates this. The SBI TT rate on the date of remittance is the official reference rate for INR cost basis calculations — keep records of this for ITR purposes.

15CA/15CB must be filed for each remittance above $5,000. Keep E*TRADE transaction records, Form 1099 (if issued), and the SBI TT rate on each vest date and sale date. Your CA needs all of this for the ITR Schedule FA, Schedule CG (capital gains), and for the Form 67 foreign tax credit claim.

• →LRS limit: $250,000/year — quarterly repatriation aligned with quarterly vests is practical
• →SBI TT rate on remittance date is the official INR reference for cost basis
• →Bank FX spread of 1.5-2.5% costs $900-1,500/year on $60K repatriation volume
• →Keep E*TRADE statements, vest records, and SBI TT rate history for ITR

Stock Sentiment

MongoDB India employee sentiment on MDB has been mixed-to-positive in recent quarters, reflecting the stock's own roller-coaster. During periods of strong Atlas growth beats (2021-2022), internal mood was euphoric — engineers were comparing their RSU gains in Slack channels and on Blind. During the 2022-23 tech sell-off when MDB dropped 70% from peak, the mood shifted to concern, and there were meaningful departures.

The current sentiment (2025-2026) is cautiously optimistic, driven by Atlas consumption growth recovering and AI-native database use cases (Vector Search for RAG pipelines) being a genuine new growth driver. MongoDB's positioning as the developer-first database for AI applications is a credible narrative, and India engineers building these features have a sense of product-market fit confirmation.

Internal forum discussion frequently centres on MongoDB's growth rate relative to its multiple — engineers understand that the stock is priced for continued 20%+ revenue growth and are somewhat aware of the risk if growth slows. The departure rate from MongoDB India has historically spiked after the 4-year grant cliff, particularly when engineers have found pre-IPO startups or other cloud-native companies offering higher base or guaranteed bonuses.

The transition from a "hold everything forever" culture to more systematic selling has been visible among employees who lived through the 2022-23 drawdown. Many engineers who watched their MDB holdings drop from ₹80 lakh to ₹24 lakh have become more active managers of their equity positions.

• →Post-2022-23 drawdown created a more sell-conscious employee cohort
• →AI-native database positioning (Vector Search) is driving positive internal momentum
• →Engineers track Atlas NRR closely — it is the proxy metric for their equity value
• →Departure spike at 4-year cliff — pre-IPO startups are the primary competitor for talent
• →Stock discussions on Blind are active and analytically sophisticated for a non-finance company