Upwork is a cesspool. There's a lot of shady shit going on in there. Another scam they're doing there is for someone to borrow your Apple App Store or Google Play Account to upload their build.
Someone is pretending to be me
231–240 of 395 posts
Re: Someone is pretending to be me
#232Earlier quoted context omitted.
BTW, why are you applying just for internships? I checked out your (non-forked) github repos and you're definitely better than I was as an intern. It's not senior engineer level, but you could definitely go for at least a junior eng position for sure. God knows we hire much worse junior FE engineers than that. Or are you interviewing for FAANG(-like) positions only? edit: small tip though, I would rename the App2.js…
My kid chose this approach. He had a mix of startup and bigger (not mega-) company experience and chose FAANG internship because they have the infrastructure to make an internship productive. This was from some advice he received. By "infrastructure" it's not just code (CI, tools, etc) but personnel, how they come up with projects, etc. New grads or still-undergrads may have a lot of programming experience but none o…
> By "infrastructure" it's not just code (CI, tools, etc) but personnel, how they come up with projects, etc. New grads or still-undergrads may have a lot of programming experience but none on working as part of a team.
Fully agreed, the code part of the job is really only 20%. The rest is learning to do so in a team and business environment, which is actually much harder than programming.
I learned this in a startup however and would definitely recommend it to others. You learn less "the correct approach", but more or less get shoved into doing bigger things earlier since all the big guns are focused on some ungodly hard problem. So all the medium-hard problems get shoved to the juniors and interns. It's not the healthiest environment sure (I was doing 40hr/wks as part-time frequently), but if you can survive in it for a while you gain tenacity and a lot of skills that are hard to normally deepen until later.
Re: Someone is pretending to be me
#233I wonder how widespread this really is? If it's reasonably common, there might be a place for a "reputation protection" service in the tech community - a service that watches various contracting and hiring sites for its members names, then notifies the real person when their name is used. I could see it being a real issue in the future if someone's professional reputation is tarnished this way. If a prospective emplo…
My new startup is a protection racket! Sure would be a shame if your good reputation was tarnished by some low-skill offshore devs...
Re: Someone is pretending to be me
#234Maybe it's time to add PGP public keys to resumes.
Re: Someone is pretending to be me
#235A long while back I was sitting in a coffee shop, and happened to meet a guy recounting his work history to a client. The hilarious part was hearing my life plagiarized off my web CV at the time. Seeing the con describe climbing an antenna mast where I worked was awe inspiring given he was over 350lbs. I tipped off the client to do his own verification after, as there was no way that guy was part of our small team at…
Can you give more details about this stenographer tactic?
Re: Someone is pretending to be me
#236This story is much more fun when you come at it from the interviewer's position. You've been doing interviews every week. They're mostly rejections. They're the same questions over and over with minor variation. You're about to repeat the experience for the 18th time and you're 100% on autopilot. But suddenly you're in a spy thriller. This is the greatest thing that's ever happened. Is it a good legal/corporate decis…
I feel like this PND thing might just be an agency for the folks on https://www.reddit.com/r/overemployed to outsource the acquisition of their 2nd, 3rd, 4th jobs.
Re: Someone is pretending to be me
#237Earlier quoted context omitted.
BTW, why are you applying just for internships? I checked out your (non-forked) github repos and you're definitely better than I was as an intern. It's not senior engineer level, but you could definitely go for at least a junior eng position for sure. God knows we hire much worse junior FE engineers than that. Or are you interviewing for FAANG(-like) positions only? edit: small tip though, I would rename the App2.js…
My kid chose this approach. He had a mix of startup and bigger (not mega-) company experience and chose FAANG internship because they have the infrastructure to make an internship productive. This was from some advice he received. By "infrastructure" it's not just code (CI, tools, etc) but personnel, how they come up with projects, etc. New grads or still-undergrads may have a lot of programming experience but none o…
I've supervised a ton of internships, and was an academic before that.
The success of internships is largely preordained by the quality of the mentor. Specifically: careful project selection, good advising particularly in the first few weeks, and political/social capital to translate internships into offers (both at the company and elsewhere). Interns can screw things up, and in rare cases heroically rescue an internship, but the liklihood of a good outcome for the average intern is often preordained.
So the real advice is to find an excellent mentor. But that's really hard because you rarely know who the mentor is when applying. In lieu of better information, FAANGs and Better-than-FAANG (eg Jane Street) are a good proxy because they disproportionately pull individual contributors with significant experience mentoring juniors: PhDs, people who TA'd during undergraduate, etc.
Re: Someone is pretending to be me
#238Earlier quoted context omitted.
> In fact, down to two pointers, left and right, iterating over a list of heights to find how much rain water it can trap. Ah haha I hate that question It should be banned everywhere, oh well. I once saw a physicist (not even a coder) give a really cool answer to it though, I wish I could remember it.
I remember being asked this during my interview at Google. It was the first time I heard it and I gave an answer that iterated over the list twice. The interviewer said that it wasn't good enough and I am only allowed to iterate over it once. He didn't let me write my O(2n) solution down so he returned a strong no as feedback.
He probably got chastised for poor interviewing in Feedback on Feedback.
Re: Someone is pretending to be me
#239Andrew here. Connor, thanks for releasing this on the orange site. This story is also more fun from my position. I've been applying to internships and interviewing every week. They're mostly rejections. They're the same questions over and over with minor variation (sorry to top comment for "impersonating" your comment style). My days are deteriorating from a colorful sphere down to two points. In fact, down to two po…
BTW, why are you applying just for internships? I checked out your (non-forked) github repos and you're definitely better than I was as an intern. It's not senior engineer level, but you could definitely go for at least a junior eng position for sure. God knows we hire much worse junior FE engineers than that. Or are you interviewing for FAANG(-like) positions only? edit: small tip though, I would rename the App2.js…
Ha! You're good. I'm still in uni, so I am interviewing for internships (mainly for big tech companies right now since I had a taste at a IoT startup last year). Perhaps I am underestimating myself, but I'm in no rush.
Thank you reminding me about that diagramming and xml-parsing repos. Regarding the diagramming repo, that was honestly some of worst code I've written (2000 lined React class with 15 states). It's so bad that I put a warning in the repo and haven't gone back to it since. And regarding the xml parsing repo, wow, you really looked carefully! I however added a funny warning regarding this in the readme (https://github.com/BlastWind/xml-leaf-highlighter#design-dec...). I wanted to use regex since it was just a school project. Going to add an additional warning, thanks.
Re: Someone is pretending to be me
#240Earlier quoted context omitted.
A big reason why a lot of companies are trying to push people back to the office is they have low confidence that line managers will catch these kinds of problems, and many more - including 'the guys working 4 jobs and barely doing anything for us', the 'guy starting his own company that competes with us at the same time as working for us', the 'guy who farms out all his work to subs in India', etc. It's easy to say…
> A big reason why a lot of companies are trying to push people back to the office Which is kind of useless for most of the points you described at the end. There are plenty of comments here really proving that you can scam even in person interviews. Let's say you are not scam, you pass an interview. You can still do all of those things while you work. The only way to prevent this is by having keyloggers and similar…
It’s harder/nearly impossible to scam at scale in person.
It’s also way more obvious and personal when it happens, and it’s a lot easier to actually physically arrest someone if it gets really weird or out of hand, not that it was common for that to happen.
I think we’re seeing the birth of a new industry, the equivalent of Nigerian email scams, but with job interviews.
Exciting!