Month 2 is where most reskilling attempts go wrong. The temptation is to consume more courses — to add a second certification, a third tutorial series, a fourth online programme. Resist this entirely. Month 2 is about going deep on one skill until the foundational concepts are genuinely understood, not just recognisable.

Weeks 5–6 Core Concepts Mastery

• Complete the intermediate modules of your primary course — focus on the concepts that appear most frequently in the job descriptions you analysed in Month 1
• After each concept, immediately apply it in a small coded exercise before moving forward. Passive consumption without application does not build skill.
• Identify the 3 most commonly tested technical topics in interviews for your target role — these become your Month 5 preparation priorities

Weeks 7–8 Applied Deepening

• Work through 2–3 domain-specific case studies or solved problem sets in your field (Kaggle datasets for data science, LeetCode for software engineering, case study banks for product management)
• Begin your first portfolio project concept — choose something real, specific, and connected to an industry problem. Generic projects (“movie recommendation system”) are unmemorable. Industry-specific projects (“credit risk scoring for P2P lending”) differentiate.
• Attempt the practice/mock version of the key certification in your field — identify gaps, not to pass yet, but to calibrate where you actually are versus where you think you are

Month 3 is the most critical month of the entire 6-month programme. More high-CTC reskilling journeys succeed or fail here than at any other point. Certificates are table stakes — every applicant has them. Portfolio projects are what separate candidates in a competitive market.

Weeks 9–10 Portfolio Project 1: Complete & Deploy

• Complete your first portfolio project end-to-end — from problem definition through solution to deployment or presentation
• Write a clear README on GitHub: what problem you solved, what approach you took, what results you achieved, and what you would do differently. Hiring managers read these.
• For data/ML projects: deploy a simple demo (Streamlit, Gradio, or Hugging Face Spaces). For web development: a live deployed URL. For product management: a written case study PDF. Tangibility matters.

Weeks 11–12 Portfolio Project 2 + Certification Sprint

• Begin and complete your second portfolio project — this one should be more complex and more directly aligned with a specific target company’s domain or problem type
• Schedule and sit the primary certification exam in your field if relevant (AWS Solutions Architect, Google Professional Data Engineer, CFA Level 1, PMP, etc.) — having an active target date accelerates preparation dramatically
• Update your LinkedIn profile with both portfolio projects: add them to the “Projects” section with descriptions, links, and the skills demonstrated

By Month 4, you have skills and portfolio. The majority of high-CTC job offers — particularly at senior levels — do not come from job portals. They come from networks, referrals, and visibility. Month 4 is entirely about making yourself findable and credible to the right people.

Weeks 13–14 LinkedIn Transformation

• Rewrite your LinkedIn headline to reflect your new direction: not “Looking for opportunities” but “[Target Role] | [Your Key Skill] | [Relevant Domain Expertise]”
• Rewrite your About section to tell the transition story in 3–4 sentences: where you came from, what you have built, and what you are moving toward — lead with the most relevant recent achievement
• Begin publishing one short LinkedIn post per week on something you learned, built, or found interesting in your new domain. Consistency over time creates visibility; single posts do not.
• Connect with 5 professionals per week in your target role — send personalised connection notes referencing something specific about their work

Weeks 15–16 Referral Network Building

• Identify 15 target companies and find at least one current employee at each in a relevant role — not to ask for a job, but to have a 20-minute conversation about the role and the company
• Reach out to 3 people per week for informational conversations — explicit ask: “Could I have 20 minutes to learn about your experience at [Company] in [Role]?” The conversion rate on this is high when the ask is specific and respectful of their time.
• Attend 1–2 in-person or virtual events in your new domain — meetups, conferences, webinars with Q&A. Being seen asking good questions is a form of credibility-building that a LinkedIn profile cannot replicate.

Interview preparation is not studying — it is practicing under conditions that simulate the real thing. The most common failure mode is over-preparing content and under-preparing delivery. Month 5 builds a systematic, repetitive interview practice regime that makes performance under pressure feel familiar rather than foreign.

Weeks 17–18 Technical Interview Framework

• Compile your master list of technical interview questions for your domain — use Glassdoor, levels.fyi, AmbitionBox, and community forums to identify real questions at your target companies
• Answer each question in writing first — full, structured answers. Writing reveals gaps that mental rehearsal hides.
• For coding/technical roles: complete a minimum of 3 timed practice problems per day (LeetCode, HackerRank, CodeSignal). Simulate real conditions — timer running, no hints, no documentation.
• For non-technical roles: write out 5 detailed STAR (Situation, Task, Action, Result) examples from your career that demonstrate each key competency the target role requires

Weeks 19–20 Mock Interview Reps

• Complete a minimum of 4 mock interviews with real people — not friends who will be kind, but peers or mentors in the target field who will be honest
• Prepare your “transition narrative” — a confident, 90-second answer to “Tell me about your background and why you’re making this move.” Practice it until it feels natural, not rehearsed.
• Research each target company’s recent news, product launches, challenges, and competitive position — demonstrate in interviews that you understand the business context of the role
• Begin applying to 3–5 “practice” companies — companies you are less excited about — to warm up your interview skills before the companies that matter most

Month 6 is execution month. The skills are built, the portfolio is live, the network is warm, the interview system is trained. Now the job is to generate a sufficient number of quality opportunities — and then negotiate hard when offers arrive.

Weeks 21–23 Targeted Application Sprint

• Apply to a minimum of 5 high-quality, well-researched applications per week — not 50 spray-and-pray applications, but 5 tailored ones with personalised cover notes and specific role research
• Activate referrals at all target companies where you have had informational conversations — ask directly: “I’m actively applying to [Role] at [Company]. If you’re comfortable, would you be willing to submit a referral?” A warm referral multiplies interview conversion rates by 4–6×.
• Run interviews in parallel — do not wait for one process to conclude before advancing others. Multiple concurrent processes create negotiating leverage and protect against single-offer pressure.

Weeks 24–26 Offer Management & Negotiation

• Never accept a first offer without negotiating — the first number is almost always not the final number. At high-CTC levels, a single negotiation conversation can add ₹3–8 LPA.
• Know your walk-away number before any negotiation conversation begins — and know the market range for the role from salary surveys, LinkedIn Salary Insights, and levels.fyi
• Use competing offers or active processes at other companies as gentle leverage — you do not need to lie or exaggerate, simply indicate that you are “in late-stage conversations with a couple of other companies” if true
• Negotiate the full package: base salary, performance bonus structure, RSU/ESOP grant, joining bonus, and remote/hybrid flexibility. CTC is the headline; total compensation is what you actually live on.

The Salary Negotiation Script

1. Express genuine enthusiasm firstBefore any number discussion: “I’m really excited about this role and the team — the work on [specific project/product] is exactly the direction I want to move in.” Enthusiasm de-risks the conversation before it starts.
2. Ask about the full package before anchoring on base“Could you walk me through the full compensation structure — base, variable, equity, and any one-time components?” Understanding all levers before anchoring gives you more to work with.
3. Counter with a specific number, not a rangeRanges signal uncertainty and invite the employer to anchor at the bottom. A specific number — “Based on market data and my total experience, I was targeting ₹X” — is more effective and more respected.
4. Justify with data, not needNever negotiate based on personal financial need. Always negotiate based on market rate and your demonstrated value. “My research on comparable roles at similar companies suggests ₹X–Y is current market” is a compelling argument. “I need more because of my EMIs” is not.
5. Ask for time to consider any offer“Thank you — I’m very interested and would like 48 hours to review the full offer letter.” This is standard, professional, and gives you time to evaluate and compare without pressure.