Gergely Orosz is back for our annual year-end update on the tech market, writ large. How is hiring? Has AI really changed the game? What about that OpenAI fiasco?
We also talk in-depth about Gergely’s self-published book, The Software Engineer’s Guidebook, which has been four years in the making.
Valerie Phoenix from Tech By Choice joins Amal & Kball to tell them all about her non-profit that’s passionate about helping people interested in technology, no matter their experience level.
KBall and Amal go deep on careers. They share their career journeys, talk through learnings and mishaps that happened along the way, and break down key factors to understand about big role transitions like “Senior->Staff” as well as “Engineer->Manager”.
On Monday, Kelsey Hightower announced his retirement from Google. On Tuesday, he sat down with us to discuss why, how & what’s next.
Along the way, Kelsey teaches us how not to suck at work, analyzes his magical demos, fights off the haters (again) & opines on System Initiative, Dagger & 37Signals moving off the cloud.
The panel dives into a topic that makes most software developers cringe: Professional networking. Starting with a definition - what does it even mean? - they go into hacks they’ve found for getting more comfortable with networking, building your network in person or online, and then using your network to find new job opportunities or consulting work.
Mat & Johnny interview everyone’s favorite LLM (Natalie with a special hat on) to see if it’d make a good hire as a Go dev. Also, Mat tries to turn it into his very own creepy robot by asking personal questions about his co-hosts. Things get weird. In a good way?
This week we’re back talking to Gergely Orosz — this time not quite about the insane tech hiring market, but more so the flip side, the 180, the not so good tech hiring market, the layoff market and what you can expect. There’s a lot of FUD out there, so hopefully this show gives you a lens into what’s really going on, and what to really expect. Maybe more so, how to keep your job or find a new job. We come to this topic with great compassion and great understanding, so please…there is a community here for you. There’s a lot of people in our Slack. Call it your home, it’s free to join and everyone is welcome.
In this episode, we will be exploring interviewing as a Software Engineer. Tips, tricks, and gotchas, as well as potentially some interviewing horror stories and red flags to avoid at all costs. We’re joined by Emma Draper, Engineering Manager at the New York Times based in Arizona, and Kate Jonas, goes by Jonas, Technical Enablement Manager at Datadog based in Denver.
Struggling through the tech job interview process? We feel you! On this episode, Amal, Nick & Amelia get together to discuss the various ways the interview process disappoints, share their own interview stories, and suggest ways we can improve the process for everyone.
This week Lee Robinson joins us to talk about his journey as a DevRel. We talk about what it means to be a DevRel, what orgs they fall under, how he runs his team at Vercel, Lee’s three pillars of DevRel: education, community, and product, we compare the old days of DevRel vs now, and of course what makes a DevRel a good DevRel.
KBall, Ali & Nick explore a new type of segment: “WTFJS” talking about wild and wooly “it’s not a bug it’s a feature” examples in the JavaScript language. They also dive into code maintainability, and end by discussing the whiplash shift in the tech industry from “hottest market for engineers in history” to “oh noes everything is stopping!”
This week we’re joined by Jacob Kaplan-Moss and we’re talking about his extensive writing on work sample tests. These tests are an exercise, a simulation, or a small slice of real day-to-day work that candidates will perform as part of their job. Over the years, as an engineering leader, Jacob has become a practicing expert in effectively hiring engineers — today he shares a wealth of knowledge on the subject.
Liana Leahy tells Amal and KBall all about her journey from software engineer to product manager. Along the way we learn what a PM does, how to be great at it, how to know if it’s for you, why the role is in such demand these days, and much more. - It’s UNIX, I know this!
Ashley Willis and Ela Krief join Natalie to discuss the ins and outs of management. They discuss what makes a good manager, common mistakes managers make, how to communicate effectively, dealing with conflict, and much more.
With the constant demands of work and life we often don’t take much time to ensure that we’re maintaining ourselves. In this third episode of the maintenance series, Kris is joined by co-host Natalie, along with Ian Lopshire to discuss the ways in which we can maintain ourselves in this busy and chaotic world.
This week we’re joined by Gergely Orosz and we’re talking about the insane tech hiring market we’re in right now. Gergely was on the show a year ago talking about growing as a software engineer and his book The Tech Resume Inside Out. Now he’s laser focused on Substack with actionable advice for engineering managers and engineers, with a focus on big tech and high-growth startups. On today’s show we dig into his recent coverage of “the perfect storm” that’s causing this insane tech hiring market.
The panel discusses all the things that have to happen before you write a lick of code. Then, for Story of the Week: Dan Abramov thinks npm audit is broken by design. We also have thoughts. Lots of ’em.
KBall, Amal, and Nick dive into key dimensions of what makes a developer work environment good – or bad. They discuss systemic factors, individual factors, what you can do about it, and a proposed scoring system for good work environments.
Kamran Ahmed, creator of Developer Roadmaps, joins Jerod to talk through his 2021 roadmaps to becoming a web developer.
We cover why Kamran created these resources, who they’re for, how to interpret them, and then take a stroll down the paths to becoming a frontend and backend developer.
Which path are you on in 2021?
Gergely Orosz joined Adam for a conversation about his journey as a software engineer. Gergely recently stepped down from his role as Engineering Manager at Uber to pursue his next big thing. But, that next big thing isn’t quite clear to him yet. So, in the meantime, he has been using this break to write a few books and blog more so he can share what he’s learned along the way. He’s also validating some startup ideas he has on platform engineering. His first book is available to read now — it’s called The Tech Resume Inside Out and offers a practical guide to writing a tech resume written by the people who do the resume screening. Both topics gave us quite a bit to talk about.
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.
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.
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.
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.
