easyConceptCodingEntry

Skip the definitions. Show me encapsulation, abstraction, inheritance and polymorphism, each in about ten lines of code, and then tell me when inheritance is the wrong tool.

OOP examples beat definitions: a class refusing a bad withdrawal shows encapsulation, a caller depending on an interface shows abstraction, a subclass reusing a parent method shows inheritance, and one loop running different overrides shows polymorphism. Inheritance is wrong when the child breaks a parent promise.

4 min readUpdated 2026-10-10Target archetype: Enterprise Captive

Short answer

OOP examples prove understanding faster than definitions. Encapsulation is a class that refuses to enter an invalid state. Abstraction is a caller that depends on an interface and not on the class behind it. Inheritance is a subclass reusing its parent's code, and polymorphism is one call running different code depending on the object. Inheritance is the wrong tool when the child cannot honour everything the parent promises.

Practice answering out loud

What the interviewer is scoring

Does each snippet show the pillar doing a job, such as a rejected invalid state, rather than only declaring a keyword
That the abstraction example has a caller depending on the interface, not just an interface sitting alone
Can they separate compile-time overloading from run-time overriding when asked which one is polymorphism
Whether they produce a concrete case where inheritance breaks a parent's promise, and rewrite it with composition
Writes code that would compile, with access modifiers and return types in the right places

You have 2 more free pages. Create a free account for unlimited access.

Was this answer helpful?

Likely follow-ups

Your BankAccount has no setBalance method. How would a test put an account into a known starting state?
Change Shape from an interface to an abstract class. What can you now put in it, and what have you given up?
Which method runs if Circle overloads area(double scale) and you call shape.area() through a Shape reference?
Rewrite the Employee hierarchy so contractors and salaried staff share payslip logic without a common superclass.

Related Topics

#polymorphism #composition #java

Why the panel wants code, not the four OOP pillars recited

Every candidate in a campus viva can say "encapsulation is wrapping data and methods together". It tells the interviewer nothing, because it is the sentence from the textbook. Ten lines of code show whether you know what each pillar is for. The OOP examples below are Java 17, which most fresher panels accept, and each one is built so the pillar does visible work. Keep the domains boring (accounts, employees, shapes) so the panel spends its attention on the OOP pillars and not on your business logic.

If you want the design reasoning behind each pillar, the four pillars and abstraction versus encapsulation page covers it. This page is the version you write on a whiteboard.

Encapsulation: the class guards its own rule

public class BankAccount { private long balance; // no one outside can set this directly public void deposit(long amount) { if (amount <= 0) throw new IllegalArgumentException("amount must be positive"); balance += amount; } public boolean withdraw(long amount) { if (amount <= 0 || amount > balance) return false; // the rule lives here only balance -= amount; return true; } public long balance() { return balance; } }

Say the rule out loud: the balance can never go negative. There is no setBalance, so no caller anywhere can break that rule. A class with a private field and a public setter for it is not encapsulated in any useful sense.

Polymorphism: one loop, different code per object

Adding a Triangle means one new record and no change to total. That is the claim worth making for polymorphism: new cases without editing working code.

Expect the follow-up "is overloading polymorphism too?". Overloading, such as print(int) beside print(String), is chosen by the compiler from the argument types. Overriding, as above, is chosen at run time from the object. Textbooks call these compile-time and run-time polymorphism. When an interviewer says polymorphism without qualification, they almost always mean the run-time kind.

When inheritance is the wrong tool

The Java library ships the standard warning. java.util.Stack extends Vector, so a stack inherits every list operation, including inserting at any index.

Stack<String> s = new Stack<>(); s.push("a"); s.push("b"); s.add(0, "z"); // legal, inherited from Vector, and no longer last-in-first-out

A stack is not a list, because it cannot honour the list's promise that you may insert anywhere. Code reuse was the motive, and the child inherited operations that break its own rule. The fix is composition: a stack class holding a list or an ArrayDeque and exposing only push, pop and peek.

import java.util.ArrayDeque; import java.util.Deque; public class SafeStack<T> { private final Deque<T> items = new ArrayDeque<>(); // has-a, not is-a { items.push(item); } T { items.pop(); } T { items.peek(); } }

Of the four OOP examples, this is the one panels most often extend, because "when would you not inherit?" separates candidates who memorised the pillars from those who have used them. The test to say in the viva is substitution. If any code written for the parent could misbehave when handed the child, inheritance is wrong. The Liskov substitution page goes deeper into the rule the compiler cannot check.

Each of these OOP examples earns its marks by doing something: a refused withdrawal, a swapped notifier, an inherited payslip, a loop that never changes. Reach for inheritance only when the child can keep every promise the parent makes.

Skip the definitions. Show me encapsulation, abstraction, inheritance and polymorphism, each in about ten lines of code, and then tell me when inheritance is the wrong tool.

Short answer

What the interviewer is scoring

Was this answer helpful?

Likely follow-ups

Related questions

Related Topics

What the interviewer is scoring

Why the panel wants code, not the four OOP pillars recited

Encapsulation: the class guards its own rule

Abstraction: the caller does not know what is behind the interface

Inheritance: the child reuses what the parent wrote

Polymorphism: one loop, different code per object

When inheritance is the wrong tool

Skip the definitions. Show me encapsulation, abstraction, inheritance and polymorphism, each in about ten lines of code, and then tell me when inheritance is the wrong tool.

Answer

Short answer

What the interviewer is scoring

Was this answer helpful?

Likely follow-ups

Related questions

Related Topics

What the interviewer is scoring

Why the panel wants code, not the four OOP pillars recited

Encapsulation: the class guards its own rule

Abstraction: the caller does not know what is behind the interface

Inheritance: the child reuses what the parent wrote

Polymorphism: one loop, different code per object

When inheritance is the wrong tool