14 Interview Rejections to Product Company Switch & Salary Negotiation Strategy (Tamil) | Part 2

Business-focused summary (career-switch strategy + negotiation tactics)

1) Switching from service-based → product-based: what to optimize

• Recruiter-filter “SEO” matters
  • The speaker believes many rejections happen because the resume/profile isn’t optimized for keyword-based matching (search/shortlisting systems).
• DSA is positioned as a gatekeeper for product companies
  • Interview difficulty typically escalates toward DSA (data structures + algorithms) rather than shallow “theory-only” prep.
  • For targeting higher packages, the advice is to be able to solve medium → deeper DSA problems (e.g., DP, graph traversal).
• Communication is treated as a major differentiator
  • The speaker reports being rejected for a long time due to poor communication.
  • Improvement came from structuring answers, defining terms clearly, and being honest about gaps.

2) Resume/profile “playbook” (repeatable process)

• Daily application throughput
  • Applying to ~20–30 applications/day.
• Resume tailoring
  • Use required keywords and relevant keywords extracted from the role.
  • The speaker “optimizes resume for each application” by aligning with job descriptions.
• Job-description mining process
  • Example workflow:
    1. Search “Java back-end developer” + “years of experience”
    2. Read ~10 job descriptions
    3. Create a skills list that matches what the market expects
    4. Prepare interview-level knowledge around those technologies (even if not deep in every tool)

Implied framework / workflow

• A GTM-style mindset (for recruiting):
  • Target role → research requirements → tailor “messaging” (resume keywords) → prepare execution (interview readiness) → iterate after rejections.

3) “Why I got shortlist calls” (mechanics + troubleshooting)

• Case example: very low callbacks despite high volume
  • After ~2–5 months and ~600 applications, only 2 calls came.
• Profile search-result targeting
  • The speaker describes seeing ~1800+ search results and that their profile was competing in a crowded pool.
  • They adjust expectations by changing profile settings (salary/intent indicators).
• Salary expectation as a filter
  • The speaker claims setting an aggressive/clear expected compensation reduces calls, because the recruiter’s system likely filters by salary fit.

4) Salary negotiation strategy (execution steps + tactics)

• Core principle
  • Negotiate with the attitude of fit and leverage, while respecting the company’s budget.
• Budget-awareness tactic
  • If the company is a “big one” (examples: Salesforce, Microsoft), the speaker suggests it may have ample budget.
  • For mid-range companies, negotiation should align with a likely budget range.
• Information gathering
  • Ask about market pay using:
    • Company reviews / public signals (e.g., Google reviews)
    • Understanding how much the role pays, then targeting a feasible top-of-range ask
• Anchoring examples (salary bands)
  • Mid-range example: ask for ~12–15 LPA (they may offer ~10–12).
  • Another referenced point: the speaker says they “always ask for 100+” (likely a higher ask; exact unit unclear due to subtitle noise).
• Negotiation with timeline constraints
  • If you have a notice period, tradeoffs may apply:
    • Getting offers before a 15-day / 1-month join window vs. waiting longer
  • The speaker’s stance: choose the best opportunity while balancing loyalty, family constraints, and work-life risk.

Negotiation “playbook” (as described)

• Read job/market → set expectations → choose target company tier → ask within a credible range → justify with strengths (skills + prior experience) → don’t panic if budget is limited → if no budget fit, exit gracefully.

5) Notice period strategy (risk management)

• Immediate joiners are treated favorably
  • Many companies prefer joining within 15 days or less.
• Speaker strategy
  • The speaker says they only submit resignation after getting an offer to avoid losing opportunities due to notice-period mismatch.
• If resigning early
  • Ensure financial runway (idea of 2–3 months salary backup)
  • Consider using the full notice period for intense preparation to reduce unemployment risk.
• Honesty warning
  • The speaker strongly discourages lying about notice period, claiming it can fail even late in the process.

6) What changed after repeated rejections (root-cause + fixes)

• Rejections count & timeframe
  • Reported 14 interview rejections, mostly on-campus.
• Primary root cause identified
  • Communication (not technical ability).
• Communication improvement framework
  • Structure answers like:
    • Define the term first (e.g., “Java is a programming language…”)
    • Provide an example
  • If you don’t know:
    • Be transparent but safe: say you don’t know, then clarify what you understand / what you’re learning
    • Avoid “I don’t know” phrasing that signals incompetence—respond constructively.
• Skill-scope mapping
  • Interview questions assess whether you can structure reasoning, not only recall facts.

7) Common reasons for rejection (ascribed)

• Resume SEO not aligned to ATS/recruiter search.
• Technical mismatch for the role: “new skills not brushed up,” even if added to the resume.
• Misrepresentation / notice period dishonesty.
• Managerial interview mismatches
  • Non-tech factors like relocation/hybrid/working days and personality fit are evaluated.
  • Example: inability to relocate could cause rejection.

---

Key metrics / KPIs mentioned (recruiting & execution)

• Application volume: 20–30 applications/day
• Total applications before breakthrough: ~600 applications
• Callback rate outcome: 2 calls after applying for ~2–5 months (as described)
• Notice period windows
  • 15 days mentioned as a preferred threshold
  • 1–2 months notice period described as common friction
• DSA targeting benchmarks
  • Mentions “10 LPA / 15–17 LPA / 18 LPA / 18-lock / 20+” style tiers (subtitle noise, but concept is clear: higher targets require deeper DSA)

---

Actionable recommendations (condensed)

• Tailor resume keywords per job using job description mining (read ~10 similar JD postings).
• Prepare DSA for product-company interviews:
  • At least medium difficulty, then go deeper for higher packages (DP/graphs).
• Improve communication as a formal habit
  • Define → example → structured explanation
  • Be honest; handle “don’t know” constructively.
• Manage notice period strategically
  • Get an offer before resigning when possible
  • If resigning earlier, build a 2–3 month financial buffer and use notice time for intensive prep.
• Negotiate using credibility and constraints
  • Ask based on role market range and company tier; don’t ask outside budget reality.

---

Presenters / sources mentioned

• Karthik (podcast guest; referenced as the interviewee/speaker about strategy)
• Jayalalitha (podcast host / thanked as providing the opportunity)
• Salesforce, Microsoft, Amazon, Google (mentioned as example product companies)