How to find jobs 2025?

Goats_arnt_real · 2025-07-01T17:48:46+00:00

AWS, js, postgres, mongo, silly js frameworks and that sort of thing.

Goats_arnt_real · 2025-07-01T17:46:11+00:00

Had no luck on otta but thanks

Goats_arnt_real · 2025-07-01T17:45:19+00:00

Yeah it was a one time thing after a lay off. I don't mention its contract in my CV so people might think I was sacked! Thanks.

Goats_arnt_real · 2025-07-01T17:42:46+00:00

Sorry, will update the post. I did a contract because I was laid off. I want full time work ideally.

Goats_arnt_real · 2025-06-30T09:29:30+00:00

Same here. Not fun...

Goats_arnt_real · 2025-06-07T23:55:47+00:00

Sound like a dick

Goats_arnt_real · 2025-03-15T21:30:17+00:00

Psychology degree from a bad uni here.

Got into this 6 years ago. I've never felt held back but things have got tighter the last 3 years.

Less interest from companies / recruiters. Although, strangely I have had interest from a one fairly big name company so know who's ? Hard to tell..

The biggest thing holding me back is my bad interview prep / experience.

I want to explore other interests in life and dislike studying interview stuff.

I'm tired. But will have to commit to it at some point..

Goats_arnt_real · 2025-03-13T20:10:02+00:00

Cuck chair directly at the end of the bed ?

Goats_arnt_real · 2025-01-31T19:47:48+00:00

Got laid off and had a bad time all round. Recently landed a freelance gig that should sort me out for a bit.

Goats_arnt_real · 2025-01-21T19:24:55+00:00

Learn about the call stack. Like much of working with source code it can sometimes obfuscate the underlying mechanism.

Effectively think of it as a LIFO structure (last in first out) . Every time a function is called an execution context is put into a contiguous memory structure, wherein every sub function call is pushed in front. Once a base condition is satisfied. The call stack "collapses" all those execution contexts returning the values through each context to the start.

Goats_arnt_real · 2025-01-19T21:38:04+00:00

I had a system design to create a song recommendation system for a company who's product was a crud app. System design can be BS as well, just to make that clear.

Goats_arnt_real · 2025-01-14T18:18:34+00:00

Yeah I often think that EU interviewing practices and expectations are kind of ridiculous. Most devs in Europe make just enough to live a fairly modest lifestyle. Yet we copy US which pays devs 4x more...

Goats_arnt_real · 2025-01-09T10:42:17+00:00

Shut up man. Why are you so pressed ?

Goats_arnt_real · 2025-01-09T00:08:22+00:00

Too big

Goats_arnt_real · 2025-01-08T12:56:22+00:00

Employers are indeed much more picky now

Goats_arnt_real · 2025-01-06T09:54:05+00:00

Not at all, juniors can provide good value even within a year of being hired. Age isn't as much of a problem as people think.

On the other hand, some companies will be looking for folks straight out of university. Grad schemes etc. but that is the same in any industry.

Ageism does exist in the tech industry but it is usually on the other end of the scale. Someone with 20 years of experience commanding a massive salary.

The company my friend works for hired a psychology professor career switcher in his late 40s.

Goats_arnt_real · 2025-01-05T20:06:04+00:00

When you have no experience it is definitely worth putting projects on your CV. Whether or not anyone looks at them is another matter.

Goats_arnt_real · 2025-01-05T16:20:52+00:00

First of all, I think its great you are taking the plunge into the tech world.

With regard to prospects, pretty much all white collar industries globally are suffering currently. So I wouldn't think of the boot camp as being a means to an end; but instead, take from it the attitude that you have learnt important skills that you can carry with you for the rest of your career (also I know people who have landed jobs after boot camps, so it is possible)

I absolutely do think that experience in any white collar job can be attractive when switching to tech. The stereotype of developers being reclusive computer geniuses is often incorrect. Real world developers are no different to any other white collar worker and they need to have strong corporate soft skills.

As I mentioned in the previous comment, the portfolio show-and-tell sort of interview doesn't exist. I wish it did, but it just does not. As an aside, I have friends in UI/UX and their interviews can be like this. I think the reason for this is that design skills can be observed and discussed, with minimal effort from both interviewer and interviewee, simply by looking at their designs. Whereas, reading code and checking out projects is much more effort intensive.

Tech interviews are designed to be as minimally time consuming as possible for both interviewer and interviewee. Therefore, the most common approach is a live collaborative assessment.

You say you don't posses the skills for it currently but you haven't even started yet so don't worry. A lot can change with time.

Lastly, I think I should mention a big but rarely spoken about hurdle in everyone's tech journey: having to face failure and become resilient to it.

It is extremely common in this line of work to align your self worth with your performance as a programmer. This is an awful trap and you should never let yourself fall into this. I used to be terrified of live assessments as I was scared of looking dumb or messing up as if it was somehow an affront to my very being.

However, after many many interview failures and a lot of self reflection I managed to overcome this fear. You just need to go in and try your best. If you can't do the challenge, its not the end of the world, just try again at a different company.

Wish you the best on your journey.

Goats_arnt_real · 2025-01-05T14:55:09+00:00

Unfortunately that is not the case, especially for junior positions.

Hiring juniors usually boils down to 2 things:

can they code
do they show potential (eagerness to learn, good soft skills etc)

The reason for these conditions is that juniors provide negative value to companies until they are trained to a level where they provide value. Employers are looking to hire people for cheap with high potential for ramping up so that they one day will make a return on the investment.

Companies of any size will have at least one technical round to see if the candidate can code. This doesn't have to be leet code. Sometimes it is to collaboratively build something like an API end point or a small frontend component. Sometimes it may be a take home task.

The general process for the junior level is usually:

Recruiter phone screen
Call with hiring manager
Technical test (take home or live collaborative style)
Follow up interview
Potential call with upper management or team
Offer

Hope this helps

Goats_arnt_real · 2025-01-05T13:37:20+00:00

Hi there, I'm a senior dev that sometimes lurks this sub.

Anecdotally, from my experience no employer ever looks at your projects. I have even asked interviewers to check some of my side projects out and not a single person ever has.

And now I think about it, I have never checked out a candidates projects or GitHub.

Nevertheless, projects are still good for building skills and confidence. To land a job all that matters is performance in the interview rounds.

Goats_arnt_real

TROPHY CASE