Twipped

InterviewThis: Questions for Developer Job Interviews

InterviewThis is a community-contributed reference list of questions developers can ask prospective employers. Use it to investigate a role, engineering practices, on-call expectations, workplace culture, and company policies before accepting an offer.

View on GitHub Compare
Stars
6.9k
Forks
400
Stars, last 30 days
-2
Last commit
4.2 years ago
Contributors
17

Our take

Inactiveno commits in over a year

Health score

28/100

How it is scored
Activity
19
Community
50
Issues
21
Pull requests
20

-2 stars in the last 30 days

InterviewThis is a broad, practical prompt library for assessing a prospective employer, but its inactive maintenance and unasserted license warrant caution for teams adopting or redistributing it.

Good fit if

  • You want a wide-ranging set of prompts to adapt for your own interviews.
  • You are a developer evaluating engineering practices, culture, or operational expectations.
  • You can use the material as a reference rather than treating every question as mandatory.

Look elsewhere if

  • You need a recently maintained resource: the project has had no commits or releases in over a year.
  • You need a clearly asserted license for reuse or redistribution: the repository's license is reported as NOASSERTION.
  • You want tailored advice for a specific role or interview stage rather than a comprehensive question list.
All health signals
Last commit2022-08-28 (4.2 years ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors17 (top contributor: 63% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age13 years

Checked on 2026-10-25 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

6,907

Forks

398

Change since Nov 16, 2026: 0 stars·0 forks

Overview

InterviewThis is a community-contributed list of questions developers can ask prospective employers during the hiring process. It helps candidates uncover details about a job and company that may not come up in a standard interview, from development workflows and team culture to on-call duties and benefits.

The list is a reference, not a script or checklist. Choose questions that fit the role and interview stage, and use your judgment about when to ask them. See the repository for the complete list and contribution guidance.

Key Features

  • Covers role expectations, responsibilities, and compensation.
  • Suggests questions about team structure, collaboration, and project management.
  • Explores development practices, including source control, code review, testing, releases, and technical debt.
  • Includes questions about monitoring, incident response, and on-call work.
  • Addresses remote work, open-source contributions, and personal projects.
  • Provides prompts for evaluating architecture, company culture, career development, and benefits.
  • Includes additional questions for PHP, JavaScript, and IT operations roles.

Use Cases

  • A developer preparing for interviews can select questions that clarify day-to-day responsibilities and team expectations.
  • A candidate comparing offers can investigate engineering processes, workplace culture, benefits, and company stability.
  • Someone considering a remote role can ask about communication, working hours, travel, and home-office support.
  • A developer interviewing for an operations-heavy position can explore incident response, access controls, infrastructure, and on-call policies.

Getting Started

Open the repository, review the list, and choose questions relevant to the position and interview stage. The README explains how to contribute questions.

License in Plain Words

No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.

Considerations

  • The measured project health is Inactive, with no recent commits, releases, merged pull requests, or issue closures. The repository has contributions from multiple people, so contributor activity is not concentrated in one person, but that does not indicate current maintenance.
  • The list spans many topics and includes some questions that may not apply to a given role or be suitable for an initial interview. The project explicitly advises using discretion.
  • The repository's license is reported as NOASSERTION. Check the repository for licensing terms before incorporating or redistributing its content.

Found this useful?

Share it with someone who would like InterviewThis.