7

You have been ghosted. Move on and never use that recruiter again. It happens from time to time. It has happened to me. Apply for another job.


6

Match the first language in the job ad I haven’t lived in Montreal, but I have interviewed for software jobs there. As a rule, a place seems to primarily English if the English comes first in the job ad. They didn’t ask if I spoke French. It always came up when the French came first. Or, if you have solid proficiency in both languages, check which one is ...


6

On the other hand I don't want a project which could be referred as bad code or something like that (even though I believe it isn't such). So which is it? Everyone is insecure about their work. And everyone understands that old work doesn't represent ones' current level of knowledge. Leave it up. If they ask you about it, you can always suggest ways it ...


6

When I had interviews or applied for jobs, my rule was that if I didn't hear back in two weeks, I followed up once, and if I didn't hear from them after that, I moved on. If they had every intention of interviewing you and had other issues (interview for other person ran longer, forgotten the time, miscommunication), they would have called back and said, "...


5

There's no right or wrong here, but usually we follow the same route thought which we received the information. If the open position was informed by a recruiter, go through them. If it's a direct communication from company, or you noticed the job post on company website while following up, apply in their portal.


5

When applying to software development jobs in Montreal, is it best to use an English resume, French one, or to include both versions? If you see the ad in other language than English, or the job posting mentions the requirement of knowing other languages that English and you happen to be comfortable / proficient in that language, why not attach both the ...


3

Generally, when applying for jobs, regardless of any prior knowledge or existing relationships, the first step should be to respect the employer's process. If an employer has a jobs portal, or all their positions are posted through some specific jobs website (i.e. linkedin or whatever), or the employer uses a specific third party recruiter for their hiring, ...


2

Not necessarily ghosted. It's possible that the person was dragged into something else. Give it some time (say 3 days) and see if you get a response back. If not then just move on. The number of times that haven't got the interview call, due to agent to HR to interviewer miss communication.


2

I am on the other side of the table, in a very similar situation (well, the two projects we are offering are NLP and ML related, but you get the idea...). Every company is different, but still let me explain how this is seen from the other side. In our case we took the initiative and explained the candidates that, while the projects are still not completely ...


2

It may, or may not, rattle you, but most tech leads that are forced, by the company's pipeline, to take part in the recruitment pipeline don't really care about you OSS projects. I know I didn't when I was tasked with such chore. Yes, companies like saying OSS contributions are an advantage and "We look forward to what you are about to share with us", and I ...


2

Your old code may harm your future career only if it contains things code shall never ever contain under any circumstances. I do not mean "while(true)" loops, "goto" mazes, "\\ let miracle happens" comments and other coding sins. They are more like jokes or pranks. At least it may show that you have grown from such jokes and code responsibly. I mean racist ...


1

Now, clearly after years probably both my development skills have increased as well as knowledge of that technology. I don't think the project has crappy code in it, though I try to clean it from time to time and improve. These are positive things. If someone ever brings this code up in an interview (or even if they don't) then you have a great ...


1

Don’t delete it. It can even work for you if you can demonstrate code improvement over time to indicate that You keep pace with the technologies that are relevant to you You improve your code base as you improve your knowledge Code we wrote in the past always look worse compared to the code we write today... that just comes with the territory as we keep on ...


Only top voted, non community-wiki answers of a minimum length are eligible