Back to Why This Company
Q2Question 2 of 3

Why do you want to join THIS company specifically?

Key Concepts
  • Give researched, company-specific reasons that could not be pasted onto any other company.
  • Reference concrete things: their product, engineering blog, a public talk, a known technical decision.
  • Connect each company-specific reason to a specific career goal of yours for a two-way fit.
  • Cover multiple buckets: product and mission, scale and technical challenge, culture, and growth.
  • Avoid generic flattery like 'you are a great company' with no substance behind it.
  • Show that you treated this interview as a priority, not one of many identical applications.
  • A two-way match: they get your skills, you get the growth and mission you want.

Definition

Give researched, company-specific reasons that could not be pasted onto any other company, tied to your own career goals.
  • Specificity from research – Reference concrete facts about the company: their product, tech stack, engineering blog, recent news.
  • Two-way fit – Connect each company-specific reason to a goal of yours, making it mutual value, not flattery.
  • Multiple buckets – Cover product and mission, scale and challenge, culture, and career growth.
  • Impossible to recycle – The answer should mention something only this company does, so it cannot be copied to another interview.
  • Priority signal – Show that you invested real time researching this company, not just applying broadly.

Imagine Rajesh choosing where to invest his savings. A generic reason is "I want good returns" : true of every bank. A specific reason is "I am choosing National Bank of India because your real-time UPI settlement is the fastest in the market and I want my business payments to clear instantly." The second shows he actually studied the options.

Understanding the Concepts

What is this question really testing?

The interviewer is testing whether you have done your homework and whether your motivation is genuine. A vague answer like "you are a great company" signals you have not researched them. A specific answer signals you treated this opportunity as a real priority.

JAVA
package com.bank.interview;

public class ResearchTest {
    enum Signal { RESEARCHED, GENERIC }

    public static Signal evaluate(boolean companySpecificFact, boolean tiedToGoal) {
        return (companySpecificFact && tiedToGoal) ? Signal.RESEARCHED : Signal.GENERIC;
    }

    public static void main(String[] args) {
        System.out.println(evaluate(true, true));   // RESEARCHED
        System.out.println(evaluate(false, false)); // GENERIC
    }
}

How do you research the company effectively?

Check these sources: the company website, their engineering blog, recent press releases, tech talks on YouTube, job postings (which reveal their stack), and LinkedIn profiles of the team.

JAVA
package com.bank.interview;

import java.util.List;

public class ResearchSources {
    public static void main(String[] args) {
        List<String> sources = List.of(
            "Engineering blog: learn their tech stack and patterns",
            "Job postings: reveals Java, Spring, Kafka, etc.",
            "Press releases: recent product launches or funding",
            "Tech talks: conferences where their engineers spoke",
            "LinkedIn: understand the team composition"
        );
        sources.forEach(System.out::println);
    }
}

How do you structure the answer in buckets?

Organize your reasons from broad to specific: product and mission, scale and technical challenge, culture and engineering values, and your growth path.

JAVA
package com.bank.interview;

public class WhyThisCompany {
    record Reason(String bucket, String companyFact, String myGoal) {}

    public static void main(String[] args) {
        var reasons = java.util.List.of(
            new Reason("Product",   "Real-time UPI settlement",        "I want to build real-time payments"),
            new Reason("Scale",     "Tens of millions of txns/day",   "I want to work at that scale"),
            new Reason("Culture",   "Strong ownership model",          "I want to own systems end to end"),
            new Reason("Growth",    "Fraud detection platform",        "I want to specialize in fraud")
        );
        reasons.forEach(r -> System.out.println(r.bucket() + ": " + r.companyFact() + " -> " + r.myGoal()));
    }
}
TEXT
Product: Real-time UPI settlement -> I want to build real-time payments
Scale: Tens of millions of txns/day -> I want to work at that scale
Culture: Strong ownership model -> I want to own systems end to end
Growth: Fraud detection platform -> I want to specialize in fraud

How do you make the answer impossible to recycle?

Reference something only this company does: a specific product feature, a known technical choice from their blog, or an open-source project they maintain.

JAVA
package com.bank.interview;

public class NonRecyclable {
    public static void main(String[] args) {
        System.out.println("Recyclable: 'You have a great engineering culture' -> any company");
        System.out.println("Non-recyclable: 'Your event-sourced ledger using Kafka, "
            + "which I read about on your blog, is exactly the pattern I want to work with' -> only them");
    }
}

How do you show two-way fit instead of flattery?

Connect their offering to your goal so both parties benefit. "Your fraud platform is exactly the domain I want to specialize in, and I can contribute my payments experience immediately."

JAVA
package com.bank.interview;

public class TwoWayFit {
    public static void main(String[] args) {
        boolean companyOffers = true;  // fraud platform
        boolean iCanDeliver = true;    // payments experience
        if (companyOffers && iCanDeliver) {
            System.out.println("Two-way fit: they get my skills, I get my growth domain.");
        }
    }
}

What is the difference between this question and "Why are you leaving?"

The "why leaving" question is about your push factor. The "why this company" question is about your pull factor. They overlap at the close, but the emphasis differs.

| Aspect | Why leaving? | Why this company? |
|---|---|---|
| Focus | Your growth need | Their specific offering |
| Tone | Forward-looking | Enthusiastic, researched |
| Key evidence | What you have outgrown | What you researched about them |

JAVA
package com.bank.interview;

public class PushVsPullCompany {
    public static void main(String[] args) {
        System.out.println("Push (leaving): I have outgrown my monolith scope.");
        System.out.println("Pull (this company): Your event-driven platform is that scope.");
    }
}

How is this different from "Why are you leaving?"

The "why leaving" question is about your push factor: what growth need drives you. The "why this company" question is about your pull factor: what specifically attracts you here. They overlap but the emphasis differs.

JAVA
package com.bank.interview;
public class PushVsPullFull {
    public static void main(String[] args) {
        System.out.println("'Why leaving' = push: what you outgrew");
        System.out.println("'Why this company' = pull: what specifically draws you");
        System.out.println("Both connect at the close, but emphasis differs.");
    }
}

What are common interview follow-up questions?

Expect: "What do you know about our product?" (covered in Q2477), "What would you change about our product?" (be careful and constructive), and "How does this role fit your five-year plan?" (covered in Q2472).

JAVA
package com.bank.interview;

public class CompanyFollowUps {
    public static void main(String[] args) {
        System.out.println("What do you know? -> See Q2477 for structured research answer");
        System.out.println("What would you change? -> Be constructive, not critical");
        System.out.println("Five-year fit? -> See Q2472 for growth axes answer");
    }
}

Visual Overview

DIAGRAM
┌────────────────────────────────────────────────────┐
│       "Why This Company?" Research Framework        │
├────────────────────────────────────────────────────┤
│                                                    │
│  Research Sources:                                 │
│  ┌──────────┬──────────┬──────────┬──────────┐    │
│  │ Eng Blog │ Job Posts │ Press    │ Talks    │    │
│  └────┬─────┴────┬─────┴────┬─────┴────┬─────┘    │
│       │          │          │          │           │
│       └──────────┴──────────┴──────────┘           │
│                      │                             │
│                      ▼                             │
│  Organize into Buckets:                            │
│  ┌───────────────────────────────────────┐         │
│  │ Product  │ Scale   │ Culture │ Growth │         │
│  │ UPI      │ 10M txn │ Owner-  │ Fraud  │         │
│  │ settle   │ /day    │ ship    │ domain │         │
│  └─────┬────┴────┬────┴────┬────┴────┬───┘         │
│        │         │         │         │             │
│        ▼         ▼         ▼         ▼             │
│  Map each to MY career goal:                       │
│  Company fact → My goal = Two-way fit              │
└────────────────────────────────────────────────────┘

Key Takeaway

I want to join this company specifically because of what you are building at National Bank of India and the fact that it maps exactly onto where I want to take my career. You are moving your core banking onto an event-driven architecture with real-time UPI settlement, and you run an in-house fraud platform at a scale of tens of millions of transactions a day. That is not a generic reason : it is specific to you.

I have deliberately been steering toward real-time payments and fraud. Your real-time settlement and your fraud platform are precisely that domain, at a scale that most places simply do not have. So this is a genuine two-way fit: I get to work on the specific problems I want to specialize in, and I can contribute immediately because I already bring hands-on payments experience.

I also looked at how you work as an engineering organization : your emphasis on ownership and your approach to incidents : and that matches how I like to operate. I want to own systems end to end and be accountable for them in production, and that is clearly the culture here.

The reason I answer this way is that this question is really testing whether I have done my homework and whether my motivation is real. So I give reasons that could not be copy-pasted onto any other company, I tie each specific thing about you to a specific goal of mine, and I show that I can contribute from day one.

Remember one sentence: Give company-specific reasons tied to your career goals that prove you researched this company and cannot recycle this answer anywhere else.

---

Share
Use ← → arrow keys to navigate