I realize this isn't super on topic but I also feel like this is the best place I know of to ask for this advice, so here goes. I need some entry-level, remote-based work. What should I do? Help desk work seems the most promising / practical, but I haven't been able to find anything yet. The remote jobs I see posted are nearly all for higher-end positions.
I live in the poorest region of the United States, but I do the best with what I have. I’ve worked on my family’s farm and done a couple stints at retail beauty supply shops that friends own. I helped open two of those shops. That’s the extent of my non-existent resume. Given a chance to interview, I believe I would do ok. Maybe even exceed expectations for the sort of job I'm looking for.
I need to work remotely for family reasons. I have a special-needs sister and I look after my youngest brother. They are what's most important to me, which is why I don't want to relocate. I have another brother who was helping me, but he accepted a job offer far away. Now I am the only relative near who'll be able to care and look over them. I have time for a full-time job, though, and I need a way to support us.
I do have a job offer that would require me to move by March 13th. The problem is that it is far from my family, and with my brother gone, I would be leaving them on their own. The job is at is an auto body repair shop paying minimum wage. I would be stressed every day worrying about my family back home. What I want is a way to work that lets me stay at home, fulfill my family responsibilities, and make money to keep things afloat.
I am a techie at heart. I’m a Linux/MacOS person, but I easily adapt to other technologies. My first PC was a Compaq Presario that ran Windows 3.1. My father saw the ‘future’ in it, and he hoped I would be part of that future. To use it, you needed to enjoy torture to some extent. Still, it sucked me in. Something about that mysterious DOS prompt promised treasures if only I learned its magic. A few years later, I was dual-booting an ugly Dell machine (Windows 98 SE and Ubuntu). In between that time, my school still had an Apple IIe on which I loved playing Oregon Trail. I bought one a few years back for nostalgic reasons, but I had to leave it behind at my old residence. I miss it a lot. I hope it got a good home.
I am currently working through the freeCodeCamp course and intend to pick up Eloquent JavaScript by Marijn Haverbeke soon. I use VS Code and Spacemacs as my editors. I google like a madman. I have fun playing ukulele and guitar, and I’m teaching my youngest brother about the different parts of a Raspberry Pi. Oh, and I love to read. I am a habitual reader. There’s a lot more, but those are the kind of things that interest me.
I learn quickly, I am flexible, and due to working in customer service (beauty supply shops) I have a calm and understanding demeanor. I am a friendly person and I am always willing to find a solution, even when a solution seems impossible.
I would be grateful for any advice, and I am particularly thankful for dang's / Daniel's time in editing this to be a better Ask HN submission.
I can be contacted at AskHNremote2021@gmail.com and I can provide my GitHub as well, which is mostly documentation editing. I have been told I am a competent writer, if that counts for anything.
Edit: I know that this is an unusual Ask HN post and I am grateful to anyone who takes the time to read through it. I'm curious how others in my situation managed to find remote work. I feel lost in all of this. To say that this has been a stressful time would be an understatement, but I'm turning to HN in the small chance the right person sees this and can give me suitable advice or point me in the right direction. I have always found comfort in this community, so this is where I've turned. Thank you.
Now that that's out of the way: You need to focus. You've described your abilities and that's fine, but you lack focus. Your qualifications are great, but your presentation is all over the place. You need a single one page resume that focuses on one aspect of your knowledge and experience, and lightly mentions the others. Make multiple resumes, each with a focus on one thing. Use the resume that's best for the job. I recently saw somebody who must have had 20 different resumes to match the jobs they were applying for. It worked.
Also, you might consider looking into the Web Hosting business. If your temperament is as you describe, and you like talking on the phone or live chat, most web hosts will overlook any technical gaps. Those can be taught. In fact that can lend to your focus! Focus on the fact that you know things that can't be taught: Customer Service, talking down angry customers, talented writing, friendly and always willing to find a solution under dire circumstances. Those are GOLD. Once those are on the table, the rest is negotiable. I'll email you a link to at least one that is hiring full remote entry level.
Additionally, you need to step up your confidence level. Let an employer know that your family is important to you and that you're dedicated to working hard so that you can support them- and leave it at that. They don't deserve the other details, and they aren't relevant.
I hope this helps.
For most people, different resumes for different roles (web dev, mobile dev, etc.) make sense, but if you have 20 resumes for different roles you're probably applying for jobs that you are highly unqualified for - nobody has expertise in so many areas where they need 20 resumes. 2-3 for most is probably plenty.
The key difference in most resume customizations is how you define yourself to the reader. I use summaries to tell the reader who I WANT them to think you are. If the job is "web developer", I want to tell the reader right away that you are a web developer right in the summary. You've defined yourself as what they are looking for, checked their first (and most important box), and they will now keep reading.
If that summary said "embedded developer", they may stop reading. If there was no summary and your first job title is "data analyst", they may stop reading.
I'd like to second this methodology. It is a very effective approach. I've worked across multiple specialties within technology and I always tailor my CV to the job I am applying for. I highlight the most relevant experience and skills required and remove (or summarize) experience that is not relevant to the position.
Matching your CV to the job can be as simple as updating it to use the same keywords that you see on the job advert. It sounds trivial but many recruiters will filter job applications with a keyword search. If they dont see the exact keywords they are expecting, your CV will be thrown away.
Good luck!
Let's suppose you were a machine learning engineer for 2 years, a web developer for another 2 and a product owner for 3 years.
I presume that some experiences would almost make it seem that you're not dedicated to the role you're applying for if you leave them in. So you have to leave them out.
How do you deal with that?
If you know Linux well enough to configure Wordpress, how about tech support for a hosting company? Try making some short email approaches to old-school hosting companies (I used to run one). They might be flexible enough to take a chance depending on how confident your approach is.
They have lots of customers bashing away at Linux, making mistakes, often without the patience to see their own problems through. Their business problem is that these customers need hand-holding but only pay a fixed, monthly fee. (the hope is eventually they stop asking and keep paying for years).
The combination you can offer those companies could be basic Linux knowledge (no need for advanced cloud stuff) and whatever flexibility you can offer them - especially if they're not in your time zone.
The larger ones might be a tall order, all listing locations by default (Gandi, Leaseweb, GoDaddy, Hetzner etc.), but maybe someone here will have an inside track.
I agree with other posters - never mention difficult circumstances in a job application, particularly a cold application. Just talk about how keen you are to solve their difficult customers' problems, how well you work in a team, and keep the initial approach brief.
Good luck! And please update us if you can.
Once you get that first job, just soak up as much as you can. And keep studying on your offtime. Learning AWS is very valuable.
Note how this path wouldn't be possible if all these hosting companies went out of business thanks to competition from big cloud providers. Then think about what this means for the future we (in IT) create for ourselves and for newly minted IT professionals.
I commonly see people on HN deny that there are any major shifts in overall system complexity happening right now. "Everything always seems complex if it wasn't created when you started in IT". Ok. If the complexity of newer tech stacks is an illusion, why don't you hire the OP to manage your containerized micro-services via Kubernetes? He's starting his career in IT right now, so he should have no preconceptions you allude to.
I just wanted to say to keep your head up, remain persistent, keep learning and stay curious. It can be done and hard work (usually) pays off.
Stay flexible - even if a job doesn’t seem super relevant to your core interests you never know when it’ll come in handy later. For example, my experience in fast food gave me great insights into POS systems (which I ended up building) and my time working at a luxury boutique hotel taught me how to provide excellent customer service even in difficult situations (one time I didn’t call a customer’s room at the request wake up call time and he missed his flight- eek).
Best of luck to you!
Ps- just sent you an email
Instructions on how to bootstrap a software portfolio:
Pick a language (sounds like you chose JS which would be my pick as well), buy a copy of cracking the coding interview, make a leetcode.com account, make a codepen.io account, and get to work.
If you’re smart and dedicated you can teach yourself this stuff and these are the best tools to help you in my opinion.
Spend your time solving problems on leetcode and then utilizing these techniques in codepen portfolio pieces.
In my opinion with serious dedication you can have a junior swe worthy resume and portfolio put together within a year.
[edit] since the question inevitably comes up with JS in my opinion you should not spend any time focusing on front end frameworks. Learn Vanilla JS, HTML and CSS, you will blow your interviewers away if you can solve their problems without a framework and it is overhead you don’t need as a beginner.
In my opinion this is a pretty bad advice and I see a lot of entry level programmers struggling for a long time because of this. A basic algorithms and data struture book (something like Introduction to Algorithms by Cormen, and Data Structures by Mark A Weiss) is a must before jumping into leetcode/cracking the coding interview. One needs to have a foundation before diving straight to interview problems.
If you're applying to somewhere small it's less important to demonstrate you're already a good developer, and more important to demonstrate that you're interested in learning what the company can teach you, you're a decent human being who the company will want to be part of the team, and that you're not going to give up after a few weeks. Tools like leetcode won't teach you those things.
To be honest I don't know how without any prior experience or graduating from a top uni you would get an interview at a FAANG in the first place.
Sure, algorithmic thinking is valuable, but linear programming and complexity theory has no bearing on 99% of all web development jobs that require JavaScript and in this context I think this fetishisation of Informatics Olympiad style puzzles is the wrong advice for someone trying to enter the field. You do not need an in-depth understanding of computer science to get started with programming or survive in the field, especially not in an enterprise environment. I met Java developers who I suspected didn't even know what class is to be honest. But people like this can thrive at big corps.
In the first year of university I had Prolog, EBNF and partial derivatives, theoretical foundations of computing, linear algebra and stochastics but how much of that stuff do you really need when programming a UI? The complexity lies elsewhere, understanding business requirements, talking to people, avoiding technical debt by talking PMs out of weird requirements, structuring your application in a modular fashion, staying up to date with the eco-system etc.
I agree that focusing on HTML, CSS and vanilla Javascript before jumping into React, Vue or whatever is a good idea tho. For frontend development job, the best thing in my view would be a solid understanding of the web fundamentals + experience in one of the big three frameworks. Outside of that, I think there are probably a lot of jobs where being able to just work with Wordpress templates is good enough tbh.
Anyways, when I'm hiring "juniors" or I'm looking for something that tells me the person a) actually likes programming b) has some demonstrated talent (problem solving, compositional thinking, whatever you want to call it) and is able and willing to learn and c) is able to work together with people (which is the biggest problem with self-taught solo-devs, not having worked in teams before) d) is not an asshole
This is how I got my first job in the industry. I built software and websites to solve problems that I personally found useful. Though the solutions were (in retrospect) rather unpolished, they were good enough that a team saw some potential and were generous enough to take a chance on me.
It’s irritating as fck that these FANG companies are so brain dead, that this is all that they can focus on.
Learning JS would be my pick too. In fact, there are coding schools/bootcamps that also make this their #1 pick.
Learn JS, HTML, CSS. Play on codepen, make things. Once you've got that down then you're ready to tackle cracking the coding interview and get that job.
It's hard for us vets too you know. With ever increasing requirements, frameworks, tools to learn. We also practice this make stuff in order to stay relevant. Coding is a life-time of learning (new frameworks, new languages, new ways of doing things) and is very rewarding. Graphic Design is as well in the right brain category of work. Web needs both. Right brained people, left brained people, new coders to grow teams, old coders to mentor and lead those teams.
Either way, either path you choose - Backend or Frontend, there's never been a better time to learn this from online resources in the comfort of your PJs.
- figure out for whom you are a good fit based on your experience - for whom and what are you a good solution?
- create a professional, to the point resume, highlighting your unique value prop for these people, and your experience that they will care about
- write a really good cover letter about it, and say in it "I realize you may not have considered remote, but I think I am a very good fit and would be a benefit to your company, would you consider discussing this possibility"
- go through stack overflow careers making a big list of everyone you'd be a fit for, regardless of whether they think they will hire remote. The whole world is your oyster.
- send out applications TWENTY TIMES A DAY. <--- THIS IS WHAT MATTERS
- follow up: after a few days, after a week, after two weeks, then drop them if you haven't heard.
That's really all there is to it, it's a sales grind. You get up and you do your TWENTY calls every damned day and you will find work.
Some folks might think these are high numbers, but here's the rub: when the answer come in, you want options. There's a sales saying: the best negotiating tool is a fat pipeline. If you get a hundred applications out in a week, and they take a few days to a week to get around to them, the following week you have a bunch to look into. But don't snooze, keep firing out another hundred that week until you close! That way, you get not just a job, but one that is actually good for you. You can do it, it's a sellers market in tech! So grind the numbers. Good luck! :-)
Focus on achieving some initial level of “proof” that you can perform in an entry-level software (or help desk) role. If you can’t ever visit the office, you’re competing against a worldwide set of candidates, but you can still bring something that distinguishes you. That you work in US time zone and make it easy for someone to employ you are surprisingly strong benefits to an employer who has so far only employed US people.
If you want to break into programming, go after that rather than help desk or sanding body panels. If your next best alternative is moving far away, renting a place there, and doing auto body work for minimum wage, you can probably come out after-everything even by staying put and doing a mix of online learning and even terribly paying gigs on fiverr/ upwork/ etc.
Once you get to the point where you have the basics down and are the equivalent of a boot camp grad, you have more options for full-time employment. Even at bootcamp grad level, most companies are losing money on you for a year, so before that point, it’s a really tough sell.
Maybe consider Lambda School as well. They’ve got a repayment program that scales with income, so if you don’t manage to make the turn and break into coding somehow, you’re pretty much off the hook after some time. (Obviously read their terms, don’t rely on my summary.)
I applaud your focus on your family; I’d keep that out of the interview process. If I’m hiring an entry-level remote employee, I don’t want to worry that they’re taking care of a family member most of the time and trying to fit my work into the gaps. If that’s what is happening invisibly behind the scenes, great, but it’s irrelevant or negative to the interview.
“I have strong ties here and am only open to remote work” is all I need to know as an interviewer.
Best of luck; once you hit the “I am at a boot camp grad level or better”, we have remote-only positions available (as do many companies). Provided you’re in a state where we have the ability to hire, I’d be very happy to have you apply.
Best of luck on your journey!
This is really important. Don't think about employers "taking a chance" on you or having their hearts warmed by your story. (I mean, it might actually work when the OP is hitting the top of HN but in general...) They want non-risky choices.
Since a sibling comment already covered the other thing I was going to say, I'm going to focus on this part, as it's 100% correct.
Moving away to take a minimum wage job is most likely a trap. You will not be making enough money to both support yourself and do anything meaningful for your family, and you're going to be physically tired after working 8+ hours a day. It's definitely not a good long term solution, and it seems pretty terrible in the short term, too. Even taking a minimum wage job locally seems like a better solution to me, if at all possible (I did see you mentioned you live in the "poorest region of the United States.")
I think I would start by focusing on what the minimum amount of money you need to make to support your family, then seeing how you can make that much remotely. That can be whatever, because it's just a stepping stone allowing you to move on to finding a remote job that not only lets you take care of your family, but also lets you get ahead.
You've got a hard road ahead of you, OP, but it's one I've been down myself. For the longest time, I never had more than a few hundred bucks to my name. My net worth was deeply negative due to student loans until very recently. Even though I'm in a much better place than that now, it's still been 3 steps forward, 2 steps back for me. At the minimum, you will need a lot of perseverance, a little luck, a dash of chutzpah, and a willingness to keep improving yourself.
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.
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.
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.
Another alternative is to join up as a sales person at an enterprise company. Look for companies that are growing at a rapid clip; they will often hire people whose sole qualification is that they have a body temperature of 98.6 F. Sales includes helping people do POCs and such, which is part of the sales process for complex enterprise products. Once you start there, you can work your way into Software Development if you wish and can find helpful colleagues. The advantage of Sales is that they require a regional presence, and there is a chance your location will work out to your advantage (typically enterprise companies have sales forces organised by vertical and/or region, including regions of the United States).
The last option is to join an enterprise company as a Customer Support person. Once again, you can develop basic skills and become a helpful person by trying your hand at scripting to help perform minor tasks support people do when troubleshooting customer issues. I see plenty of bright Customer Service people move into Software Engineering proper after they have demonstrated intelligence and a willingness to help the customer by going a little above and beyond the immediate problem.
Most of my advice is centered on Enterprise companies because that's where a large workforce comprising people with a variety of technical skills can be found. Consumer web or mobile type companies are a bit too narrow in the types of people they hire, and frankly, the variety of interesting coding and problem solving opportunities at such companies pales in comparison with Enterprise shops.