Interviews can be tough! Especially when you’re trying to find your first developer role. Asking “tell me about a typical day” often results in cookie cutter answers. During the interview, it’s your time to shine and also ask questions to get to know them better. After all, you’ll be spending 40 hours a week with them and sometimes you’ll be shoulder to shoulder.
After a few years of experience, these are questions that I asked during interviews. Some of these questions are vulnerable (from prior experience) while others were process related. I hope this helps spark a few ideas of what to ask. ✨
When in doubt (or if you go blank) it’s okay to ask:
- Can you tell me more about…
- I’m curious about…
- Oh? Why?
- Why not?
How does the team celebrate success?
It’s easy to keep pushing forward towards the next ticket or project without pausing to reflect. Without acknowledgment of the team’s work or success, you may start to feel burn out. Pausing to celebrate isn’t the same as a retrospective, it’s truly a time to celebrate. 🎉🎉 It doesn’t have to be a fancy ordeal. Good job, well done. We did it. We made it.
- How do you define success?
- What does the team do for fun?
- Does the team have a favorite go-to restaurant?
What can you tell me about work/life balance?
As developers, we’re story tellers and problem solvers. It’s easy to bring our work home… whether that’s reaching for the laptop after hours or sending just one more message late at night. Embrace boundaries. Time at home is time for family/friends, hobbies, and living outside of work.
- Other than critical production issues, do you send emails late at night?
- What’s the expectation for communication outside of work hours?
- Is there an on-call schedule?
- What do you like to do on the weekends?
Halp! When I’m given a task that’s “new territory” and I have a lot of “I don’t know yet” answers, how do you respond?
An African problem sums it up well, “If you want to go fast, go alone. If you want to go far, go together.” You’re looking for a graceful answer.
- Who would I go to for questions?
- Is there a dedicated time for pairing /office hours / slack channel?
- Will you describe the pair programming process?
- How often do you pair program?
- How do you describe quality pair programming?
- What resources (books, subscriptions, learning allowance) are available?
How does the team stay in the loop for current work?
Whether it’s daily standup or chatting in a slack channel, the team should know what they’re working on and what’s next. Sometimes priorities shift quickly and that’s okay. There should be a go to place for communication. (Example: dedicated slack channel or email distribution list.)
- Is there a project manager and/or scrum master?
Can you give me a quick walk-through of a ticket from creation to completion?
This is all about the process. Tickets should be thoughtfully created with enough information before you begin the work. The ticket should be clear and have “success criteria” or a “definition of done” otherwise your small ticket may turn into an epic.
After the work has been merged, it may go through a PR pipeline to run tests, tested by Quality Assurance (QA), and then pushed to production. This is a chance to see if a company implements Continuous integration (CI) and continuous delivery (CD) commonly referred to as CI/CD. Some companies may do scheduled released based on sprints. Asking will help you know if Thursdays are stressful.
- Who creates the tickets? (project manager, request manager, product owner)
- Who decides the due date on a ticket? (the team should decide this)
- What is the work rhythm? (sprints, commitments, etc.)
- How often is work pushed to production?
- Is there a QA team?
Will you describe the Pull Request (PR) process?
Instant approvals are quite scary! Intentional small PRs shouldn’t take long to review, so it should be a red flag if things are merged in without a review. Eek! Comments on a PR can have negative associations, but you’re looking for kind and thoughtful communication.
- How many people need to approve a PR before merging?
- Are there CODEOWNERS?
- Are tests required for PRs? 😍
- What would cause you to block a PR?
What does “moving up” look like? Is there a plan in place to help developers grow?
Listen closely for red flags. This a bit of a trick question. 😬 There are some amazing senior engineers that are also great leaders, but keep in mind that leadership & development skills are completely different. Having “senior” in the title doesn’t automatically make you a great leader. (Ouch) If you’re interested in leadership, be sure to specifically ask about personal and leadership development.
- What would it look like to move from a junior position to mid-level position?
- How often will I receive feedback or reviews?
- Are there 1:1s? How often are they? (If the answer is rarely, run quickly! 🚩)
All teams experience conflict. It can be healthy or unhealthy. Can you talk about how the team handles conflict?
You shouldn’t have to wait until the project is over to share your woes. Healthy conflict can strengthen your knowledge, sharpen your skills, and open tons of new possibilities. Unhealthy conflict can cause constant stress and heart ache. The team should trust each other and should be able to communicate openly.
- How often do you have retrospectives?