Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "#wk61"
-
Maintain your LinkedIn, write little articles about implementations on a tech blog, check issues on popular github projects and make PRs, create a portfolio website. Register as a company and do some freelance work, even if it's just a cheap website for your grandma's knitting club.
Do the tour/tutorial of every popular language/framework. Learn the basics of react/vue as a backend dev, learn some sql as a frontend dev. Set up a vps server at DO or AWS, host a few small services. Fullstack is bullshit, but communication is key in development, which means you need to know about the whole playing field.
Recruiters can be useful, but knowing developers in your area is even more valuable. So especially if you're unemployed, go to hackathons, conferences and meetups.4 -
- It's a game, play it
- Come prepared
- It's better to say "not sure" or "don't know" than bullshit
- Don't write in the CV (or mention during the interview) things you don't want to be asked about
- Sound eager and enthusiastic about your profession because no one likes a downer
- the interview is a sales meeting, you are the goods, be sure to be a good salesman10 -
Side projects what got me job three times. Move your lazy ass and work on your projects AND actually finish at least one 😒15
-
Do side projects, even if they're small. If you already have completed side projects, show them off. Employers love to see your efforts and eat that up.10
-
⚪Present yourself properly
⚪Have a basic idea about the company and the role you're applying for
⚪Be respectful and pleasant to everyone when you go to an interview
⚪Day before the interview, go over the interview in your head and prepare as much as you can ( this way you'll be more comfortable in the actual interview )
⚪Figure out and prepare your "Strength and weakness" answers
⚪Don't lie on your resume or in the interviews, if you don't know something, simply say "I'm sorry i don't have experience with that”
⚪Being nervous is ok, but try to relax and answer the questions correctly and clearly
⚪Don't give up and join something that's not worth investing your time5 -
Life is about spamming. Want to get into a relationship? Spam every girl you see and like in the streets and ask nicely.
Want more clients? Spam.
Want a job?
Tell everyone you know, that you search for a job.
Send a resume to every company you desire. Spam.8 -
Always deliver the goods.
Even if who you work for are idiots, and the product is useless. You never know who will see what you've done.
- I did a six-month underpaid project for ShittyCompany.
- Strived to write it nice and clean with unit tests and good(barely) documentation.
- Got a call up a year later from a consultancy company who integrated with the application I wrote. Now I work for them, and it's as close to my dream job as I could hope for.1 -
Don't apply for a job that you don't like. You're gonna hate your life.
Don't ask for a salary you know you're not worth.
Work in a tech company as much as possible. If you don't, you're gonna be treated as a powerpoint presentation expert, office installation expert, video editor/movie maker expert, IT support guy, loose plug/broken headset repairman, facebook hacker, and a dark magician all at once. Most (not all) tech companies know who you are better. They understand your needs better.7 -
For any job, you can include in your resume, without a hint of lying, that you are Time magazine person of the year 2006. Seriously.1
-
When a company comes at you with a skills test or a stupid whiteboard interview, while completely disregarding your portfolio/GitHub/other proofs of competence, run far away.11
-
Always remeber:
The interview goes both ways. Ask the interviewer how he likes to solve problems, and how he works with ppl. This will give you the information to decide if you want to work with him or the company.
This is especially effective on HR: ask about thier corporate culture and how they deal with promotions/good people and how they deal with bad people.
And make sure you visit glassdoor.com before the interviews begin. -
Best advice for dev job hunting is work on your soft skills. Don't be a fucking hero, prove your teamwork ability.
Remember all the rules of all religions and social communities can be summed up in one line: "Don't be a dick!"1 -
I just wanted to say that wk61 came just at the right point in time ^^
My school threw me out a couple of days ago and now I have nothing, so I'm thankful for all of you who're giving advice for job hunting
You guys are awesome! :)5 -
Don't be afraid to approach companies that aren't actively hiring. No-one will look negatively at a positive attitude3
-
The things on your cv are suppose to be known by you, not by your colleague from the previous job.
I had a guy on interview, who talked about his colleague's work... wtf.4 -
I got my job because I've been myself. As soon as I laughed with the interviewers I knew I got it.
They choose you for a interview out of all the other CVs because they hope you know your stuff. Proof it! And most important - show your character. Don't be a blank paper! Make fun with them. Or at least leave some kind of positiv impression.
The funny part:
I applied for jobs in Austria while doing my Bachelor degree in the UK. Over Skype they had no idea I was wearing sweatpants.1 -
Don't lie in your resume or in the interview.
People know you're not an expert at everything, nobody expects that from anybody (and you should really avoid working for anybody who does)2 -
"Pasting code from the Internet into production code is like chewing gum found in the street." - unknown3
-
Be extremely active on GitHub! It’s a nice way to backup your code, as well as show off your skills to potential employers.2
-
[ ] be humble, but not unconfident.
[ ] Step out of your comfort zone. Don't apply to a job that is exactly like your last one.
[ ] A good team is the most important thing for a developer. Intelligent, and nice people to work with and to learn from is more important than the salary difference between jobs.
Try to 'feel' for a good team. Ask to be introduced or to look around when you finish the interview.2 -
Everyone says "don't lie, don't bluff", but all those years ago I put my foot in the door and got my first ever dev job by pretending I knew what JavaScript was. It all worked out in the end.2
-
Don't be me. Don't miss an interview because you don't know how timezones work and at least take a look at their website if you're applying for a web dev job.4
-
“Good comments explain why, not what,” says Andy Marks. “Do more of the former and none of the latter. A well named method or variable will beat a well-written comment every day.”2
-
Happened to me - an experienced dev with most of the experience on the web.
I apply to this company that I had no idea what they do (big mistake on my part). I ace the technical interview, and they follow up with a request for a presentation on a topic, to see how well I can prove a point or understand a technology. So I do that. Everybody is listening carefully. Most people at the office didn't know the basics of what I was talking about, but there was a guy who knew more and asked the tough questions, but I didn't let down.
So we talk again, and again, and all is going well, we're out for a coffee, talk about the future of my career and the company, in a more casual setting. Got to know the CTO, etc. Everything was going stellar.
I was waiting for the offer, but instead I got a generic "We can't continue with your application" together with a notification that I was being blocked by the contact person.
Weirdest interview ever. And this thing really put me down and struck at my self-esteem. I mean was it really hard to mention whether you didn't like my expectations, or my skills, or my "fit for the team"? Or at least not block me like that, it's not like I'm gonna stalk you or anything. I still get birthday notifications on Skype from people I've interviewed with before, and I haven't written them since because they have other stuff to take care about, as do I.
Anyway. I got up and started again. New company. High expectations. High salary expectations. Rejection. Fuck.
Ok, start again. 2 companies this time. Both at the same time. Both make me an offer. Have to turn one down. Harder than I had imagined. The choice that I made literally changed my life for the better. I'm glad I didn't end up at any of the other 2 companies that rejected me.
Even experienced people get bad bitter rejections. Don't have high expectations, and that will help you keep your emotions in check, and fight on.2 -
Go to interviews. You always learn stuff in any interview. Either be a technology or design pattern or any freaking thing they use there.
Basically 2 things can happen:
you get the job or ... you don't,
either way you will still leave with some extra knowledge.
Also don't be afraid to tell how much money you want to earn. Getting a job ans feeling pissed about the salary is a horrible feeling.1 -
This was a comment I made on another ranter's post.
* Tailor your resume (and cover letter if needed) according to the job. No generic resume.
* Research about the company and make sure you have the same interests as the company. Clearly let them know why they should hire you. One question you can expect is: Why should we hire you?
* Show them that you're passionate about the job.
* Be curious. Ask questions. That's how they'll know you're interested.
* Be open to opportunities. Let's say you're applying for Full Stack developer role. Be open to take up Front End or Back End developer role. You don't have to accept everything but at least roles tangent to your job (provided they match your interest).
* Be flexible but focused.
* You don't have to know every listed requirement but make sure to know the majority.
* Don't lie. "Fake it till you make it" doesn't work with dev roles.
* Be confident in telling them "you don't know" if you don't know. Also make sure to tell you're willing to learn that.4 -
Never put a thing on your CV that you don't actually know. I've seen many people put a lot of languages that they don't really know, just to impress the interviewer and get rejected.
Also, be confident..... even when you are bluffing.4 -
Find out the company hiring and apply directly to the company. Don't go through a 3rd party agency if you can avoid it. It gives the company a massive saving and a great incentive to hire you.1
-
The best way to get an interview call is through referrals.
Recruiters are lazy. They don't want to sift through resumes coming from sites like LinkedIn. Referrals are usually better quality.
I'm not saying this. My recruiter friend is.2 -
Be proactive and improve your own projects. Publish them on GitHub, and make sure your LinkedIn profile is set up. You'll be contacted soon by companies for sure!3
-
I don't have anything to say about getting a dev job in some company. But I can give some tips on attracting clients for your freelance work.
* Have a few projects of your own hosted on Github to show off your quality code.
* Contribute to others' open source projects if possible.
* Get yourself a nice website and showcase all your work.
* Ask your current clients to write testimonials on your work and post it in your website.
* Be nice to your clients. Chances are they'll refer you to their friends and family.
That's pretty much all I've done and I get more freelance dev requests than I could take. -
Don't be specific on any programming languages, focus more on OOP approach, and say you know about OOD/A rather than, you know Java, C# and this and that.1
-
Be yourself, don't make yourself look better (or worse!) than you actually are. Also, I never made a side project in my life and I landed every job I applied for. Don't pretend to be someone you're not.
-
Go to meetups and talk to people. Give presentations at meetups if you can. Get involved in community projects. Love coding. Use your downtime to study new stuff.
When talking to potential employers be positive and enthusiastic about your technology.
EDIT: Oh, a few more. Don't seem desperate for a job. Without saying anything, potential employers should feel like you have other offers and they're being evaluated by you. Ask questions about their company if you get an interview.
Try to give off an air of being in control and having a number of choices in your carreer (even if you're living off ramen every day).
The pressure should be on companies to hurry up and snap you up before another company does.
Be honest but a little spin won't hurt. -
"The web. Using a mouse, mices, using mice. Clicking, double clicking. The computer screen, of course. The keyboard. The... bit that goes on the floor down there."3
-
Ask yourself: 'What do I really care about?'
Then find a company that makes a positive difference regarding those things.1 -
In getting a remote job, go to a lot of online job boards. Filter their feed for remote work or work from anywhere. Get the RSS feed (if they don't have it, make one yourself), and add them to your RSS reader, like Feedly.
Do the following daily:
Go through the feed, study the job post ad, apply for the job as per their instructions. Archive those you don't have an interest in and those that you have applied. Repeat.
This also applies for hunting freelance contacts too.3 -
Smell the lies and too much process. Learn how to smell it and stay the same. It's the best also look over political correctness8
-
Maintain an up to date resume and work portfolio. Contribute to open source projects. Network with other professionals. Pursue professional development.
-
In your earlier years. Try to work in a startup. Don't go for corporate life yet. You will learn hell of a lot in a small startup.
And also if you are doing job hunting just spam the recruiters and top officials of the company in LinkedIn until you get an interview setup. Because fuck it you need a job !4 -
You will get far more rejections than acceptance. A lot of the time it has more to do with the interviewer and not the candidate (assuming the candidate is a genuine hard worker). The job search process is similar in this regard to finding a mate or compiling your code.
Keep moving forward! -
Know your shit and don't give a fuck.
Sometimes interviewers are just idiots or monkeys.
I dunno, I've had a few interviews where it just doesn't click. While I'm sitting there, I say to myself: this is nothing like what you said on your job description.. and I've seen all your "technical questions" on Google -
A bit late for wk61 but here goes:
Does anyone have any advice for an older dev (just turned 50) during job hunting?
One of the devs on my current project was let go some years a go, and hasn't found a new job yet.
He keeps applying to positions, but keeps getting rejected and being told "we went with another candidate".
Choosing the young buck who will leave in a year over a older dev who still can contribute for ten years seems like the most common descicion.
I hired him on the current project I'm doing for a client, which is on iOS, and I've thought him swift and the general process of development on ios. And he's taking to it really well :)
I hope this will better his chances, but the current client won't have the resources to hire someone full time now.6 -
Be good at speaking! I've landed 3 dev jobs, without any formal education, merely because I'm good at talking. Bigly good!3
-
As someone who often interviews devs, I can say you should be honest about your abilities. Just because you tweaked someone's Python code doesn't mean you are a Python expert. Stick to the facts on your resume/cv. Also, have a good code portfolio. That shows the interviewer much more than a degree does.4
-
I don't have a job so uhhhh I would suggested don't go dressed like a slob look nice like not to nice but like worthy like a button up shirt blue jeans and combed hair and shoes nice looking one burshed/combed3
-
"Vitamin B" as we say in Germany.
Would be something like "Vitamin R" in english, it's all about relationships to the right people.3 -
This one is from experience:
>always update your CV,
>don't lose hope,
>learn what you stumbled against and
>most importantly- "ABH (Always Be Hunting)" -
Focus on your strengths and not your weaknesses. Oh and wear one of those Polo Pullovers, that way you'll say "Hire me, because I'm that cool kinda sexy but douchey as fuck developer you guys need in your life". That should get the job done or job gotten.
-
Work hard. Seriously. If its your first job, prepare yourself for 1 year in front. Learn programming, repeat, repeat more, fail, gain expertise. Surprise them with everything you do, blow the others out of the water with your knowledge.
-
Network (people not infrastructure)
My first programming job was because of someone I knew in college worked there. Strangely he also got me my fourth programming job.
My fifth job was a recruiter. First time that ever worked. But it does work.
The biggest thing to remember that in an interview you are selling yourself. So you need to understand a little of sales and marketing. -
Suppossing that you're a very capable professional my advice is to NOT UNDERESTIMATE YOU. There are a lot of crappy programmers that feels like an expert because they did a hello world.
-
Searching for a job is a terrible, soul-crushing experience. Take advantage of local meetups and tech-job-seekers groups to help keep your morale up.
During the interview: if you don't know something, that's ok. Don't get rattled by it. Some questions are designed to see how you think, not to see what you know. -
Don't automatically count yourself out of positions because you haven't done them before, you can learn and grow.
I'm in the best job that I've ever had, but didn't meet all the criteria the vacancy had as "requirements". I had some experience in some of the areas that they were looking for, none in others, but they thought I was the right person for the job. I'll always be grateful for that.
At the same time, you need to be realistic, if you've never even heard of half the things on a job vacancy then it's probably not for you. -
Make good connections with the engineers in the company. Persuade them to refer you for the job, if you're lucky you get to skip the interview.
-
Murder the other applicants.
If you can't just do that, hit up your friends and colleagues for connections into companies. That's the easiest way to get a job, I find. -
Be confident, if they are too fool to not hire you after the interview, don't worry the next one will see that you are the best
-
Never apply for a job that has been posted in stackoverflow.
(Oh! And never work in stackoverflow, too!)1 -
Be confident
use buzzwords
know your shit.
So many applicants I've interviewed only tick the first two boxes.
Also, remember you are interviewing them as much as they are interviewing you.1 -
Write every dev project (even the smallest ones) you have ever done on your CV. I once used an obscure Python module in a really small project, but they desperately needed someone w/ experience with it. It was the reason I got that job.2
-
Quick question about resumes. Is it ok to talk about personal projects directly on them? I was always told to wait until the interview, but 57 resumes sent later, no interview...5
-
In addition to talking all about yourself and polishing your resume, take a bit of your time and learn something about the company that should hire you. Try to find out what they do, how they do it and what their success story is. And then put yourself in that picture.1
-
- Never lie, if you get the job and they find out you lied on something you have a problem
- Never say "oh this company is too good it will never accept me with my grades", Usually bigger companies have an assessment center where you can show that you are good for this job
- If they ask you for weaknesses try to pick some that can also be seen as strengths -
Be clear on your aim as a dev.
Be truthful of wat u know.
DONT DONT ever try to outsmart a interviewer who himself is a dev for many years.
Lastly keep cool and backup ur skills. -
For compsci/related university students
- work on personal projects, and don't forget that connections made while at university can quickly lead to job opportunities -
Don't just think starting salary - think about your income over the course of your working life.
Your starting salary might be high - but it might mean that your ceiling after that is quite low. If you reach your ceiling too soon, you'll have to retrain to get more dough.
Retraining is starting again and might not jive very well with a partner and children in tow.3 -
Keep your search relatively broad, but find a company that you'd actually like to work at if you can. This would make interviews more smooth because you actually want to work there, and it'll keep your morale high.
-
Don't be discouraged by rejection. If you get rejected from a company it doesn't necessarily mean you're not good enough for them, they might just be looking for a different type of developer, different type of personality, etc. Or they might even have misjudged you based on the 30 seconds they gave you. Of course, you need to sharpen your skills, but decouple that from reactions from companies to you.
-
Always befriend your recruiters and shoot them straight. They are on your team and it’s in both of your best interests to find you a good spot.
-
Take the time to do a little research into the company, then tailor your CV to the company and the position. Don't be afraid to add a little pizzazz, but also don't lie... There's a difference between something that's a little misleading and an outright false claim.
-
Data structure and Analysis
For experienced ones, add "System Design".
...path for big fat packages. -
I have just started working fresh out of college and don't have much experience in job hunting. But I will share what worked for me when I was in college looking for jobs.
In my opinion these are the top three qualities which we must develop while hunting a dev job.
1. Insane focus : work hard. Learn stuff. Complete lessons, projects. Do not deviate from the end goal, and work towards it.
2. Resilience : Don't lose heart over few bad interviews. Keep on trying with the same zeal.
3. Incorporate feedbacks. Don't be stubborn and arrogant. Look out for learning opportunities from any circumstance.
Best of luck -
Title yourself 'object oriented developer'...anyway noone of the stupid headhunters will ever learn what this means and what you might be else. They just 'google'3
-
Be confident. Know your self worth.
I remember one of the best interviews I've had. I knew I'm qualified for the job so I went in with a mentality of "if they want me, they will want me" (in a nice, non-cocky way). It really calmed me down and helped me get the job. -
Ask the community who's hiring, visit user groups and other tech gatherings. Being an organizer really helps also, put that on your resume along with any highlighted side projects. When interviewed and asked something you don't know, say "I'm not sure, but I'm really eager to learn"
-
Brush up on languages/technologies the company is using/what the job post is for. Say what u like/dislike about those technologies. Most importantly, know that even though you will have many bad days, it only takes 1 good day for none of those to matter!!
-
Interviewing is a skill. Technical interviewing is a skill related to but not totally based on coding knowledge. You need to flex this muscle.
Try mock coding interviews with friends. Set up interviews at places you don't necessarily want to work at. Take coding interviews even when you're not looking for a job. -
Just be true to yourself and to them. Know your own terms when looking for a job, and know if their terms fit with you. Ask them a lot of questions. These questions should provide you a glimpse of what their company culture is like. Try to have fun during the entire process. Don't stress out. And believe in yourself!
****these tips are actually somewhat meant for me but we're all in this together in the process of job hunting -
Look at career section in horoscope before interview. So you have idea doing well or shit. Your week should have some Patten. Monday shit Friday is the best for example. So don't put interviews on Monday.
Last you don't need to be the best in interview, but you have to be better than your opponent. -
Have well prepared profiles on linkedin, xing aso. This way job hunters will find you best I think1