twipped/interviewthis

★ 6,893Audience · developerComplexity · 1/5LicenseSetup · easy

Mindmap

mindmap
  root((interviewthis))
    What it is
      Interview question list
      Community maintained
      Plain Markdown doc
    Topic Sections
      Position and role
      Dev process and tools
      Team coordination
      Remote work and culture
    Use Cases
      Pre-offer research
      Team assessment
      Fork and personalize
    Audience
      Software developers
      Job seekers

mindmap root((interviewthis)) What it is Interview question list Community maintained Plain Markdown doc Topic Sections Position and role Dev process and tools Team coordination Remote work and culture Use Cases Pre-offer research Team assessment Fork and personalize Audience Software developers Job seekers

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Pick questions to ask a hiring team about their development process, code review practices, and release schedule.

USE CASE 2

Use the on-call and monitoring section to understand what your pager-duty situation would actually look like.

USE CASE 3

Fork the list and trim it to your personal priorities before your next technical interview.

Getting it running

Difficulty · easy Time to first run · 5min

No restrictions mentioned, use, fork, and adapt freely.

In plain English

InterviewThis is a community-maintained list of questions that software developers can ask employers during the hiring process. The author created it after repeatedly accepting jobs and discovering unfavorable things about those companies that they would have wanted to know beforehand. Over time, other developers added their own contributions, making it a broad collection covering many angles of what a software job actually looks like day to day. The list is organized into sections covering different parts of how a company operates. The Position section helps you understand what you would actually be doing and how long you might stay in the role. Developer Coordination covers how teams are structured, whether people pair-program, how work gets assigned, and what the management style looks like. The Development Process section gets into technical practices: source control methods, branching strategies, code review, testing, environments, and release schedules. There are also sections on monitoring and on-call responsibilities, remote work policies, culture, and compensation. The README makes clear this is not a checklist to hand to an employer. It is a reference to help developers think through what matters to them and pick the questions most relevant to their situation and the stage of the interview. Some questions are only appropriate once you have already moved past the initial HR screen and are talking to the team you would actually join. The repository accepts pull requests and issue reports from anyone who wants to contribute a new question. The maintainer may reword or decline questions that do not fit the spirit of the list. The project has no code, no build process, and no license restrictions. It is just a plain-English document, formatted in Markdown, stored in a public GitHub repo so that anyone can fork it, adapt it, or send improvements back.

Copy-paste prompts

Prompt 1

I have a technical interview tomorrow at a startup. Using the InterviewThis list, give me the 5 most important questions to ask about their development process and team structure.

Prompt 2

I am evaluating a remote-first role. Based on the InterviewThis question bank, which questions should I prioritize about remote work policies and async communication?

Prompt 3

Using InterviewThis as a reference, help me prepare a cheat sheet of questions to ask during an HR screen focused on compensation and company culture.

Prompt 4

I am interviewing at a company with on-call responsibilities. Which InterviewThis questions should I ask to understand their incident response and monitoring practices?

Open on GitHub → Explain another repo

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

Verify against the repo before relying on details.