3 ms·
Depends a lot on the companies and positions you’re interviewing for. I work in technical security these days and did very little in the way of actual code quiz
by d4mi3n 5y ago
Depends a lot on the companies and positions you’re interviewing for. I work in technical security these days and did very little in the way of actual code quizzes compared to when I was a straight up software engineer.
I think it also helps to remember that interviews are two-way. If you see a company with an insane interview process, do you really have confidence in the quality of a team you’d be on when you got to the other side of it?
These days I generally look for and focus on a few things when I interview with a company I’m interested in:
1. How do they make money?
2. Do they understand how they make money? Alternatively, do they understand their market, customers, and product value?
3. How mature is management? Good managers make or break your job satisfaction and dictate how good a company is at hiring & retaining talent, as well as dealing with adversity like professional adults.
4. How much of the work I’m doing is driven by planning as opposed to circumstance. E.g. am I working off a roadmap or expecting to spend the majority of my time handing incidents and fighting fires.
Your mileage may vary, but I suspect these good or bad interview practices will only exist as long as hiring managers allow them to.
- MamaJumba 5y ago> How much of the work I’m doing is driven by planning as opposed to circumstance What question(s) do you ask the companies to get information for this?
- d4mi3n 5y agoI usually ask this question multiple ways with different wording as I go through an interview panel. They're generally along the lines of: 1. What does your roadmap look like? Do you have a roadmap? 2. How reliable is the team about hitting deadlines? Why or why not? 3. Who handles incident response? How frequently does this responsibility rotate? 4. For a given week, how much work is planned vs interrupt driven (e.g. someone needs something by the end of this week and we only learned about it days prior). 5. How much firefighting does this team do? Is this driven by the team's own work or issues in other parts of the organization? Your mileage may vary, there are a lot of ways to get a sense of how a team/org works and what may be important to me may or may not be as important for you. Cheers!
- eins1234 5y ago> I think it also helps to remember that interviews are two-way. If you see a company with an insane interview process, do you really have confidence in the quality of a team you’d be on when you got to the other side of it? Exactly this. As someone who works primarily on frontend, I immediately disqualify any company whose frontend interview process for seniors+ doesn't involve actually building a frontend app/page/component/etc. If I was ok with the prospect of working on a team with senior frontend engineers whose only competency was cramming leetcode, I might as well work at one of the tech giants.