📎 Webclip
Thread de @oliverjumpertz: For the last two weeks, I posted at least one thread every day about cracking your tech in…
Oliver Jumpertz shares a meta-thread collecting his recent series of threads for software developers. Over two weeks he posted daily about cracking tech interviews, marketing yourself, and growing as a developer, and here he links each thread and hints at more content to come. The collection covers handling common interview questions, understanding your market value, building a personal brand, leveraging LinkedIn, and general growth advice, plus future plans like content on starting a business and content creation.
Reading notes#
- The author introduces this as a collection of threads from the last two weeks on cracking tech interviews, marketing yourself, and growing as a software developer.
- He highlights the interview question “Are there any questions left we can answer?” as a chance to stand out and leave a lasting impression.
- He addresses “Where do you see yourself in five years?” and notes many candidates dislike it, but he suggests it can be turned into an advantage.
- He argues developers should give themselves a stronger professional title than “Junior X Developer,” saying how you call yourself should differ from how your employer labels you.
- For “Why should we hire you?”, he calls it an insane and uncomfortable question, but says there are specific dos and don’ts for answering.
- On “How would you rate your XY skills on a scale of 1–10?”, he notes people already dislike grading and calls it tricky, yet claims you can turn it into a big win.
- For “Why do you want to work here?”, he says it is more complex than simply wanting the job and that there is more behind the question.
- On “What’s your greatest weakness?”, he observes that people already have many weaknesses and may resist talking about them, and he frames this as a chance to become more self-aware and reflective.
- He stresses the importance of a personal brand, claiming that good self‑marketing can lead to strong results and even inbound interest from recruiters and clients.
- On “What is your current salary?”, he criticizes companies that base offers on current pay and calls this mindset BS, then points to a guide for handling the question.
- He includes a thread on understanding how much you are worth and what salary level you can reasonably ask for.
- He links advice for aspiring developers that he wishes he had received earlier, noting that some of it can also apply to senior developers.
- He provides a guide on data structures for software developers, explaining their importance, which ones to learn, why they matter, and offering learning resources.
- He offers a seven‑step guide for system design interviews to help candidates approach them in a structured way and improve their chances in that round.
- He shares guidance on using LinkedIn to get more interviews by optimizing the profile once and benefiting passively from it.
- He outlines future content topics: marketing yourself, growing as a developer, starting a business, content creation, cracking interviews, and other material aimed at helping people reach their goals.
- He closes the thread hoping the collection was useful, inviting readers to like and retweet, and encouraging those excited for future content to follow his account.
- In replies, he confirms that each thread will become its own blog post when he finds time.
- He repeatedly thanks individual commenters and says their positive feedback makes him happy.
- He mentions he is thinking about refining the interview series and possibly turning it into a short ebook with additional content.
