Golang / GoLang Interfaces and Object Oriented Interview Questions

How does Go differ from classical OOP in terms of inheritance and method overriding?

Go deliberately omits classical inheritance. The Go FAQ explains this choice: inheritance creates tight coupling between classes, makes hierarchies rigid, and encourages deep class trees that are hard to refactor. Go replaces inheritance with composition and interfaces.

OOP Concept Mapping
OOP Concept	Go Equivalent	Notes
Class	struct + methods	No single keyword — type + methods on that type
Constructor	NewXxx() factory function	No special syntax — just a regular function
Inheritance	Struct embedding (composition)	Not IS-A, just method promotion
Method overriding	Shadow via embedding + own method	Outer method takes precedence; call inner explicitly
Abstract class	Interface + unexported concrete type + factory	Contract via interface, implementation hidden
Polymorphism	Interface dispatch (runtime)	Any type satisfying interface can be used
Protected	No equivalent	Go only has exported and unexported (package-private)
super()	Explicit embedded type call (EmbedType.Method())	Must qualify explicitly — no super keyword

// Go 'inheritance' via embedding â it's really composition
type Base struct{ ID int }
func (b Base) Identify() string { return fmt.Sprintf("ID=%d", b.ID) }

type Derived struct {
    Base        // promoted: Derived.Identify() â Base.Identify()
    Extra string
}

// 'Override' by defining the same method on Derived
func (d Derived) Identify() string {
    // 'super().Identify()' equivalent:
    return d.Base.Identify() + " extra=" + d.Extra
}

d := Derived{Base: Base{ID: 1}, Extra: "foo"}
fmt.Println(d.Identify())      // ID=1 extra=foo (Derived's method)
fmt.Println(d.Base.Identify()) // ID=1 (Base's method)

// CRITICAL: Derived is NOT a subtype of Base
// This does NOT compile:
// var b Base = d  // cannot use Derived as type Base
// They ARE both usable through a shared interface:
type Identifier interface { Identify() string }
var id Identifier = d    // OK â Derived satisfies Identifier
id = Base{ID: 2}         // OK â Base satisfies Identifier too

Take quiz

What is the Go equivalent of calling 'super.Method()' in Java?super.Method()

✗ Try again.

Explicitly qualifying the embedded type: d.Base.Method()

✓ Correct! Well done.

Go does not support calling the parent's method

✗ Try again.

base(d).Method()

✗ Try again.

In Go, can you assign a Derived value (which embeds Base) to a variable of type Base?Yes — Go embedding creates a subtype relationship

✗ Try again.

No — embedding is not inheritance; Derived and Base are independent types. Both can be used through a shared interface if they satisfy it.

✓ Correct! Well done.

Yes — but only through an explicit conversion

✗ Try again.

Only if Derived has no additional fields

✗ Try again.

More Related questions...

What is an interface in Go and how does it differ from interfaces in Java or C#? What is the internal two-word structure of a Go interface value? Explain the nil interface trap in Go. Why does a typed nil fail the '!= nil' check? How does Go's implicit interface satisfaction enable duck typing and loose coupling? What is the empty interface (any) in Go and what are its trade-offs? What is the difference between value receivers and pointer receivers in Go methods? How does interface embedding (composition) work in Go? How does Go achieve runtime polymorphism using interfaces? How does Go implement code reuse without inheritance? Explain composition via struct embedding. How does embedding help a struct satisfy an interface? How is the built-in error type defined and how do you implement custom errors? What is the fmt.Stringer interface and how do you implement it? How do type assertions work on interface values and when do you use them? Explain the Go design principle: 'Accept interfaces, return concrete types'. How do Go interfaces enable dependency injection and improve testability? How do you sort custom types using sort.Interface in Go? How do io.Reader and io.Writer demonstrate Go's interface design philosophy? Why can't you always use a value of type T where *T is needed for interface satisfaction? How can a single Go type implement multiple interfaces simultaneously? How does Go implement encapsulation without private/public class modifiers? How do the fmt.Stringer and error interfaces work together and how do you avoid infinite recursion? How do generics relate to interfaces in Go 1.18+ and what are type constraints? How do you implement an abstract type pattern in Go using interfaces and constructors? What is the compile-time interface check idiom and why is it important? How does equality work for interface values in Go? How does the io.Closer interface work with defer for resource management? How does Go differ from classical OOP in terms of inheritance and method overriding? How does http.Handler demonstrate real-world interface design in Go? What is the function-as-interface pattern in Go and how does it enable flexible APIs? What is interface pollution and how do you avoid it in Go? What is the difference between fmt.Stringer and fmt.GoStringer? How does Go's standard library use interface layering for I/O transformation? When should you use reflection instead of interfaces for type-agnostic code in Go? How does thinking about interfaces as 'behaviours, not data' guide better design? What is the interface upgrade (optional interface) pattern in Go? What is the difference between embedding a struct and embedding an interface inside a struct? Are interface values in Go safe to use concurrently? How do you combine table-driven tests with interface mocks in Go? How is context.Context an interface and how does its design demonstrate Go best practices? How does Go embody the Interface Segregation Principle (ISP)? How do type aliases and type definitions differ in relation to interface satisfaction in Go? How does embedding propagate interface satisfaction through multiple levels? What is the zero value of an interface type and how does it differ from a zero-value struct? How do you use wrapper types to adapt existing types to satisfy interfaces in Go? Walk through a complete Go OOP design: payment processing without inheritance. What are the edge cases in Go interface value equality that trip up experienced developers? What is sync.Locker and how is it used in real-world Go concurrency code? Summarise the key rules and best practices for Go interfaces that interviewers test.

Show more question and Answers...

GoLang Concurrency Mastery Interview Questions

	Interviews Questions Java Spring Hibernate DevOps Testing API BigData Web Erlang AI Database Integration Cloud Python Scala Tools Golang SAP	About Javapedia.net Javapedia.net is for Java and J2EE developers, technologist and college students who prepare of interview. Also this site includes many practical examples. This site is developed using J2EE technologies by Steve Antony, a senior Developer/lead at one of the logistics based company. Follow Javapedia updates
	contact: javatutorials2016[at]gmail[dot]com
Kindly consider donating for maintaining this website. Thanks.
	Copyright © 2026, javapedia.net, all rights reserved. Privacy Policy · Terms of Service.

Golang / GoLang Interfaces and Object Oriented Interview Questions

How does Go differ from classical OOP in terms of inheritance and method overriding?

Comments & Discussions

Recently added questions