Kashmiri Pandit๐ฎ๐ณ, Software Engineer - Backend Tech Lead at Accenture๐จโ๐ป, Avid Traveller๐งณโ๏ธ, UFC and cricket Lover๐คฉ๐คผ
New Delhi, India
Joined October 2013
- Tweets4.2K
- Following769
- Followers66
- Likes3.9K
Karan Tikoo retweeted
In your forties and fifties, if you don't have diabetes, high cholesterol, BP, No disease or irregular sleep; if your BMI is under 21; if you have no loans or EMIs; if you drive a car, have a good boss, trek occasionally, can climb 4 floors without panting,then you are blessed!
Karan Tikoo retweeted
Your Resting Heart Rate tells the whole story.
95+ bpm - Heart is working overtime to keep you alive.
90 bpm - Sedentary and stressed.
80 bpm -
Karan Tikoo retweeted
๐จBEST & WORST Months to Switch Jobs in Indian Corporations
January - โ
โ
โ
โ
โ
- Peak Hiring, Budgets Released
February - โ
โ
โ
โ
- Companies aggressively filling roles
March - โ
โ
- FY end, offers slow down
April - โ
โ
โ
โ
- New FY, fresh mandates open
May - โ
โ
โ
- Steady but selective
June - โ
- Post appraisal
July - โ
โ
โ
โ
- Mid year Push Begins
August - โ
โ
โ
โ
- Strong Market activity
September - โ
โ
- Slowing Down
October - โ
โ
โ
- Moderate, act fast
November - โ
- Budgets closing offers rare
December - โ
- Worst month hiring frozen
Karan Tikoo retweeted
Dear job seekers from India.
If you are not getting interview calls from Naukri even after updating your profile, do this.
- Delete your current Naukri account
- Create a new one with different email
- Update a ATS compliant resume that shows relevant skills and experience
- Use metrics in your resume points with right context ( Achieved this by doing that and Star format)
Add some AI relevent experience and you will start getting a lot of calls.
Karan Tikoo retweeted
A heart surgeon named 6 things aging your heart that you think are protecting it:
1. Skipping the dentist.
Karan Tikoo retweeted
Over the next 5 years, the highest paid tech roles will be:
Agentic AI Engineers
AI Evals / Reliability Engineers
Context Engineers
Forward-Deployed AI Engineers
AI Infrastructure / GPU Systems Engineers
AI Product Engineers (systems not wrappers)
AI Security & Guardrails Engineers
Applied Research Engineers who can ship
Not because they write the most code.Because they own the systems everyone else depends on.
Karan Tikoo retweeted
INDIA'S GOT LATENT S2 Bonus EP 3 ft. Deepak Kalal, Ravi Gupta, Agu Stanley
Full Episode in HD Quality nitter.cf/annchalbharti/status/2โฆ
Karan Tikoo retweeted
37ๆญณใง็พๅฝนใฎๅๆฌๅไบบ้ธๆใใใฃใฆใ่ก้ข็ฏใฎในใใฌใใใใใ่
ฐ็ๆใกใซใใใชใใใใใใ
Karan Tikoo retweeted
๐คฏ 91 km diarios durante mรกs de 45 dรญas, con jornadas de hasta 18 h en movimiento ๐คฏ
Nick Fowler ๐บ๐ธ ha establecido un nuevo #FKT del Pacific Crest Trail.
4.270 km entre Canadรก ๐จ๐ฆ y Mรฉxico ๐ฒ๐ฝ en 45 dรญas, 17 horas y 47 minutos.
Lo extraordinario es que lo hizo en modalidad self-supported, cargando su material y recurriendo รบnicamente a puntos de reabastecimiento previamente establecidos.
Karan Tikoo retweeted
WFH any day, I'm fed up with :
- 2 hrs of commute, losing productive hours
- Colleagues discussing broken marriages, situationships, why should I care?
- Forced small talk and pointless meetings
- Being judged by visibility rather than output
- Office politics as collaboration
Karan Tikoo retweeted
AI engineering is saturated with full-stack JS developers who think calling an LLM with LangGraph qualifies them for both AI and ML.
Thatโs why you see lots of AI jobs and lots of disappointment.
For you it may be AI or ML, but organisations treat data, ML and AI as one department.
When I interview, I look for a 50-50 mix so I get someone quality, passionate and versatile engineers.
I can switch between agentic systems, LLMs, time series, data engineering and MLOps as needed.
Why learn so much? You get opportunities when you leave a saturated market with specialised skills.
If everyone knows agents, I look for someone who also knows ML in depth and can help the team with versatile skills in a single hire.
Once you learn the basics of ML, neural networks, feature engineering and FastAPI deployment, you will master the rest over time and crack the field.
Be specialised and versatile. Thatโs why founding engineers and forward-deployed engineers are in demand.
So don't just learn agents, it may not be there tomorrow but ML engineering will be there for decades.
Karan Tikoo retweeted
Many people went to US/UK for MSc Data Science courses in 2023-24.
Yesterday I met my friend who went to UK for this and came back to India for job search. He spent a lot money to learn fundamentals for data science, machine learning, etc.
But never have a GitHub projects and build in public profile, not even good LinkedIn but he thought studying in UK for masters will make his profile so strong. Today he is looking for internship/fresher job in Pune.
Back then I didn't have that money to pursue, I really wanted a good college that time to learn but but as I started build in public, technical writing, and freelancing life changes completely.
I completed my Masters from tier-3 college in Pune and I got a contract based MLE job in Pune in first week of college. I never attended college and passed with 52% in FY and 87% in SY (thanks for ML and project marks weightage)
So in 2023, there was a boom of data science and everyone was going in west for degree. Very few of them got any job but I can bet maximum over 90% students are coming back to India for job search.
Today because of build in public I opened tons of opportunities including current job, prev job, prev to that job, freelancing, working with IBM for Coursera, brand collaboration, etc.
I mean you can pursue the degree but now only build in public matters. Show your work not degree, people will die to hire you.
Karan Tikoo retweeted
If I had 6 months to become a Forward Deployed Engineer.
I'd do this.
Stage 1: Python and API Foundations
FastAPI, async, error handling, webhooks, REST/GraphQL, third-party SDKs.
Stage 2: Customer Integration Patterns
OAuth2, SAML, SSO, Salesforce/Slack/HubSpot APIs, webhook verification, retry logic.
Stage 3: Multi-Tenancy and Data Isolation
Row-level security, tenant identifiers, separate databases vs schemas, data partitioning.
Stage 4: Security and Compliance Basics
SOC 2, GDPR, HIPAA, PII redaction, encryption at rest and in transit, audit logging.
Stage 5: RAG for Customer Data
Secure ingestion pipelines, access control per document, citation tracking, permission filtering.
Stage 6: Deployment Automation
Docker, Kubernetes, Helm charts, CI/CD pipelines, one-click customer environments.
Stage 7: Observability and Dashboards
Distributed tracing, customer-facing health pages, usage metrics, SLA monitoring, alerting.
Stage 8: Incident Management and Debugging
Production debugging, log analysis, rollback strategies, post-mortems, customer communication during outages.
Stage 9: Documentation and Runbooks
Deployment guides, API docs, troubleshooting playbooks, onboarding checklists, knowledge base articles.
Stage 10: Requirements Gathering and Translation
Talking to non-technical stakeholders, translating business needs to technical specs, managing expectations.
Stage 11: Customer Success and Adoption
Usage analysis, feature adoption tracking, identifying expansion signals, reducing churn, proving ROI.
Stage 12: Public Portfolio and Case Studies
Document deployed projects, write implementation guides, share integration patterns, publish success metrics.
Most people stay stuck watching tutorials.
Builders get hired.
(Bookmark it)
Karan Tikoo retweeted
๐๐ฎ๐ฟ๐ฒ๐ฒ๐ฟ ๐ฆ๐๐ผ๐ฟ๐๐๐ฒ๐น๐น๐ถ๐ป๐ด is the ONLY way to get a JOB now, start here!
Recently a CTO told me: "We need faster deployments."
The Software Engineer in the room jumped straight to tooling. I watched the deal die in slow motion.
Not because they are a bad engineer but because they skipped the most important part of the job.
After 15+ years building customer facing outcomes based engineering teams at startups, Google and Microsoft, I distilled what the best ones actually do into 5 steps.
My ๐๐๐ผ๐ฟ๐๐๐ฒ๐น๐น๐ถ๐ป๐ด ๐ณ๐ฟ๐ฎ๐บ๐ฒ๐๐ผ๐ฟ๐ธ ๐ณ๐ผ๐ฟ ๐๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐: ๐ฆ๐๐ข๐ฃ๐ ๐ ๐ฒ๐๐ต๐ผ๐ฑ
๐ฆ: ๐ฆ๐๐๐ฑ๐
Research the customer's business before you ever speak to them. Walk in informed, not blank.
๐: ๐๐ผ๐ป๐ป๐ฒ๐ฐ๐
Push for the executive conversation. Anything below gives you a pre-filtered problem and you'll build the wrong thing.
๐ข: ๐ข๐ฏ๐๐ฒ๐ฟ๐๐ฒ
Walk the customer's process end to end. That CTO who wanted "faster deployments"? The real bottleneck was regression testing eating 40% of cycle time. CI/CD was never the answer.
๐ฃ: ๐ฃ๐ฒ๐ผ๐ฝ๐น๐ฒ
Read the room. The skeptical CTO. The threatened engineer. The VP with the impossible timeline. Same project. Three completely different conversations.
๐: ๐๐
๐ฒ๐ฐ๐๐๐ฒ
Scope projects tied to measurable outcomes. Hand off clean. Leave something the customer can own.
This is what hiring managers at OpenAI, Anthropic, and Google are actually screening for. On top of your AI stack!
๐ข๐ป ๐ฆ๐ฒ๐ฝ ๐ญ๐ฑ, ๐'๐บ ๐ฟ๐๐ป๐ป๐ถ๐ป๐ด ๐ฎ ๐ญ ๐ต๐ผ๐๐ฟ ๐๐ฅ๐๐ ๐๐๐ ๐๐ป๐๐ฒ๐ฟ๐๐ถ๐ฒ๐ ๐ฃ๐ฟ๐ฒ๐ฝ Session teaching exactly this: real discovery reps, live walkthroughs, enterprise scenarios.
If FDE is a role you're moving toward, this is the workshop for you!
๐ฅ๐ฒ๐ด๐ถ๐๐๐ฒ๐ฟ: maven.com/p/c1b081/free-forwโฆ
Save and share with a friend wanting to become FDE!
#fde #forwarddeployedengineer #google #microsoft #anthropic #openai #palantir #storytelling #careerstorytelling
Karan Tikoo retweeted
Two years ago, I struggled to solve basic LeetCode Medium problems. Every new question felt like a completely new puzzle.
Then a Staff Engineer gave me one piece of advice:
"Group your practice by pattern, not by company tag."
My 6-week turnaround:
Week 1: Two Pointers, Sliding Window, Fast/Slow Pointers (Arrays & Lists)
Week 2: Binary Search & Merge Intervals (Search & Ranges)
Week 3: DFS & BFS (Trees & Graphs)
Week 4: Heap & Hash Tables (Lookups & Priority)
Week 5: Backtracking & Greedy (State Search)
Week 6: Dynamic Programming (State Tables)
Once you recognize the pattern within the first 60 seconds of reading a problem, the panic disappears.
Karan Tikoo retweeted
"Later" is a dangerous word, it turned my 2013 Microsoft rejection into 4 years of stagnation at TCS.
By 2018, I was four years deep into TCS Labs, getting paid 50% less than my IIT colleagues for the same
I had two choices: keep complaining or build a ladder out. I chose to exit.
From Aug 2018 - Aug 2022, I worked at Thoughtworks -> Freshworks -> Landed at Microsoft.
My dream came true, even though it took 4 years.
Choose your next move with intention and have the patience to follow through it.
Karan Tikoo retweeted
1. Work really hard on your interview skills like DSA, low-level design, system design, concurrency, writing code fast under pressure, behavioral and values rounds, and negotiation.
So that you go from 3 LPA to 10 LPA to 25 LPA to 60 LPA to 90 LPA to CPA,
and sweep through junior to senior roles without living at the mercy of your company or manager.
2. Work really hard at your office, develop skills like leadership, communication, ownership, handling corporate situations, building with responsibility, and feel the heat of production.
So that you are actually a senior engineer when you get to become one. So people know youโre reliable enough to work with.
3. Work really hard on your side projects, stay updated with current affairs and developments in tech,
find the right people to work with, build a product, market it, sell it, support it, and get funding.
So that after a few years, you donโt have to work for someone else, impress your boss. So that you donโt have to grow linearly in LPAs, but instead grow exponentially.
And the most important thing is to do all of this simultaneously, daily, and consistently.
Get on it!
Karan Tikoo retweeted
I built my 2nd iOS app (thanks to @cursor_ai )
Yesterday it took me 3 prompt gradual update, no fancy skills setup to have a functional app for phone and watch in just few hours.
I started with 3-4 screens and by 3rd revision I have optimized the flow to just 1 screen.
Currently, I am testing it to find bugs, challenges as a user (CX), and what else can be improved.
These both apps are for my own personal use.