Corrections

Help keep the field guide accurate.

Report technical errors, stale claims, broken links, unclear explanations, or missing edge cases. Specific corrections with evidence are especially useful.

Open a public correction issue Email a private correction

Include

the page URL;
the exact statement or behavior that needs correction;
the proposed replacement or missing qualification;
a primary source, reproducible example, or short derivation when available.

Do not include

confidential or proprietary interview questions;
employer-protected documents or internal hiring material;
personal candidate information;
API keys, credentials, private repository content, or customer data.

Other suggestions

Topic requests and usability feedback are welcome. Explain the role, interview round, or task the suggestion would support.

A GitHub issue is public. Email is more appropriate for a private note. See the privacy page for details.