Tyler Hurtt

Software Engineers - Why are so many CS degrees with 4+ years of experience failing technical interviews that use leetcode? A very strange trend I'm seeing LMK

3

8 Comments

For years, hiring engineers meant one thing: LeetCode, HackerRank, and other similar tools. ➡️ Memorize algorithms. ➡️ Solve puzzles from memory. ➡️ Whiteboard under pressure. But something interesting is starting to happen. More companies are abandoning LeetCode-style interviews and replacing them with AI-assisted pair programming sessions. Candidates can use tools like ChatGPT, Microsoft Copilot, or Cursor while solving real problems. Because the reality is…that’s how engineers actually work today. Instead of testing memory, these interviews focus on things that actually matter: ➡️ How someone breaks down a problem ➡️ How they prompt and collaborate with AI tools ➡️ How they validate and review AI-generated code ➡️ How they think about architecture and tradeoffs The engineers we talk to every day at Nxt Level are overwhelmingly in favor of this shift. Why? Because it feels: ➡️ More realistic ➡️ More collaborative ➡️ More reflective of the actual job So now I’m curious… Are we watching the beginning of the end of LeetCode-style interviewing? Or do algorithm interviews still have a place? Would love to hear from: ➡️ Engineering leaders ➡️ Founders ➡️ Engineers who’ve gone through interviews recently What are you seeing? #Hiring #EngineeringLeadership #AI #SoftwareEngineering #TechHiring #Startups #Recruiting

15

10 Comments

"Texas Tech University is positioning itself and the state of Texas as leaders in the AI race by being one of the first universities to purchase the NVIDIA GB300 NVL72 - a system purpose built for large scale AI training and inference,” - Chris Malachowsky This investment in AI infrastructure, powered by the NVIDIA accelerated computing platform, drives economic growth, fuels research and workforce development, and strengthens America’s industrial ecosystem to compete globally.   Learn more: https://bit.ly/4rWOJBy 

3

Sharing a project I’ve been working on recently; a coding task tool to help companies hire software engineers faster. It's called: Task45.com As a recruiter of software engineers, I see the time it takes for companies to build and review coding tasks. A few days to send it out, a few more to find time to review and boom, the candidate has gone. With AI gaining trust, now might be the time to find a better way... Enter Task45 💥 With just a prompt (or a job description), Task45 will build out a coding task for you to share with engineers. As soon as the task is complete, it will review it instantly. Key benefits;  -45 min duration (to increase submission rates)  -AI-pair programming (for guidance and collaboration)   -Cheat-detection capability (for honest submissions)  -Immediate AI scoring (so you can act fast) -Human override options (for training the model) It’s ready to use today. Who's it for? -Recruiters -Non-technical founders -Time poor engineering teams If you think this could help shorten your hiring cycles, head to www.task45.com and give it a try! All feedback welcome! 

32

5 Comments

DON'T attend coding BOOTCAMPS ⚠️ here is why Most coding bootcamps teach you how to pass interviews — not how to build real apps. I’ve seen bootcamp grads who know every algorithm question... But freeze when you ask them to build a real production app with auth, payments, API integrations, and state management. Tech companies don’t pay you to solve leetcode puzzles. They pay you to ship features that solve real problems. If you want to actually grow as a dev: ✅ Build real projects. ✅ Work with real users. ✅ Break things. ✅ Fix things. That’s where the real learning happens. 💯 #softwareengineering #codingbootcamp #mobiledevelopment #reactnative #startup #developerlife #careeradvice

180

38 Comments

Game changer: Claude Code paired with Playwright CLI Playwright allows computers to work with the visual hierarchy of web pages, interact with page elements and take screenshots. Other ways to interact with web pages from Claude include the Claude Chrome extension and the Playwright MCP server. Both options are heavy on token use because they force the LLM to process images and a large MCP surface area. With the Playwright CLI you get token efficient browser processing. By default it's headless but you can also have it show what is seen in a window. Some ways Claude + Playwright CLI helped me recently. Testing Some AI generated code was completely broken on some API calls. The problem was the data shape was wrong so the tests "passing" meant nothing. Adding Playwright in the loop provided Claude a way to test the code in the same way a user would use the app. Iterative Design I pointed Claude at the current state and the reference for a "good" design I wanted to move towards. I interacted in real time regarding how the page was looking and directed test cases to further check behavior. I am currently exploring other use cases and I'm excited for a functional level up in my workflow. Are you doing visual work with AI? What tools are you using?

5