Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

ViewModel vs AndroidViewModel

EasyCoding00:00
Practice interviewer
In session
5 left
00:00

Your question is ViewModel vs AndroidViewModel. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Context

In Android interviews, this question tests whether you understand lifecycle-aware architecture, dependency management, and separation of concerns.

Core Question

Explain the difference between ViewModel and AndroidViewModel.

Address these points:

  1. What each class is intended for and how they differ in constructor dependencies.
  2. Why AndroidViewModel exposes Application and what trade-offs that creates.
  3. Why modern Android code usually prefers plain ViewModel with dependency injection over AndroidViewModel.

Scope Guidance

The interviewer expects a practical architectural explanation rather than framework trivia. A strong answer should cover lifecycle behavior, testability, coupling to Android framework classes, and when AndroidViewModel is still acceptable.