Canvas & Ratio
Choose your destination platform format
Layout Template
Choose a content structure for your slides
Preset Themes
Typography & Sizing
Brand Kit Customization
AGENCYConfigure brand assets for headers & footers
Outro Slide CTA
Customize your closing call-to-action slide
Background Pattern
Build Your Carousel
Drag and drop any post card below onto a slide, or use the quick buttons to insert content/images instantly!
1/ Most people “prepare for interviews”. If you’re aiming for top spots like @Rippling , @databricks , @stripe , @nvidia , @Razorpay , @JioHotstar etc, you may need to rebuild yourself for that bar. Here’s the PLAYBOOK for 0–5 YOE folks in India. Save this. 🔖
2/ Step 1: Pick your “A list” (5/7 companies max) From the list: Rippling, Databricks, Stripe, NVIDIA, OpenAI, Anthropic, Razorpay, Tekion, Datadog, JioHotstar, Microsoft, Adobe, Salesforce, Atlassian, Glean, Abnormal, ThoughtSpot.. this list is far from complete... go find your own niche and style! Rule: if you’re serious, don’t chase 50 logos. Go deep on a focused 5/7.
3/ Step 2: Know what these companies actually do For each target company, answer in your own words: - What problem do they solve? - Who pays them and why? - What is the core product surface you might work on? If you can’t explain this in 4 or 5 sentences, you’re not ready to interview there.
4/ Step 3: Understand the type of work Rough buckets: Rippling / WorkOS / FusionAuth / Okta → infra + B2B SaaS + HR/identity. Databricks / ThoughtSpot / Glean → data/analytics/AI platforms. Razorpay / Stripe / Tekion / PhonePe → fintech / commerce. JioHotstar / Agoda / Expedia → consumer scale, latency, reliability. Your projects should align (rhyme) with the kind of work they do.
5/ Step 4: Foundation - 3 parallel tracks (12–24 weeks) Every week, split your time: - DSA/Algo - Systems / web fundamentals - One serious, long‑running project No hack: you can’t skip any of the three if you’re aiming for the top.
6/ DSA: the bare minimum bar For 0–2 YOE / undergrads: LeetCode / TuF / GfG grind: problems across arrays, strings, DP, trees, graphs, greedy, bit manipulation. Everyday: 2–4 problems, but review old ones. For 2–5 YOE: Focus more on medium/hard patterns and speed + clarity of explanation. Tag problems by pattern or use a platform that enables this by default (sliding window, binary search on answer, etc).
7/ DSA: how top companies use it Rippling / Databricks / Stripe / NVIDIA etc will use DSA to test: problem‑solving speed, clarity, ability to reason under pressure. Many India product companies still heavily filter on this to manage volume. You don’t need to “love” DSA, you just need to be competent at it!!
8/ Systems & web fundamentals: where you differentiate You want strong answers for: - How does a web request travel from browser → your service → DB → back? - How do you design rate limiting, caching, pagination, search, auth? - Basics of OS (threads, processes), networking (TCP/HTTP), DB (indexes, transactions), queues. Most candidates are shallow here. That’s your gap to exploit!!!
9/ System design: scaled to your experience 0 to 1 YOE / undergrad: Focus on “small” design: URL shortener, basic feed, notifications, leaderboard, search‑within‑app. Talk more about trade‑offs than buzzwords. 2 to 5 YOE: Add: designing an API gateway, payment processing flow, metrics/alerts pipeline, multi‑tenant SaaS, streaming service basics (good for JioHotstar / Razorpay / Databricks). Don’t memorise diagrams!! Understand patterns...
10/ Projects: your single biggest lever Pick 1 or 2 projects that look like: A real product (users, auth, payments, dashboards, etc) With non‑trivial scale/complexity (background jobs, queues, caching, search, etc) For example: Build a mini “Rippling‑like” HR dashboard: employees, payroll, permissions, audit logs. (Medium) Or a mini “OTT‑like” system: ingest content, serve video, track concurrent viewers, live scoreboard. (Hard)
11/ Align project with target company If you’re targeting: - Rippling / WorkOS → multi‑tenant SaaS, RBAC, audit logs, integrations with external APIs. - Databricks / Glean / ThoughtSpot → analytics/dashboard app with ETL, warehouse, query builder. - Razorpay / Stripe → payment flow, retries, idempotency, reconciliation. - JioHotstar → high‑read system, caching, pagination, rate limiting, feature flags. The goal: when they describe their work, you should be able to say “I built a smaller version of something similar”.
12/ Company‑specific seasoning: Rippling Rippling tends to value: - Ownership mentality (“this is my system”) - Ability to move fast without breaking everything - Clear written communication (they are very doc‑heavy) Prep: - Have 2–3 stories where you owned a broken system, cleaned it up, and moved key metrics. - Practice writing 3–5 paragraph design/decision docs for your own projects.
13/ Company‑specific seasoning: Databricks Databricks loves: - Strong fundamentals in distributed systems + data - Comfort with Spark‑like mental models (partitions, jobs, pipelines) - Ability to think about performance and cost together Prep: - Learn basics of Spark / distributed processing concepts. - Build one data‑heavy project (ETL + dashboard). - Be able to reason about why you’d choose batch vs streaming, columnar vs row store, etc.
14/ Company‑specific: Razorpay / Stripe / fintech Key themes: - Consistency, correctness, idempotency - Observability: logs, metrics, alerts - Security mindset Prep: - Know exactly how you’d design “charge a card”, “retry a failed payment”, “webhook with retries + backoff.” - Have real examples of bugs you prevented / debugged in critical flows.
15/ Company‑specific: JioHotstar / consumer scale Expect questions around: - High QPS reads, caching strategies - Efficient pagination and feeds - Handling spikes (match start, sale start, etc) Prep: - Design a live sports score service: millions of users, low latency, frequent updates. - Talk about CDN, cache‑control, push vs pull, backpressure.
16/ Behavioural: this is where many India candidates fail At these companies, “culture fit” ≈ - Can you take ownership without being a hero? - Can you disagree without drama? - Can you learn from failure without excuses? Prep: - For each job/project, write 3 stories: a big win, a big failure, a conflict. - Use them to answer most behavioural questions with specifics: numbers, impact, your exact role. (please don't fake numbers, 2% increase is sometimes a good impact, not everyone has a 50-90% bump across every single project)
17/ 90‑day preparation template (0–2 YOE) Weeks 1–4 - Daily: 3–4 DSA problems - Alt days: systems reading + notes - Start 1 main project, ship v1 by end of week 4 Weeks 5–8 - Daily: 2–3 DSA problems (medium/hard heavy) - 3x/week: system design questions, 45‑min mock with a friend - Project v2: add scale (queues, caching, background jobs) Weeks 9–12 - Daily: 1–2 DSA problems to retain sharpness - 3x/week: mock interviews (DSA + design + behavioural) - Refine resume + company‑specific prep for your 5–7 targets.
18/ 90‑day preparation template (2–5 YOE) Cut brute‑force DSA volume a bit; instead: - More mocks, more design, more storytelling. - Make sure your current work is explained well: architecture, trade‑offs, metrics. - If you’ve already got solid system knowledge: lean harder into company‑aligned projects and storytelling.
19/ Resume & outreach: treat this like a product launch - Single‑page, impact‑heavy resume. - Numbers, not adjectives. - Highlight 1–2 projects that match target companies. - Cold emails/DMs to engineers at these companies > mass job‑portal apply. (do not send templatised msgs to LinkedIn, see if you have a connect, reach out via referrals, I try to get members of @TeamShiksha a referral at almost any company in the country or beyond via my own network. Proof of work is the only ask.) Your goal: in the next 6 to 12 months, get ~5 to 10 real chances to talk to your top‑priority people and make a serious pitch or ask.
20/ Final mindset Stop “trying your luck at big tech/startups”. Be deliberate in training to operate in high‑density environments: better people, better systems, better problems. The interviews are just a noisy test for that. Follow along for tips on interviews and preparing for the specific rounds. Join @TeamShiksha to be around other learners in from across the globe, and be a part of the community. (It's FREE!) 🤖 Excuse Typos! 🔁 Repost to help spread the msg! <a target="_blank" href="https://x.com/sunnykgupta/status/2039997845051433182" color="blue">x.com/sunnykgupta/st…</a>