Built by Android developers

Help make Android interviews less opaque

Share the question that caught you off guard, correct an answer that needs a sharper boundary, or document what an interview was actually like. Use the guided form. No GitHub account or Markdown required.

Contribute anonymously Use GitHub instead
  • No sign-up
  • Rich-text editor
  • Maintainer reviewed
Choose what to share

Five ways to help other Android developers

Each form asks only for the information maintainers need to review that kind of contribution.

Question and answer

Add one focused interview question with a precise answer, boundaries, and sources.

Creates a review PR

Content correction

Point to an outdated, unclear, or incorrect statement and propose the exact fix.

Creates a tracked issue

Topic guide

Propose a study path for an Android or Kotlin area that deserves deeper coverage.

Creates a review PR

Interview experience

Share the rounds, questions, outcome, and takeaways. Anonymous submissions are welcome.

Creates a review PR

Article or deep dive

Write a longer practical guide about Android engineering or interview preparation.

Creates a review PR
How it works

A clear path from your draft to publication

1

Write in the browser

Choose a contribution type and use the rich-text editor. No account or local setup is required.

2

We create the review

The site turns publishable content into Markdown and opens a pull request. Corrections become tracked issues.

3

A maintainer checks it

We review technical accuracy, clarity, privacy, and editorial fit before anything appears on the site.

Contribute anonymously
For repository contributors

Prefer working in GitHub?

Every published page is still plain Markdown in the open-source repository. Fork it, make a focused change, run the checks, and open a pull request.

Open the repository Read CONTRIBUTING.md
1

Fork & clone

Fork the repo on GitHub and clone it locally. Run npm install && npm run dev to preview your changes.

2

Add a content file

Drop a Markdown file into the right folder under src/content/. Each question, post, or experience is a single file - copy a template below.

3

Open a pull request

Commit on a new branch, push to your fork, and open a PR. A maintainer reviews for accuracy and merges. Cloudflare Pages deploys automatically.

Content templates

Copy the relevant structure when contributing through GitHub. The browser form generates this frontmatter automatically.

Interview questionsrc/content/questions/ View template

Keep each question focused on one concept. Answers should name the exact API, mechanism, failure condition, and important caveat. 

---
question: "What is structured concurrency in Kotlin coroutines?"
topic: coroutines        # must match a topic id in src/content/topics/
difficulty: mid          # junior | mid | senior
tags: ["coroutines", "scopes"]
author: "Your Name"      # optional
---

Structured concurrency ties the lifetime of coroutines to a **scope**...

\`\`\`kotlin
viewModelScope.launch {
    val user = async { repo.user() }
    val feed = async { repo.feed() }
    render(user.await(), feed.await())
}
\`\`\`

Explain trade-offs, edge cases, and what an interviewer is really probing for.
Interview experiencesrc/content/experiences/ View template

Anonymize freely. Never include interviewer names, personal information, confidential prompts, or NDA-bound material. 

---
company: "Acme Corp"
role: "Senior Android Engineer"
level: "Senior"          # Intern | Junior | Mid | Senior | Staff+
location: "Bengaluru, India"
remote: false
outcome: "Offer"         # Offer | Rejected | Withdrew | In Progress | No Response
date: 2026-05-12
author: "Anonymous"
tags: ["compose", "system-design"]
---

## Round 1 - Phone screen
What they asked, how it went...

## Round 2 - Coding
...

## Takeaways
What you'd do differently next time.
Topic guidesrc/content/topics/ View template

The filename becomes the topic ID referenced by questions. Check existing topics first so the scope does not overlap. 

---
title: "Coroutines"
description: "Structured concurrency, scopes, dispatchers, and Flow."
category: "Kotlin"       # groups topics on the index page
order: 10                # lower sorts first
icon: "⟳"
---

Optional overview shown above the questions on the topic page.
Article or deep dive src/content/blog/

Include title, description, date, author, and tags frontmatter. Markdown and MDX are both supported.

Before you send it

What makes a strong contribution

  • Be technically precise. Name exact APIs, lifecycle states, exceptions, and failure conditions.
  • Separate guarantees from common behavior. Call out version or device dependencies where they matter.
  • Respect privacy. Remove personal, proprietary, and NDA-bound information.
  • Keep it focused. One question, correction, experience, or article per submission is easier to review.