Based on data from over 30,000 developer resumes analyzed by CV Compiler (automated resume reviewer), here are ways to upgrade that should lead to getting more job interviews
At some point in the not-so-distant future, it’ll be easier to make a list of remote-unfriendly companies in tech. Until then, bookmark this for the next time you’re on the job hunt.
Can’t find a job working in Go? Perhaps introducing your current team to Go is the solution. In this episode we talk about how Go was introduced at different organizations, potential pitfalls that may sabotage your efforts, some advice on how to convince your team and CTO to use Go and more.
We are currently in tough times. With a lot of people losing jobs and struggling to get back one. I sailed the same ship and just got back a job. I wrote this post to help people who are currently in the job hunt and are facing rejections (by writing about all the rejections I had so far).
I want you to know that job search might be stressful (at times), but you got this! Prepare yourself and go out there; Don’t get hurt by rejection.
While writing the post, I just realized how common the culture of ghosting a person during the interview process has become.
I wish that we get better at not ghosting people as an Industry.
This is an extended version of my essay “When front-end means full-stack” which was published in the wonderful Increment magazine put out by Stripe. It’s also something of an evolution of a couple other of my essays, “The Great Divide” and “Ooops, I guess we’re full-stack developers now.”
This is a lengthy, sprawling piece on the evolution of frontend development by someone who really gets the web. It also has its own art-direction and design so you’ll want to read it onsite vs in an Instapaper-alike.
The panelists discuss their thoughts on career progression while sharing some of their own history. They also talk about important considerations to think about when deciding where to go next, and share useful resources.
This the first majorly bearish case I’ve read on remote work:
… remote work makes you vulnerable to outsourcing, reduces your job to a metric, creates frustrating change-averse bureaucracies, and stifles your career growth. The lack of scrutiny our remote future faces is going to result in frustrated workers and ineffective companies.
Let’s tackle these issues one at a time.
A new study from North Carolina State University and Microsoft finds that the technical interviews currently used in hiring for many software engineering positions test whether a job candidate has performance anxiety rather than whether the candidate is competent at coding. The interviews may also be used to exclude groups or favor specific job candidates.
What’s more, the specific nature of the technical interview process means that many job candidates try to spend weeks or months training specifically for the technical interview, rather than for the actual job they’d be doing.
Be careful out there.
Looking for a new gig? Ryan Choi helps YC startups hire great people and he’s offering free advice to job seekers on their resumes and how to reach out. You can email him your resume at
firstname.lastname@example.org if you want feedback or pointers.
In this post Ryan says to be sure to cover what, how and impact for each position on your resume.
What did you work on? How did you get your work done? What impact did you have?
Mat Ryer talks to a new full-time Go programmer, an intern at Google, and a high-school programmer about the tech world from their perspective.
The two main theses of my professional career have been that distributed is the future of work, and that open source is the future of technology and innovation.
On the distributed front, the future of work has been arriving quickly. This week, a wave of companies representing over $800B in market capitalization announced they’re embracing distributed work beyond what’s required by the pandemic…
Change happens slowly, then all at once.
There are few people on Earth that have been thinking about this longer (and more deeply) than Matt.
Even if you job is secure now, who knows what the future holds? Especially these days, it helps to be prepared. Learn some quick techniques to help make your future job search easier: knowing more people, upgrading your skills, getting public evidence of your skills, plus fallback planning for peace of mind.
To help you succeed as a remote programmer, here at CV Compiler, we analyzed about 1,000 remote vacancies, (~330 job listings for each group), to define the tech skills employers are demanding from remote developers right now.
Some of the particulars in this article don’t feel relevant during the coronavirus-lockdown phase of history, but the overarching message is solid:
Companies waste millions on building the environment they think makes developers happy, without understanding what actually makes developers tick.
What does make developers tick? What motivates us? The answers aren’t always the same, but they often aren’t all that different either. Eduards argues that autonomy, mastery, and purpose are at the heart of it.
After taking a 12-week data science bootcamp and in 2016 and then launching into industry, Dan Friedman’s expectations weren’t remotely met:
Over the past few years, I’ve worked as a Data Scientist, a Data Engineer, and as an industry consultant. I’ve also learned from the stories of dozens of data scientists and similar professions, actively read articles on data science and followed data science thought leaders on Twitter.
Across these diverse data experiences, I have noticed common themes.
Below are seven most common (and at times flagrant) ways that data science has failed to meet expectations in industry. Throughout each section, I’ll propose solutions to these shortcomings.
Maybe I’ve been listening to Practical AI too much, but I am not surprised that one of his seven shortcomings is that most of the job is spent cleaning data. That being said, there’s a lot here that is surprising to me and worthy of consideration for anyone thinking about entering the industry.
I love this idea of having a singular, parseable data source for your resume that can be read & formatted in many different contexts & places. Once cool example of this is react-ultimate-resume which uses JSON Resume as its data source.
Dear New Developer,
You know that there’s a chasm between your skill level and that of the mythical “senior software developer”.
If you build a list of topics you encounter on your job that, if learned to a deep enough level, would put you on the same level as a senior developer, you’ll end up even more demoralized than before compiling that list.
No need to assemble this list yourself! I’ve done it for you.
I’ve heard many people recommend Deep Work over the years. Add this one to the list.
(I like this style of writing where you imagine a hypothetical new developer –knowing full well they real thing is out there– and tell them things you wish you’d known when starting your career as a dev.)
Justin Searls shares some advice on working from home that he’s acquired over 9 years of running a remote company. I like how he breaks it up into advice for humans (everyone), employees, and managers.
I mentioned this post in the resources segment of today’s JS Party recording all about WFH. That conversation hits feeds a week from tomorrow.
Lauren Tan joined us to talk about her blog post titled “Does it spark joy?” In this post Lauren shared the news of her resignation as an engineering manager at Netflix to return to being a software engineer. We examine the career trajectory of a software engineer and the seemingly inevitable draw to management for continued career growth. The idea of understanding “What are you optimizing for?” and whether or not what you’re doing truly brings you joy.
Emily Robinson, co-author of the book Build a Career in Data Science, gives us the inside scoop about optimizing the data science job search. From creating one’s resume, cover letter, and portfolio to knowing how to recognize the right job at a fair compensation rate.
Emily’s expert guidance takes us from the beginning of the process to conclusion, including being successful during your early days in that fantastic new data science position.
Matt Mullenweg, on the potential industry-changing affect that Coronavirus is having:
This is not how I envisioned the distributed work revolution taking hold.
For those asking for tips, my Distributed Podcast has a wealth of advice and stories about how we operate. But here are four good ones to start with
TLDR: Minimize real-time meetings, invest in audio/video quality (yes!), your blog is your new office, and chat tools like Slack and Matrix are a must-have.
Answers are given by the community. If you know how to answer a question well, open a PR. If you are asked a question that is not covered, open a PR. If you see a mistake, open a PR. You get the drift…
I absolutely loved this piece by Cedric Chin about games and their metagames. Fascinating stuff to think about.
Every sufficiently interesting game has a metagame above it. This is the game about the game. It is often called ‘the meta’.
I’m a fan of games (who isn’t?), and every game I’ve ever really gotten obsessed with has had an even more interesting meta. Oh, and if you’re looking for some kind of a direct link to software development, here you go:
Everyone eventually quits. So, what kind of quitter are you? Are you a bridge burner, the 2-week lame duck, or a generative quitter?
Here’s what Dave Evans, co-founder of Stanford Life Design Lab, has to say about quitting.
Whether your next quit is years away or you wish it were tomorrow—there is no avoiding it. You are going to be a quitter. What kind of quitter, though, is all up to you.
The two most common types of quitter are the Bridge Burner and the 2-Week Lame Duck. But we have a radical third option—the Generative Quitter.
But what’s this Generative Quitter about?
The Generative Quitter is a radical third option. Most people think of quitting as a negative, destructive thing. It means leaving, ending, bailing out. But quitting is also the critical turning point between finishing well and starting anew. Let’s re-frame quitting into a chance to refresh and renew things for the company and a chance for you to author a great final chapter of your old job en route to a great next job.
Jared Nelsen tells a story that we’re all too familiar with. Nothing new there, but the analysis and concluding thoughts are worth sticking around for. My favorite:
There is a fundamental mismatch between the public square’s claim that companies are absolutely desperate to hire software engineers and the brutal reality of being a software engineering candidate. These do-or-die high pressure coding challenges seem like more of a hazing mechanism rather than a valuable evaluation tool. Using them is like hiring a police officer by shooting at him before you ask him what he knows about the law.