An interview is an opportunity for both of you to decide if it’s a good fit. Unfortunately the seeker is usually happy to accept anything. Lying is counter productive. They only want to hear any reason that you picked their workplace. Consider it structured small talk and focus on your energy.

I generally say: "let’s be realistic, I’m not passionate about what your company does. I am here to trade my time for wages and I have heard good ones about [company name].

Elaborate by mentioning something from their website to appear engaged and interested. Say you were a perfect fit because you meet all the requirements, talk about a friend who works there, mention using their products or services, or just mention that it’s close to your house and will be a short commute. Ultimately this is a soft question that is just to get a quick idea of each person applying.

Unfortunately most of the nuerodivergent kids have to go to special places that can handle their tantrums. After an incident, great clips will recommend you to the local location.

I offered 3 potential solutions that work across ever model (unlisted) and you guys are downvoting?

• USB - apple 30 pin: note that the pin number might change depending on release year. Someone smarter than me will mention why firmware might not work out.
• USB to aux: this will give you a headphone jack and is the most reliable
• FM transmitter: if you lack a headphone jack you can also get an FM transmitter. It makes your device a mini radio station. These are pretty unreliable or staticy, but sometimes you need an option. I would recommend a new player first.

https://elevenlabs.io/ You’ll need to pay for premium to train a model with your own audio. They may have a trained version already

I personally don’t like the idea of migrating off Jenkins, we blew our yearly budget testing our build platform in git. But it’s all just platformed ci/CD, which is why I’m recommending the other path. Platform teams lost the goal recently.

US Sr SRE (devops) checking in: I would personally recommend the networking path. Caveat: A good engineer will know the background of both (curl, telnet, Iam, security groups, cidrs, domains)

Devops was mostly automating the stuff in between the other teams; and most of that is working out of the box these days. Most repos already have their Jenkins and docker files. How much admin are you expecting on serverless? Most people are pivoting to app support (ticket queues) or supporting managed services (on call).

As far as my day to day:

• Troubleshooting incidents and walk ups
• Answering pages (read restarting things)
• Groovy Jenkins build pipelines
• Cdk applications
• Ruby configuration management
• Parameter/secret management
• Reading error messages for devs
• Yaml/xml linting
• Assisting in load testing
• Changing settings to make the application more stable. Ex: db connections, memory
• Cloud UI/clis

Pros: I do a lot of different things, we get downtime because we need to respond to things immediately, I don’t have normal project/sprint planning. I have the keys to the kingdom. Higher pay than most other devs. I hack things together, I don’t need to design workflows.

Cons: I am on call, I am the silliest clown (I get hardest problems), I need to understand a lot of moving pieces, sometimes when things break, there is a lot of pressure on you to find something hard. I regular have to Google “bash variable syntax” because I’m coding in 15 languages. Interviewing for jobs is impossible because no 2 positions are the same

My list for zoom party games:

• Jackbox on steam. You host and users join a lobby to play via browser.
• https://www.drawio.com/ pictionary
• https://garticphone.com/ group telephone game pictionary
• https://oneword.games/room/imported-island coop word game
• https://codenames.game/ group caragories