Hacker News new | ask | show | jobs
by virtuous_signal 1947 days ago
As a self taught graduate in an unrelated major, in a rural area, I was fortunate to get an entry level job and then a fully remote job this past year. If you can do any contract work or part time work in the field to start with, that would help. Welfare helps. Then I would try to make sure not to target FAANG types of jobs or any markets where every job posting gets 300 bootcamp applicants. Some concrete advice below:

I learned javascript + basic web development stuff like everyone else, because that's where the most beginner resources are. But the job offers I actually got were due to my learning Java (with some Java enterprise edition mixed in) and having some book knowledge about it. There are vast swaths of industries that will help you enter the middle class, and then some, by working on their old Java or C# applications. A ton of career advice out there is targeted towards the 1% who are shooting for Silicon Valley. We don't need that.

Also try to get proficient at Leetcode and come off as intelligent. A lot of your competition is computer science majors.

Lastly, and this might involve some conscious or unconscious deception: Make it sound like you intend to move to wherever the job location is, post-COVID. This works better if you are already in that state. Once you land the first job, maybe they'll offer the remote option eventually; otherwise keep applying to a couple jobs per day; this job search will be slightly easier and you will actually have the leverage to ask for a remote option when it comes up.

2 comments

> "Then I would try to make sure not to target FAANG types of jobs or any markets where every job posting gets 300 bootcamp applicants."

The second job I landed in tech was a FAANG. I completely agree that you shouldn't target FAANG type jobs for your first job. Not because of the other applicants. I could care less about the other applicants.

Where I work and do tech interviews (AWS), it's not about the other applicants. We don't look for the best person out of a pool of applicants. There's one question and one question only: Is this person better than half of the people currently doing this job.

If you're better than half of the people currently doing the job, you're hired. If not, you're not. And the issue is that it's really hard to have the breadth of knowledge necessary to meet that bar without previous experience.

I work in premium support for security. To be better than half the people already here you have to know the following really well: Linux or Windows; Networking; DNS; Encryption; SSL/TLS; Network/OS Troubleshooting; Web App Vulnerabilities; DDoS attacks and mitigation; and more. It'd be very hard for anyone who hasn't done this professionally to be exposed to enough tech to have that sort of depth.

I interviewed people for Amazon as well before moving to another FAANG. All I would amplify here is that entry level is entry level, especially in software. None of the college hires have professional experience (maybe internships, but they had to start from nothing to get those anyway). So what you are trying to do is

1) not be an asshole; look at their leadership principles and figure out how you resonate with them; answer honestly if you never did that

2) beat the technical questions. they are a proxy for skills and experiences

I used and recommend Leetcode for #2... for entry level I don't think you should need the paid tier.

If there were a Leetcode for not being an asshole, I would recommend the paid tier.

> " I interviewed people for Amazon as well before moving to another FAANG. All I would amplify here is that entry level is entry level, especially in software. None of the college hires have professional experience (maybe internships, but they had to start from nothing to get those anyway)."

100% agree with everything you said, although depending on the Org 'entry level' can mean 'just graduated from college'. In Premium Support, at least, they're always tinkering with their recruiting models.

I was hired as entry level with 1 year experience at a startup. These days, that entry level job is reserved for recent college graduates or people getting out of the military. They wouldn't slot me as entry level today for recruiting/interviewing purposes.

Not sure how AWS handles entry level software engineering positions.

What were the things that surprised you the most coming from outside IT ? what were the hard part ?