Skip to content

Instantly share code, notes, and snippets.

@azemetre
Created May 8, 2019 16:50
Show Gist options
  • Save azemetre/a4d3ad5fed800664bc35ff407ef27045 to your computer and use it in GitHub Desktop.
Save azemetre/a4d3ad5fed800664bc35ff407ef27045 to your computer and use it in GitHub Desktop.
interview Qs
Qs to ask
How does the engineering culture differ from the overall company culture?
What were some of the biggest changes on the team in the last 6 months?
How did your team come to use your current framework(s)/tech stack?
Did they consider other options?
How did they evaluate tradeoffs between them?
What is the build process for the company products?
Single shell script? Executable?
What is the most common reason engineers have left this company?
How do you prevent meetings from overwhelming an engineer’s schedule?
What is your process for writing post-mortems, and are they shared publicly?
How does product management work?
How do you decide what products people work on?
How much say do engineers have over what is built and how it's built?
What project will I first work on, and what metrics will determine success?
How often are engineers expected to provide status updates on a project?
Can you walk me through your development process, from a ticket or task to code on production?
Who sets deadlines and what happens when people fail to meet them?
If company is B2B, ask how many clients they have or who is their largest driver of revenue. Reason why:
A lot of sensible stuff already mentioned. Some will probably disagree with me but my stress levels improved a lot when I switched from employers that had a B2B model with a handful of clients that had enough power to squeeze deadlines and make changes when they please using money (or the lack of potential payment) as leverage compared to a B2C model where employees had real control over the direction of their in-house projects. I don't think it's enough for the business to have a B2C model though it actually needs to be profitable and an expanding team is a more positive sign than a contracting one.
product teams are much more valuable when people understand each other's disciplines
Qs to ask
What is the purpose of the product
what are the goals of the product
how will we know we're successfully
who are the users of the product
what problems are we solving for them
what tasks are critical for users to accomplish
How does this role contribute to larger company goals?
What particular achievements would equate to success at this job? What would success look like?
What metrics would you use to measure success in this role?
How do you deliver negative feedback?
Can you give me some examples of the types of projects I may be working on?
What is the biggest challenge the team has faced in the past year?
In the recent past, how has the company acknowledged and rewarded outstanding performance?
Why did you decide to work at this company?
What is the next step in the process? When do you think you will be making a decision?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment