4 ms·
Well, all that said, it's been interesting that no one has wanted to work with me. Frankly, it was shocking, as I definitely have the skills, experience and "so
by ChrisMarshallNY 6y ago
Well, all that said, it's been interesting that no one has wanted to work with me. Frankly, it was shocking, as I definitely have the skills, experience and "soft" skills, like Accountability and Responsibility, as well as years of experience at selling difficult projects to real hard-nosed, empirical managers.
I also would have been quite willing to work for a fraction of what people that don't have my chops would want.
The worst was working with recruiters. They are downright insulting. Quite jarring.
Whiteboard/LeetCode tests are a flat-out insult to me. I won't do well at them, and I'm quite aware that people spend huge amounts of time, practicing for them, so I don't have a chance.
I do have a few hundred thousand lines of code, dozens of blog articles, dozens of repos, and a decade or more of checkin history. I've been told that I "faked" it, which would be hilarious, if it weren't so insulting.
In the end, I just decided to stop looking for work, and I'm working in a small startup team, writing some fairly powerful software, for free; because I enjoy doing this stuff.
It's pretty odd that the current scene is actively hostile towards folks like me. I feel that it's fairly self-destructive.
- chrismcb 6y agoWhy do you feel whiteboard problems are an insult? And why do you feel you don't do well on them? Just because others spend a ton of practice on them, didn't mean you don't have a chance.
- ChrisMarshallNY 6y agoBecause most are "young-pass filters," and that makes itself obvious, as soon as I see them. I've learned that when I see a binary tree question, I might as well just wrap up the interview. They have no intention of hiring me. I am mediocre at them. Most represent stuff I haven't done. A lot of it is common sense, but I'm solving them for the first time, so my approach is usually sub-optimal (I tend to start with naive approaches, then refine, if necessary). The testers are usually looking for a formulaic approach. A lot of my approaches are orthogonal to the "classics." I started as an EE, so I'm pretty good with things like drivers, SDKs and APIs, but they aren't really something that you can do in a 50-line test. What's really insulting, is that when I'm asked, I usually send links to relevant gists or repos; often focused on the exact method that addresses the question asked. It's ignored (so far, 100% of the time -the "faker" comment was made by someone that was explaining why they ignored it).
- saagarjha 6y ago> I'm working in a small startup team, writing some fairly powerful software, for free If you don't mind my brusqueness, how are you feeding yourself?
- ChrisMarshallNY 6y agoSavings (not like I have choice). I’m also looking to establish some cred that just can’t be ignored. I’m fairly good at that kind of thing; it just takes time.
- MattGaiser 6y agoIn the USA, do most companies whiteboard/LeetCode? In Canada, it seems that only a minority of (admittedly top) companies do. At least up here, not being able to do algos is a barrier to top tier employment, but certainly not employment in general.
- bradlys 6y agoIn the SFBA, it's almost mandatory for every company that I've interviewed at. (100+) The rest of the country has high variance. It will also depend on the company you're targeting. A lot of target companies have a leetcode interview style (I presume every other interview style has too high of a pass rate).
- 908B64B197 6y agoThe ones that matter do.
- dasm 6y agoWhy not try to get better at whiteboarding?
- UncleOxidant 6y agoNot the OP, but I've reached a similar place to the OP (I've given up looking for paid software engineering work for now). Why not get better at whiteboarding? Because it's only useful for getting a job in certain types of companies. It's not a useful skill in doing the job. People spend hundreds of hours practicing to answer whiteboard interview questions - more power to them if they actually need the gig really bad. I just don't want to play the game anymore. Fortunately, there are companies (usually small ones) that aren't obsessed with whiteboarding - my last few gigs have been at places like that. Usually the hiring folks are older (as am I) and they remember what hiring and interviewing were like 20+ years ago.
- x3n0ph3n3 6y agoSome sort of peacocking isn't useful for maintaining a good relationship with a mate, but it's usually important for _getting into_ a relationship... The same thing goes with whiteboarding and interviews.
- ChrisMarshallNY 6y agoBecause every second that I spend on small-batch academic exercises, is a second not spent working on ship code. Here's how I spent today: I woke up at 5AM, like I always do, and did my two-mile walk. During the walk, I sorted through today's job. I'm working on a social media app, and I'm setting up the baseline (admin) stuff. I needed to add the capability to convert "standard" users to "manager" users (and vice-versa), and I'll also need to add UI in the app (native Swift iOS/iPadOS/Catalyst app) to manage permissions. I figured out how I would do it. It was a combination of work on the backend (I needed to add some functionality to the admin user layer), the SDK (I needed to add a couple of methods to funnel the UI requests to the REST API), and the app, itself (I needed to add a button to the user edit screen). The tricky part would be the backend work. I needed to do this in a manner that would not invite any security compromises, and would catch errors. I also wanted to leverage the current structure, as opposed to introducing new structure. Also, I was a dumbass, and used Git submodules in the backend (it's a "layer cake" model). That makes modification a pain. I don't write stuff down, if I can help it. After my half-hour walk, I knew what I needed to do, and, by 7AM, I had the basic framework in place on the backend. I couldn't test it until I also had the work done on the SDK, so I started that (it wasn't much code). Since I wrote the backend a couple of years ago, I also spent time, groping around, re-learning it, and getting my head out of "Swift Mode." The biggest mistake I make, is forgetting to end lines with semicolons. This is where my extremely disciplined coding standards pay off. 99% of the time, I'm the poor schlub that needs to relearn the code, so I make sure that I structure and document very well. By 9AM, I had the whole stack in place, and there were a number of bugs. I like to test, so I was able to figure out where they happened. Most were in the backend, so I spent a lot of time with Charles Proxy, examining the exchange. Some of the bugs required a fairly substantial architectural change. That's pretty common, so I write in a layered, modular fashion with lots of hooks. Makes that kind of refactoring go smoothly. By 5PM, I had it all working, but I need to make the app UI better. It needs a confirmation alert. Otherwise, it's pretty much done. Tomorrow, I'll add the confirmation, and do a lot more testing. This is fairly critical stuff. I can't afford any security lapses here, and I need to make the UX as smooth as possible. Because of the nature of the work, I need to figure out the best way to provide instantaneous user feedback, while waiting for the server to do its work. I'll hammer that out in tomorrow morning's walk. I still need to do the permissions UI, but I won't get started on that, until I'm satisfied that the privilege swap works 100% (I don't move on, until I'm satisfied that my work is at "beta" level, or better). And I spent absolutely no time at all, practicing LeetCode.
- mantap 6y agoI've also been accused of faking things that I definitely did do myself, sometimes I find myself unconsciously playing down accomplishments so as to not to be accused of fakery. What you can keep in mind is that there are very large amounts of money at stake for software engineering jobs. So it is magnet for every kind of faker you can imagine. So don't take it personally, just be thankful that you are qualified for a job that many people wish they could do. And yes the whole thing is a game. The people who are good at the game are most likely to win. So just learn to be good at the game.
- comprev 6y agoI hadn't thought of tech jobs being a target for fraud but it makes sense. Candidates will always test the market for how much they can inflate their experience.
- halbritt 6y agoI’ve been a hiring manager for a few roles. Every one that was posted publicly received approximately 20 applicants that were obviously not suited to the role for every one that was. This is exclusive of any level of seniority, which I like to be flexible on where I can. While I wouldn’t say this is fraud per se, the candidates were obviously using a shotgun approach to apply to any job in the industry.
- heavyset_go 6y agoI'm curious as to whether other roles and industries see a similar signal to noise ratio. I wouldn't be surprised if a lot of people are just applying to every job that's listed in their current location or where they want to live.
- ChrisMarshallNY 6y agoRecruiters and LinkedIn make it worse. LI has some very spammy features they sell to recruiters, based on keywords and tags. I'm a native Swift developer, with over 30 years' experience programming Apple devices, but I have also written a lot of PHP (backend) stuff, and Web sites. A few years ago, I spent a few months, learning Android, and decided I didn't like it, but I do have Java and Android Studio in the mix. I often get recruiters, trying to match me with Web design or C# (nowhere in my stack) jobs.
- rootusrootus 6y agoI'm a little confused by your post. Why do you think you've been singled out and nobody wants to work with you? Simply because you don't excel at whiteboard coding or leetcode questions? I'm honestly curious. I have never had to really do either of those things in order to get great jobs that pay quite well. Granted, I don't work for a FAANG, haven't even interviewed for one, but I don't feel any less successful even so. I'm tempted to think you come off as difficult to get along with, but this is entirely based on your writing style here and may be entirely unwarranted :). I've always found that being agreeable helps an awful lot.
- ChrisMarshallNY 6y agoI'm a bit embittered. It was a real shock, encountering the new environment. I rapidly learned that it's important for hiring managers to establish dominance in the relationship, which doesn't work so well with people like me. I made the mistake of working for a company for 27 years, and the culture changed drastically, during that time. I am a very good person to work with. My LI profile is filled with testimonials as to what kind of person I am. I just believe that humans are very important, and that seems to be an "outlier" philosophy, in today's tech scene.
- nathanaldensr 6y agoYou and I would be fast friends, I think. I've been talking about empathy at work, and I feel like it's a new concept for some.
- 6nf 6y agoIn a normal friendly conversation it’s very rare for someone to openly accuse another person they just met of faking their job history or something similarly serious.
- ChrisMarshallNY 6y ago"Normal, friendly conversations" don't seem to be normal, in today's world. Things have changed. https://www.youtube.com/watch?v=L9EKqQWPjyo https://www.youtube.com/watch?v=L9EKqQWPjyo
- bosswipe 6y agoI'm in somewhat the same circumstance. Have had a very successful 15 year career until this last iteration of job seeking. In all this time I never bothered learning the grab bag of tricks for mathematically optimizing recursive algorithms because it never came up in the many thousands of lines of codes I've written or code reviewed. I've learned many other hard problems and I can usually run circles around all the super smart new grads with their memorized algorithms, but it doesn't seem to matter now.