Skip to content

Commit

Permalink
vault backup: 2025-02-08 21:38:40
Browse files Browse the repository at this point in the history
  • Loading branch information
abhiaagarwal committed Feb 9, 2025
1 parent 9c99b92 commit 28f02c9
Show file tree
Hide file tree
Showing 2 changed files with 35 additions and 1 deletion.
34 changes: 34 additions & 0 deletions content/management/hiring/interview-questions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
title: Interview questions I've taken from the internet
tags:
- notes
---
- Personality:
- [“ Tell me about the last time you had strong opinions about something and later changed your mind”](https://x.com/buccocapital/status/1886939147643793814)
- ["What was the last thing you taught yourself how to do? How did you learn it?”](https://x.com/buccocapital/status/1886939147643793814)
- ["Tell me about the most difficult feedback you’ve ever received? What was it and how have you changed based on the feedback?”](https://x.com/buccocapital/status/1886939147643793814)
- [“Tell me about a time you faced a crisis? What happened? What was the outcome? What did you learn about yourself?”](https://x.com/buccocapital/status/1886939147643793814)
- Programming
- ["What's the code you wrote a long time ago that it still bugs you that you never got a chance to refactor?"](https://x.com/GrantSlatton/status/1888309119557464503)
- ["What does good code look like to you?"](https://www.reddit.com/r/ExperiencedDevs/comments/oket8j/comment/h58sb22/)
- Variation: "We've hired you, but two weeks from now, you've discovered there's some things we do here that you don't like. What would that be?"
- In your view, what is the hardest problem in software engineering?
- Good answers:
- Caching
- Best answer:
- Requirements gathering
- "Tell me about a time you *identified* a problem and solved it."
- I'm not interested in measuring a person's ability to problem solve tasks given to them, but rather, their ability to identify a _new_ problem, triage it, and then solve it.
- Python
- [[interview-question|When should you pick threading, multiprocessing, or asyncio]]?
- What are your favorite libraries?
- My brownie points:
- Pydantic
- Polars
- What _don't_ you like about Python?
- Lots of good answers here. They should have a _lot_ to say. The only wrong answer is not having anything to say.
- How do you keep up with what's going on in the industry?
- Software differentiates itself from other industries in that
- Ask them about an interesting OSS codebase they worked on / an article they read / whatever and ask them to share it with you _after_ the interview ("that sounds super interesting, can you send me an email after the interview?") and [they actually follow up](https://news.ycombinator.com/item?id=19076264).
- I _really_ like this question. The most important trait in any environment is responsiveness, in that people actually do the shit they say they're going to do.
- The article/whatever isn't important at all, brownie points I guess, but it's not what's being measured.
Original file line number Diff line number Diff line change
Expand Up @@ -135,4 +135,4 @@ services:

Let's say you're doing feature development on tag `my-feature`, but you need to switch to a new branch `my-hotfix` . You can `git switch`, and then with `just up`, it creates a set of containers entirely prefixed with `my-project-${TAG}` without conflicting with the original set of containers. If your spin up process is expensive, this can be a huge time-saver.

Additionally, if you have a local docker volume, say to persist database data, the volume is created with `my-project-${TAG}` as its prefix. Your data won't be polluted between branches, so you can perform database migrations, seeding, etc without getting into a funky state.
Additionally, if you have a local docker volume, say to persist database data, the volume is created with `my-project-${TAG}` as its prefix. Your data won't be polluted between branches, so you can perform database migrations, seeding, etc without getting into a funky state.git p

0 comments on commit 28f02c9

Please sign in to comment.