Tech Industry job layoffs looking scary

[DJSmooth]

Not the way it works.

You should know how, what, why it was created, what problem it was created to solve, what the downsides and drawbacks are, and so on.

Shows you have domain knowledge, implementation and troubleshooting experience. Shows you've pushed the limits or at least thought about the limits of what something was designed to do.

Dude asks about a protocol. Tell him the history of it, what problem it solves, alternatives, where it gets sticky. How it works in depth, how it works in Linux vs. Windows, who created it, and so on.

You ask me about TCP, you'll get 10 minutes on the history, going all the way back to Vint Cerf (who used to be a co-worker).

You make them stop you from talking. You should be answering five questions to the one they ask.

Depends.

If it's something out of your domain niche that you don't work with frequently then not knowing isn't a big deal. It's so much to learn in tech. I rather someone tell me what they don't know then try to lie and it sounds bad.

Sometimes an interviewer will keep asking you questions until you can't answer something to see what you don't know.

If the interviewer was biased and didn't want to hire you in the first place then they will use that against you as an excuse.

 

[Apollo Creed]

I started in 2007 during the Great Recession and it wasn't this bad. Tech workers all need to develop an exit strategy. Too much outsourcing of jobs being blamed on AI as cover.

Yeah Post 50 if you are still doing this shyt is cause you love it and/or it is like bonus money and benefits but you don't "need" to do it.

 

[DJSmooth]

If you interviewing for a data science position where you use python everyday, ok of course you should know the ends and out of python.

but if then they start asking you about some obscure math library written in C. Then start asking you C pointer questions and use that as an excuse to not hire you. They didn't want to hire you in the first place or looking for some unicorn that doesn't exist. If I was that smart why would I be trying to work here instead of doing my own thing?

 

[IIVI]

CS is becoming like hard science fields like physics, material science, or chemistry where you will need to intern for several years after college before landing a job.

And i suspect they will try to weed out candidates by raising the bar to a masters, despite self taught(ers) being able to do the exact same job 2 years ago.

This is how I think it may honestly play out.

Physics is a more difficult field so that kind of filters already.

That said people want to make money and they’ll throw a bunch of people together to build some product. However with A.I they probably think they can hire less but better: I can definitely see the standards being raised, in some ways they already are as some companies only want a B.S from Caltech, M.I.T, etc. Which is absolutely ridiculous because if your product is a CRUD app you don’t need some Princeton grad to ask ChatGPT how to build something.

I said it before in that Air Traffic Controller thread: you’re wasting the potential of our smartest minds and engineers by putting them in something like everyday air traffic control rather than them building a new system. In the same way, 90% of these web jobs are basic CRUD. Putting Albert Einstein to do that work is overkill and wasting talent.

 

[Rick Fox at UNC]

Depends.

If it's something out of your domain niche that you don't work with frequently then not knowing isn't a big deal. It's so much to learn in tech. I rather someone tell me what they don't know then try to lie and it sounds bad.

Sometimes an interviewer will keep asking you questions until you can't answer something to see what you don't know.

If the interviewer was biased and didn't want to hire you in the first place then they will use that against you as an excuse.

We are saying the same thing. It's not about knowing everything, it is about knowing the ins and outs of how systems and protocols work.

The reason you go in depth is so that when you reach your limits, you have enough context and understanding to move forward.

A good interviewer hiring for a top company can see this.

 

[Rick Fox at UNC]

If you interviewing for a data science position where you use python everyday, ok of course you should know the ends and out of python.

but if then they start asking you about some obscure math library written in C. Then start asking you C pointer questions and use that as an excuse to not hire you. They didn't want to hire you in the first place or looking for some unicorn that doesn't exist. If I was that smart why would I be trying to work here instead of doing my own thing?

Even here. So, I may not know every obscure math library written in C...but.

This is just me winging it in 10 seconds.

I know the reason code is generally written in C over Python. I imagine there is some need for speed or low-latency code. I might discuss low latency platforms and where/how they are used. I might discuss the players in the space. I would discuss that and ask questions.

I would ask what the library itself is used for then discuss alternative libraries in python and how I've worked with those. Maybe I've written a similar library myself. Discuss.

If asked about pointers, I can go in depth on pointers as they are a foundational aspect of modern programming.

So even then, not knowing the actual library was an entry point to showing domain expertise and deductive reasoning. I understand the way broadly, they know I can go specific.

 

[Rick Fox at UNC]

You ask me about C code in data science and the conversation will get to ASIC programming, low-latency networking infrastructure, chipsets from the likes of Broadcom and Arista. And so on.

You should know the world your in like a top lawyer or wall street analyst. Like knowing this shyt inside and out is the difference between netting a mil and getting your lunch ate.

 

[DJSmooth]

Even here. So, I may not know every obscure math library written in C...but.

This is just me winging it in 10 seconds.

I know the reason code is generally written in C over Python. I imagine there is some need for speed or low-latency code. I might discuss low latency platforms and where/how they are used. I might discuss the players in the space. I would discuss that and ask questions.

I would ask what the library itself is used for then discuss alternative libraries in python and how I've worked with those. Maybe I've written a similar library myself. Discuss.

If asked about pointers, I can go in depth on pointers as they are a foundational aspect of modern programming.

So even then, not knowing the actual library was an entry point to showing domain expertise and deductive reasoning. I understand the way broadly, they know I can go specific.

Nah. Maybe for this hyptohical python position you should know the diffrence between a copy and a refecence when talking about programming. Anything more deeper than that is an example of the interviewer fukking with you to try to make themselves seem smarter than they are.

Some days I wish you could interview the interviewer back. It be a one way street.

I remember I had an interviewer keep asking me about using Reflection. I eventually got fed up and asked them an example of where they use Reflection at work both of them goofys started fumbling over their words and started stuttering.

 

[Rick Fox at UNC]

Last quick note:

I remember David Boies talking to Charlie Rose about preparing for the Microsoft anti-trust case and he said something really great. Work watching the whole thing, but if you read and follow the bolded and spend the next three months following his advice. You can get on at any FAANG.


David Boies: "The first thing you do is you just read everything you can get your hands on that relates to it. And you talk to people. And you try to learn so that you know -- maybe not more than, but as much as you can -- about the industry that you're going to be dealing with. So that you can question people who have lived with it their entire life and there are at least some things that you know better than they do. So, I started with the past record. There had been a lot depositions that have been taken of Microsoft in other proceedings. I went back, and I read those. And I went back and read them in the raw, so to speak, not summaries, not digests, but to get a sense of the people. And then read the documents. And that was, of course, a continuing process 'cause we had document production going on. But you read as much as you can, you learn as much as you can. Then you start to try to put it together. You try--

Charlie Rose: You're in the discovery-for-your-own-self phase?

David Boies: You're really in the discovery phase. I mean, it is not unlike what a journalist does. You see something that's interesting. You start to investigate it. You start really with an objective point of view. You develop some hypotheses, and then you test those hypotheses. And that's very much what we're doing.

 

[Blessings]

People don't get it. Think it's because dude was asian.

Not going to make it. I wouldn't want someone who thinks like that on my team.

Dude didn't know the answers. Get better.

Whenever we interview in my current and past roles. Answering without explanation of the “how” is damn near invalid…we don’t give a fukk if the interviewer got the answer right or not without explaining how they derived said answer.

All depending on the question....

In this current job market, it's too competitive to leave it up to the interviewer to not follow up on their question without explaining the "how" and/or "how it aligns with your experience. If you're not doing it, assume your competition interviewing for the same role is doing that.

If you're not doing it, it's totally okay not to want the job "bad enough"...so it is what it is

 

[threattonature]

Nah. Maybe for this hyptohical python position you should know the diffrence between a copy and a refecence when talking about programming. Anything more deeper than that is an example of the interviewer fukking with you to try to make themselves seem smarter than they are.

Some days I wish you could interview the interviewer back. It be a one way street.

I remember I had an interviewer keep asking me about using Reflection. I eventually got fed up and asked them an example of where they use Reflection at work both of them goofys started fumbling over their words and started stuttering.

I usually do just that. I try to turn every interview into a back and forth conversation. I'll ask questions about the day to day at their company, questions about procedures and methodologies they use. Of course it's a little different since I'm just a product manager compared to a developer but not reason you shouldn't be doing that too. Plus it's an easy way to slip in your own knowledge in the midst of the convo.

 

[Rick Fox at UNC]

Whenever we interview in my current and past roles. Answering without explanation of the “how” is damn near invalid…we don’t give a fukk if the interviewer got the answer right or not without explaining how they derived said answer.

All depending on the question....

In this current job market, it's too competitive to leave it up to the interviewer to not follow up on their question without explaining the "how" and/or "how it aligns with your experience. If you're not doing it, assume your competition interviewing for the same role is doing that.

If you're not doing it, it's totally okay not to want the job "bad enough"...so it is what it is

Exactly. I'm looking for a person who is answering the next 5 questions before I ask.

When I'm getting on...nothing is better than.

"Oh, wow. Well you just answered the next few questions I was going to ask. Lets pivot to x now."

 

[Rick Fox at UNC]

Nah. Maybe for this hyptohical python position you should know the diffrence between a copy and a refecence when talking about programming. Anything more deeper than that is an example of the interviewer fukking with you to try to make themselves seem smarter than they are.

Some days I wish you could interview the interviewer back. It be a one way street.

I remember I had an interviewer keep asking me about using Reflection. I eventually got fed up and asked them an example of where they use Reflection at work both of them goofys started fumbling over their words and started stuttering.

I don't mind the interviewer doing whatever. Ok. Now we're having a conversation and I get to flip it on him or her (men tend to act like that more than women though).

That's kind of the thing. After awhile I'm not proving myself, I'm already proven. Interview or not I'm having a conversation with a colleague.

This ain't amateur hour. We talk and solve problems together. Otherwise I'll find a different team or company.

 

[JT-Money]

IT pros are caught between an AI rock and an economic hard place​

April jobs data discouraging for IT, tech professionals

: Tech gigs slide, or so this analysis of US jobs data claims

www.theregister.com

 

[Tetris v2.0]

I don't have much to add here except that the org I work for (smaller SaaS-based tech company that was recently acquired by private equity) is AI obsessed and in the midst of a hiring freeze

Every department has been asked to make an aggressive business case to the founders for how they can leverage AI and tie it back to revenue goals and deliverables. Not looking good lol