1,343 karma · joined March 16, 2009
mike@homelight.com - for business stuff mike.abner@gmail.com - for personal stuff
I know you don't want to do it, but if you are serious about finding new work then I'd strongly urge you to make your LinkedIn shine. You can always remove it after you find a new job.
What are recruiters going to look for?
First and foremost it's going to be about technology affinity. If they work for a Java shop, they are going to be looking for people with Java or C# backgrounds. If it's a ruby shop then for ruby, python, node.js, etc.
Second, they are going to look to see if what you've actually done matches what they are looking for. Are they looking for someone to do machine learning pipelines? Are they looking to decompose a monolith into microservices? Those should show up in your descriptions.
Third, and probably way less important for many places, but they are also going to look for your company history affinity. Do they think of themselves as "IBM-lite"? Then they'll look for people who have lots of big company experience. Are they a rapidly growing Rails shop? They are going to look for places like Shopify, Stripe, etc.
If they can't find you on LinkedIn, you are putting yourself in a bit of a hole. Not one you can't get out of and be successful without, but it's a handicap.
As an example, and not to try to be self promoting, I received a notification this morning that 445 people had viewed my LinkedIn last week (I'm being generous and assuming LinkedIn is telling the truth here...i know i know). I've been in the industry for 20 years. I'm mgmt now, which makes it slightly different, but out of the 445 views I received 10 or so solicitations for jobs, 5 or 6 people reaching out looking for a job, and 100 or so sales pitches.
Anyway, I wish you luck. I'm hiring (rails, monolith -> SOA, postgres, APIs, etc). Happy to chat if you want to learn more.
How does that pass, well, anything at all without someone saying “that might not be the best idea”!
These arent new, but the extra time from not commuting and WFH has allowed me to spend more time doing them.
HomeLight is working to make US Real Estate easier for all parties involved. We are competing (quite well I might add) against some really big and well known names in real estate and have a very exciting product pipeline in the works. We have central offices in San Francisco, CA and Scottsdale, AZ as well as many branch offices across the country and COVID presented the opportunity to shift to a hybrid-distributed model (once we open our offices again later this year)
Our tech stack includes Ruby/Rails, JS/Node, GoLang, Python, React and React Native, Postgres, Redis, Kafka, Heroku, AWS, and more
Roles:
PRINCIPAL ENGINEER: Looking for our first principal engineer to take the lead on our core technologies.
DIRECTOR: Looking for a director to build out our Home Loans team to compete against modern mortgage providers (better, rocket mortgage, etc.)
ENGINEERING MANAGER: Looking for multiple EMs as we scale our team
SENIOR FRONTEND/FULL STACK/BACKEND ENGINEERS: We are scaling our team aggressively and are looking for engineers with significant experience building for the modern web.
You can see our careers page https://www.homelight.com/careers and our engineering focused page here: https://www.homelight.com/engineering
Please send your info to jobs@homelight.com and mention this post!
Now, figuring out some of those numbers is harder. Okta simplest pricing is $2 per person per month, but to really us it you are looking at paying more like $15 a month. So, per user it's $180 a year. 30 billion / 180 = 166 million users. If average company size is 500, that's 330k companies, which is a lot.
Anyway, those are just very quick back of the napkin numbers. I would guess they've done a little more work to come up with the number.
(pls forgive any math errors/rounding!)
Assuming the time period is reasonable (a week or two), this works well. What I, as a hiring manager, want to avoid is you shopping my offer against 5 others for the next month. This gives people some safety net where they can get through their current interviews with other companies and then compare them at the same time and give me an answer with a known timeline.
If I'm hiring a remote team globally, then you are competing against people I can hire anywhere. A great engineer in Brazil could cost...I don't know...$45,000. An engineer with the same exact skill set who lives in California might be $160,000 and one in Chicago might be $110,000.
If an employer paid $160,000 for every employee then they aren't using their capital very efficiently when they could have saved $115,000 on the employee in Brazil and potentially hired two more people for the team.
So, maybe not 10x deadlier, but certainly way deadlier in total count of deaths.
1 - https://www.cdc.gov/nchs/nvss/vsrr/covid19/excess_deaths.htm
I've been getting paid to write code since 1998. The last few years in management. So I know something about actually being a programmer.
I hired someone who was awesome from a technical knowledge perspective. Friendly, personable, smart, driven, etc. Loved talking tech with him and he had really great ideas.
Anyway, the problem was, I'm running a startup and every single project he was on he tried to model it as "the perfect open source project". So instead of doing something simple in a couple of days he would build this really well abstracted, over engineered (but pretty damn good code!), "beautiful" thing that would take 3 or 4 weeks to deliver.
In the end, it didn't work out for him.
Anyway, my point is that it is not true that programmers hate working on the same thing for longer than necessary. I do. You do. Many others do. But some just love being architecture/purity astronauts and refining that 3 line method into a 7 class inheritance hierarchy.
It took a simple conversation with someone of color for me to even begin to understand this. The conversation was something like:
"The 15th time the guy behind the deli counter calls over your head to the person behind you in line instead of you really understand that you are not only different, but invisible to people because of your difference."
Sure, we've all had something happen a few times. But this is an everyday occurrence to people who aren't a part of the dominant group.
To me, a WASP, I couldn't even fathom that ever happening. It's just not part of my lived experience. How could someone just skip over the next person in line? It doesn't make any sense.
But, that was, and is, my privilege blinding me to the daily plight of so many people.
So yes...we should work to "raise everyone up", but simply being the person with privilege blinds us to the problem entirely.
My experience with rent control proponents (being one myself despite the pure economics problems with it) is that most of them believe that there needs to be a "reserve" of properties that are available for lower income people...service workers, teachers, etc...to rent in or near the place where they work.
The basic reason for that is, until recently, the number of people who want to live in a city like SF, NYC, etc. greatly outstrips the supply of housing. Basically, no matter how much housing you build, there is an endless supply of people willing to pay $X to live here, but $X is way over what is reasonable for a cashier, barista, bartender, teacher, etc. to afford.
Now, there might be better ways to solve that problem, but one of the "easier" and more politically possible ones in cities like SF is rent control. The reality is that SF basically can't build enough housing to satiate demand in any realistic timeframe. So what do you do? Bitch about zoning laws and NIMBY's all day and make more and more workers move to Stockton and Tracy? Or do you actually try to do something that is possible to accomplish about that problem (recognizing it isn't perfect)?
Anyway...rent control is interesting in many ways. Just felt like the number of people I've spoken to about it who believes it lowers rents generally rounds to basically zero.
https://www.npr.org/2020/04/15/835571843/episode-991-lives-v...
https://www.wnycstudios.org/podcasts/radiolab/articles/eye-s...
Then we went WFH due to the pandemic and I took a trip to the office and brought home mine from there.
Great chairs!