
Honest Interview
@HonestCoding
The real questions we should ask in coding interviews.
You might like
The feedback was largely positive, but we've decided not to move forward. Good luck at your next interview.
Us: "Can you start tomorrow?" You: "Tomorrow is Thanksgiving." Us: blank stare
Are you okay with feeling like you are making no forward progress for the next two years or until we run out of money?
I hope you like playing Risk, because we love to drink and bro out over a game.
How do you add an entry to /etc/hosts and why would you do it?
How much would you say you can drink in one night?
Welcome to the lunch portion of the interview. I'm here to force you to talk more despite all of the talking we've forced on you so far.
You have one hour. We are looking for elegant abstractions, thorough testing, and exactly the approach that would have taken us days to do.
Here is a file full of "data." We want you to make sense of it. We can't.
We need you to tell us how this API call goes through our Rails monolith. No really. Can you tell us?
Your co-worker is about to reimplement Python's Subprocess in Ruby. What do you do?
We'd like you to print the current date and time in a given time zone. Account for date changes. Can you do this in Ruby? We don't know how.
United States Trends
- 1. Wirtz 51.7K posts
- 2. Elander 3,235 posts
- 3. East Wing 141K posts
- 4. $TSLA 43.9K posts
- 5. Estevao 36.1K posts
- 6. Tony Vitello 12.2K posts
- 7. Danny White 2,778 posts
- 8. Ajax 72.8K posts
- 9. Tosin 8,179 posts
- 10. SNAP 648K posts
- 11. #YesOnProp50 7,254 posts
- 12. Hamburger Helper 1,022 posts
- 13. Atalanta 15.3K posts
- 14. Juve 19.6K posts
- 15. Frankfurt 51.7K posts
- 16. Vicario 2,875 posts
- 17. Ekitike 26.5K posts
- 18. Caicedo 19.8K posts
- 19. Vini 20.7K posts
- 20. Donte 1,074 posts
Something went wrong.
Something went wrong.