That's something we aim to figure out together! Don't pre-judge yourself, because we're often our own worst critics. If you're excited to work at Beyond, then we're excited to talk to you.
We want to keep preparation time low. We're not going to ask trick questions or expect you to have the encyclopedia memorised.
Just come as you are, and be ready to have a good casual chat.
For technical interviews, we'll generally want to talk about your solution to the coding challenge, and we may want to see how you would handle some examples of real life situations. These would include potential problems, or potential features to be built.
In interviews we're always time constrained. We have a short time to try to get a good picture of you (and vice versa).
So it's important to structure your answers well. A great tip is to use the Pyramid Principle to structure your message. This means that you're giving the punch line first, followed by the explanation and evidence.
This gives the interviewer the chance to redirect you quickly if you're going in the wrong direction — then we all benefit from a good use of time, and you've got a better chance of succeeding.
If you don't understand the question, don't be afraid to ask for a clarification. Sometimes we do a poor job of explaining things too! It's not always your fault.
There's a few key tips to keep in mind when tackling a technical take-home challenge: