Experienced Devs

Here are some from a text file I keep around for these purposes:

• What has your team been working on recently? What new changes have you shipped in the last six months?
• What is the biggest difficulty your team is facing right now?
• How long has the team existed and how long have you been managing it?
• Is the team all remote? Are you?
• How long does it take for code to be deployed after being committed?
• How often do team members move teams?
• What kinds of (soft or hard) skills do you need most on the team right now?
• Do you have a defined onboarding process?
• How long does it take for people to get up to speed as new hires? How much would a new hire be doing in six months?
• Does the team maintain deployment infrastructure? Production infrastructure? Is there an on-call rotation?
• What does your planning cycle look like? Scrum? Kanban? Meetings?
• What's one thing you would change or improve on the team if you could snap your fingers?
• What would you like to be doing less and more of on your team?
• How does the product representative interact with the eng team?
• Do you have a career ladder, with levels, and expectations at each of the level defined?
• What is your performance review cycle like? 1:1s?

lots of questions, I haven't moved jobs in a while because I'm happy where I am but I've added to these even when interviewing people to join my team.

• what is your policy for overtime or comp time when there are evening or weekend emergencies?
• how often do people tend to need to be available outside of standard working hours?
• what does success in this position look like for me 6 months down the road?
• how often do tasks and priorities change last minute?
• how long has the average person been on the team?
• what is the policy on sick days, vacation days, etc
• what is the remote work policy
• how flexible are they on work hours? if it's a salary position, generally you will have work to do, but many bosses won't care if you take a 2-hour lunch and do some grocery shopping or whatever. as long as overall you're doing your work and getting things sorted.
• when interviewing with team members instead of just the new management, it's a good idea to ask them about the managers style, and what they like about working there.
• (generally by the interview you should have some idea of what the actual job entails, but if not, ask a bunch of questions related to that. what kind of system are you developing for, is it primarily supporting new feature or handling sustaining issues, what languages are used, what is the environment, etc)

I like to open with "I know crunch happens. It's part of our industry. How often would you say crunch happens here and when it does happen, how long does it last?"

At bad companies, they'll justify how crunch is unavoidable but don't worry, their stock is gonna make you Rich(tm). At good companies, they'll crunch a couple times a year, for a week, maybe two. At the best companies, they'll talk about how their Process eliminates crunch time.

I've asked this question ever since I interviewed at a place where the lead dev had a cot in his office.

Here’s a few from me:

• How many separate projects are developers working on at any given time? (Because I want to know if they expect developers to be context switching all the time.)

• Is anyone sitting there with a stop watching checking what time I get into work in the morning? (Because I’m not hourly and don’t expect to be treated as such.)

• Describe the work-life balance.

• Are you agile? Not agile? Scrum teams?

• What might an average day look like for me? Walk me through from when I sign in and log off for the day.

• How do you perform automated testing here? (if they don’t, I’m concerned)

• Do you enforce code formatting?

• How do you deploy your code? (if it’s not a CICD pipeline, I’m concerned)

• How involved in DevOps are developers? (Will o be expected to work on CICD code? Infrastructure as Code?)

• What version control system do you use? (Of the answer is nothing, the interview is over. I will not work there. If it’s something other than Git, I’m not excited about it.)

• Is Docker used here? (Docker makes me very productive, I’m concerned if Docker is a tool I’m not allowed to use.)

• Are there any other programming languages I’ll be using other than <advertised language for the position here>?

• Are SOLID principles common practice here? Or rejected as unnecessary? (I love SOLID and think it’s useful much more than not. If SOLID is frowned upon, I probably won’t be happy there.)

• Can I choose what sort of machine I get to work on? (If I can’t work on MacOS, it could be a deal breaker… I love MacOS for development, sue me! 🤷‍♂️)

I'm not a manager but sometimes get roped into interviewing candidates, I really like when they ask the following because it opens up a discussion about "pace" of the team and organization of the department. It also sets the expectations.

What are your expectations of me after 1 month, 3 months, 6 months, and 12 months of bringing me onboard?

In fact, I like this question so much that I'll answer it at the end of the interview even if not asked, I just feel more awkward doing so inorganically. Sometimes we are back-filling a position and the new hire needs to own features by 6 months. Other times we are hiring to expand, in which case there is more runway. Bottom line is, we can discuss if both parties are comfortable with expectations because we want our candidates to succeed. And I as a candidate want to draw boundaries if I am not comfortable.

• What's the on-call process like?
• How much time off on average do developers actually take?
• What is the testing and QA process?
• How do you measure success of a project?
• When and how do you evaluate employee performance?

I want to make sure my work-life balance isn't going to be awful, and hearing that they have Unlimited Vacation doesn't tell me how much vacation people actually take. I also want to know that the place isn't just doing what a manager thinks "feels right" but actually measures and has standard processes for making decisions.

Another question I usually ask that may be relevant for many of you: what proportion of your developers are women? And: are there any women in tech leadership roles?

Personally, with that one, I'm mostly just looking for a normal response and that it isn't zero. I don't want to be the only woman around.

My secret weapon is "what questions do you think I should have asked?".

Not as a cop out, but something to follow your other questions with. A good interviewer will point you toward some of the company workings you wouldn't have thought to ask about. And if they're evasive it's a red flag you can use to consider their offer.

Something I'd ask the recruiter, long before the interview, would be "do you use safe agile?". The only place I worked at that did safe agile was awful and everything about safe agile was a nightmare.

I would ask about their favourite project for that company. You can gain so much insight from this. Do they look happy when talking about it? Passionate? Overcoming challenges or being defeated? And much more.

Ask about work life balance. I've had an interviewer tell me that they don't work "too many Saturdays" go on to say that they "only worked 4 Saturdays this year" in March. That's like a quarter of the weekends.

Another good one is what they'll do to prevent share dilution if they're bought out. Startups love to give you equity but it is paper money they can burn easily. Always remember salary is the only thing that is guaranteed.

Ask about how they protected staff during Covid. Ask how much vacation people typically take at places offering unlimited PTO.

First thing to figure out is if the new ship is stable:

• How were the customer numbers doing last 6 months? Churn vs new customers? Finance numbers (if possible to share)?
• How do you see the product of the company on the market? Who are the main competitors and how will the product win? Warning flags: not increasing customer base, people interviewing for dev roles have no clue about the product's situation on the market

Next thing is to understand the team's position within the company:

• what were the key deliveries of the team last 3 months, how are they connected to the success of the company
• what is the next top priority for the team Teams that are working on the key elements in the main product of the company are better for promotion for example. Teams that are working on side-projects or internal tooling could be better WLB.

Last, but not least, how does the team work:

• how is on-call? When was the last production incident and how was it handled?
• how does an idea get into development and to the users? Ask as an open ended question and listen carefully: -- is there a backlog and prioritization, or ad-hoc pushing in new tasks -- do they mention having different environments, code review, git or similar? -- do they mention updating tests, test automation or manual QA? How are releases done? -- where do they stop in the description of the process? Do they mention monitoring or logging? Smoke testing or post-launch checks? Is there someone checking if the release was a success for customers (usage/uptake or other key metrics)?
• how often do they release? Lead time for changes?
• how do they handle technical debt?

Great question man. This is a big help to see!

Maybe this is because I'm still relatively junior (2ish years), but my favorite question to ask is, "What are some of the characteristics you're looking for in someone in this role?"

I use it as a vibe check, especially at the end of interviews. If they start reading my resume back to me, or listing the things we've talked about during the interview....well, that's a good sign. If they start describing a bunch of stuff that we didn't talk about, it's a chance to throw a 'Hail Mary' pass and show them how that's me, as well - maybe we didn't talk about something that was important to them, but I have relevant experience or a background.

If they start describing somebody else....well, that's not great.

As a company owner and lead dev of 15 years, I'll be honest. If someone started with some of the barrage of detailed questions I see here I'd start to wonder whether I'd want to hire that person.

Although then again, I don't even ask all that many questions myself. Prefer to get a (technical) conversation going whilst gauging intelligence, speed and flexibility of thought and general character.

Thrn again, we handle all the main (software development) concerns I see here and I tend to be very flexible as long as someone is productive.

What I'm trying to say is, relax? :)

I was wondering if anyone else had any questions they always asked the interviewer in the “we’ll give you five minutes at the end to ask us questions” bit in interviews.

How much time they spent asking you questions? I hope that was 5 minutes too, interview is a 2 way thing, you need to know that you will like them too. If a company told me I have 5 minutes, I would take it that they don't care what I think about them and they're not interested in sharing information about themselves which is a massive red flag.

Check this list https://github.com/viraptor/reverse-interview

Technical things:

• What's the development process like? Scrum, Waterfall, ... No clear process would be a red flag.
• Is there source code versioning? Git and maybe Mercurial are acceptable. Only SVN would be a red flag. (At "No" I would probably leave the interview...)
• Is there a CI Pipeline? Automated testing? Unit tests?

General things:

• What would my first few weeks here look like? Is there a special introduction program?
• Is this a new role, or am I replacing someone? If the latter, why did they leave?

I'd ask why I'm only getting 5 minutes at the end to ask my questions.

Exploring Go High Level:

1. What’s the Enthusiasm About?
   Hello there! Are you familiar with Go High Level? If not, let's break it down. Imagine managing multiple apps for marketing. Sounds busy. That's where Go High Level comes in. It's like that friend who has a solution for everything. Whether you are working on creating an outstanding sales funnel or sending out an email campaign, this platform has your back. The best part? They let you test drive everything with a 14-day free trial. It's like trying out a new car but for your business. And if you ever need assistance, their support team is just a click away. Pretty exciting, huh?

2. So, How Much Does It Cost?
   Alright, let's talk about the financial side. Go High Level offers 3 main plans. The Agency Starter Plan is perfect if you're just starting or have a small business. It's loaded with all the essential tools, and it's quite cost-effective. But if you're looking to scale up, the Agency Unlimited Plan is your best choice. It's like the VIP pass at a concert, giving you access to everything without any limitations. Not sure about committing? Remember that 14-day free trial I mentioned? It's a great way to give it a try without any obligations. Lastly, they offer a Pro plan that includes "SaaS mode," where you can white label the product under your brand. Fantastic!

3. Why Everyone's Raving About It:
   In a world full of sophisticated digital tools, Go High Level is like that all-in-one Swiss Army knife. There's no need to switch between apps because it has everything under one roof. Whether you're a newcomer or an experienced marketer, it's super user-friendly. It's not just about launching impressive campaigns; they ensure you understand their performance with top-notch analytics. There's even a white-label feature for marketing agencies, so you can add your brand and impress your clients.

Here is a link to their 14-day free trial:
https://www.gohighlevel.com/?fp_ref=get-started-now.