Skip to content

Honor system based frontend interview is inherently flawed #2

@andrlime

Description

@andrlime

"Do not look at background.css" will just encourage people to look, I have a two phased (easy) solution in mind, though it doesn't completely prevent cheating:

  1. Use openpgp to decrypt CSS fetched from some remote server
  2. Host the css file on a remote server, e.g. written with Express (literally will take 15 minutes max), and have env variables on that remote server to decrypt with every GET request

Upsides:

  1. Cool, as we get to encrypt and decrypt stuff
  2. Easy, as it really only takes an hour max to implement
  3. Makes cheating a little bit harder, so any candidates that pass either by just doing the interview or cracking the encryption are probably very smart either way

Downsides

  1. Interviewees can just inspect element. I'm sure there's a way to get around that but I haven't figured it out yet. What I mean by this is, when you inspect element, the CSS is at the bottom of the screen (in Chrome for example).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions