Skip to content
tezvyn:

Interview

114 bites tagged Interview — interview questions with model answers, and 60-second explainers.

Content & Copywriting2 min read

What critical on-page SEO elements would you extract from HTML?

Tests if you know which HTML elements search engines use to index pages. Strong answer: title tag, H1, and meta description shape search results and topical relevance. Red flag: claiming meta descriptions directly affect rankings or conflating H1 with title.

Content & Copywriting2 min read

Outline an NLP pipeline to categorize reviews and identify pain points

Tests text mining pipeline design. Answers cover deduplication and normalization, then clustering or topic modeling for categories, plus sentiment analysis to rank pain points. Red flag: skipping validation or jumping to LLMs without cleaning.

Computer Vision2 min read

How does a Bayer filter capture color and what is demosaicing?

This tests CFA sampling tradeoffs. The answer covers the RGGB mosaic, demosaicing as interpolation of missing channels, and moire or zippering artifacts. A red flag is believing pixels capture full RGB natively or that demosaicing is only averaging.

Android & Kotlin2 min read

Diagnose Android UI jank using Android Studio's Profiler

Start with CPU Profiler for traces over 16ms and main thread blocking; check Memory Profiler for GC. Isolating frame drops to main thread work or GC via Android Studio Profiler. Using Logcat alone or blaming hardware.

Android & Kotlin2 min read

What is an Android memory leak? Give a Context example and fix.

Tests understanding of Activity Context retention preventing GC. A strong answer defines a leak as unreachable objects, gives a static singleton example, names LeakCanary, and fixes it with Application Context. Red flag: blaming GC or suggesting System.gc().

Android & Kotlin2 min read

What is the difference between test and androidTest source sets?

Say test runs on the JVM for unit tests mocking Android classes, while androidTest runs on device for instrumented tests. This tests understanding of test environments. Saying both need a device or treating them interchangeably.

Android & Kotlin2 min read

What is Dependency Injection and Hilt's benefit over manual instantiation?

Tests your grasp of inversion of control and why frameworks matter. A good answer defines DI as supplying dependencies from outside, states Hilt automates object graph creation and scoping, and notes manual instantiation scatters construction logic.

Android & Kotlin2 min read

How do you pass data between Fragments with Jetpack Navigation?

Define args in nav graph XML, navigate with generated Directions, read with navArgs() in target Fragment. Type-safe argument flow in Navigation. Direct Fragment constructors, manual Bundles, or Activity Intent extras.

Android & Kotlin2 min read

App crash: debug with Logcat and breakpoints in Android Studio

This tests systematic debugging and Android Studio fluency. A strong answer reproduces the crash, filters Logcat for the fatal exception, sets a breakpoint on the offending frame, and inspects variables.

Android & Kotlin2 min read

What is the difference between project-level and module-level build.gradle?

Project level sets plugin repos and shared versions; module level sets dependencies, build types, and flavors. Gradle scope in multi-module Android projects. Claiming both files do the same thing or misplacing plugins.

Android & Kotlin2 min read

Explain val vs var in Kotlin and null safety risks

Val is read-only, var is mutable; nullables use ? like String?; risk is NullPointerException if checks are missed. Kotlin mutability and compile-time null safety. Calling val deep immutability or defaulting to !!.

Analytics & Metrics2 min read

What is the difference between a metric and a KPI?

Tests strategic vs operational measurement discernment. Answer: KPIs track critical goals; metrics track processes. Page views are a metric; conversion rate is the KPI. Red flag: calling all data KPIs or using page views as success proof.

Analytics & Metrics2 min read

Explain the difference between correlation and causation with a software example.

Tests whether you distinguish association from causation to avoid blaming production issues. A strong answer defines both concepts, names a confounding variable, and gives a software example with a common cause. Red flag: claiming correlation is causation.

Analytics & Metrics2 min read

Conversion metric dropped suddenly with no recent deployments; debug instrumentation causes

Distinguishing real regressions from telemetry pipeline failures. Segment by device, channel, and geography to spot uniform loss signaling a tagging break; verify vendor delays and sampling; check for consent or ad-blocker shifts.

Agile & Scrum2 min read

From an engineer's perspective, when does Cycle Time begin and end?

Tests if you set Cycle Time boundaries to expose wait states past coding. Strong answer: starts at In Progress, ends at Done or production, includes review/test, excludes backlog queues, and distinguishes from Lead Time. Red flag: starting at ticket creation.

Agile & Scrum2 min read

What is the primary purpose of a WIP limit in Kanban?

Tests whether you see Kanban as a flow system, not just a board. A great answer says WIP limits constrain multitasking to reduce cycle time and improve throughput by prioritizing finishing over starting. Red flag: saying limits are for tracking progress.

Agile & Scrum2 min read

What is a Scrum of Scrums purpose and what technical info is shared?

Multi-team sync for blockers, dependencies, API changes, integration risks; not a status meeting. Cross-team coordination in scaled Scrum. Treating it as a lead standup with PM-style updates.

Agile & Scrum2 min read

Describe the initial columns for a new Kanban board and their purpose

Tests whether you understand Kanban as a flow visualization tool. A strong answer names Backlog, To Do, In Progress, and Done, explaining each as a handoff or state change. Red flag: adding too many columns upfront or conflating the board with Scrum.

Get Interview bites daily.

Five a day, five minutes, offline. With quizzes so it sticks.

Open testing — you’ll join as an early tester.