Linterview

Linterview is an informal, rarely standardized term used in some software development communities to describe an interview or evaluation process that centers on linting and static analysis. The word combines lint, the type of tool that scans source code for potential errors and stylistic issues, with interview, signaling a performance assessment focused on code quality and tooling discipline.

In practice, a linterview may take several forms: a candidate may be asked to run a project's linting configuration, fix issues reported by a linter within a set time, and articulate the rationale behind certain rules; or interviewers may query a candidate about their experience configuring and using linters, selecting rules, and integrating lint checks into CI pipelines. Some discussions use the term to refer more generally to a code-quality focused technical interview rather than a literal linting sprint.

Common tools such as ESLint, Flake8, or RuboCop appear in examples, reflecting the language ecosystem of the project. Because linting rules and configurations vary widely, the specifics of a linterview can be tailored to the project's stack and code style guide.

Several caveats apply: the term is not widely standardized and may be considered niche or humorous rather than an official phase of recruitment. It overlaps with broader concepts such as static analysis, code quality assessments, and code reviews.

As coding standards evolve, the role of linting in assessments has grown, and the concept of code-quality interviews persists under various labels. See also lint, static analysis, code quality, code review, programming interview.