ksundong/backend-interview-question

★ 5,824Audience · developerComplexity · 1/5LicenseSetup · easy

Mindmap

mindmap
  root((backend-interview))
    Topics
      Networking TCP UDP
      Operating systems
      Databases
      Java and Spring
    Format
      Collapsible Q and A
      Concise answers
      Interview ready
    Audience
      Korean job seekers
      Backend developers
    Prep advice
      Practice out loud
      Mock interviews
      Deeper study needed

mindmap root((backend-interview)) Topics Networking TCP UDP Operating systems Databases Java and Spring Format Collapsible Q and A Concise answers Interview ready Audience Korean job seekers Backend developers Prep advice Practice out loud Mock interviews Deeper study needed

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Prepare for backend developer job interviews in the Korean tech industry using real panel questions and model answers.

USE CASE 2

Review concise Java and Spring answers the night before a technical interview.

USE CASE 3

Study core networking and database concepts through a Q&A format designed for interview settings.

Tech stack

Markdown

Getting it running

Difficulty · easy Time to first run · 5min

No installation needed, read the Markdown files directly on GitHub or after cloning the repo.

Creative Commons non-commercial license, free to read and share for personal or educational use, but not for commercial purposes.

In plain English

This repository is a collection of interview questions and answers for people applying to backend software developer positions, primarily in the Korean job market. The author compiled the questions from their own job interviews, anticipated questions they prepared for, and material gathered from various online sources. The content is written entirely in Korean. The questions are grouped by topic. Networking covers things like how the web works when you type a URL, the difference between TCP and UDP, how HTTPS encryption works, and what HTTP methods do. Other sections cover operating systems, databases, and general computer science concepts. There are also sections about specific programming languages and frameworks, with the heaviest coverage on Java and Spring, reflecting what Korean backend interview panels commonly ask about. Each question is presented in a collapsible section. You click to expand it and read the suggested answer. The answers are intentionally short and focused on giving a clear, concise response that would work well in an interview setting, not an exhaustive technical essay. The author notes that deeper follow-up questions are expected in real interviews, so readers are encouraged to study topics more thoroughly on their own. The README includes general advice on how to prepare for backend interviews: practicing answers out loud, recording yourself, doing mock interviews with friends, and approaching coding tests with a problem-solving mindset rather than memorizing patterns. The project is licensed under Creative Commons for non-commercial use, and community contributions have been welcomed to fill in gaps, particularly for languages other than Java. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1

I have a Korean backend developer interview tomorrow. Quiz me on the top 10 networking questions from this repo, ask one at a time and tell me if my answer covers the key points.

Prompt 2

Explain the difference between TCP and UDP in a way that would satisfy a Korean backend interview panel, in about three sentences.

Prompt 3

I have a Java Spring interview coming up. Give me the five most likely questions about the Spring IoC container, dependency injection, and bean lifecycle, with model answers.

Prompt 4

What is HTTPS and how does TLS work? Give me a concise interview-ready answer covering the certificate handshake in plain language.

Prompt 5

I'm preparing for an operating systems section. Walk me through what happens from the moment a process is created to when it exits, covering scheduling and context switching.

Open on GitHub → Explain another repo

← ksundong on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.