The 3 things tech recruiters look for in the first 10 seconds Recruiters spend an average of 6–10 seconds on a first resume scan. In that time, they're looking for three things and three things only. 1. Current role and company They want to know: Is this person currently working in a relevant role? Make your current position clear at the top. 2. Years of relevant experience They're mentally checking a box. If the role requires 5+ years, they need to see it immediately. A summary line like "Senior Software Engineer with 7 years of full-stack experience" does the work for them. 3. Key technologies They're scanning for their must-have keywords. If the job requires Python and AWS, those need to be visible in the top third of your resume not buried on page two. Quick test: Open your resume. Look at the top third. Can you spot all three of these things in under 10 seconds? If not, you're losing opportunities before they start. Your turn: What's one of these three that your resume could improve on? Drop it below and I'll share a quick fix.

I’ve been thinking about this a lot lately, what if the real value in this community isn’t just what we learn, but what we share with each other? Everyone here has a unique perspective that someone else needs. What’s one idea or lesson that changed the way you see things recently?

Everytime people ask me about AI quantity take-off tools, I refer them to the Clock Benchmark https://clockbench.ai/ It's a measure of how well the top AI tools can read analogue clocks Claude Opus 4.6 (widely regarded as the most intelligent model) scores 10% Gemini 3.1 gets 30% The reality is these are language models. And visual reasoning is really quite tough I think there is some role for AI in QTOs, like extracting schedules, or simple counts. But measuring m2 of formwork on complex structures Not quite there yet....

Hey all, I spent 15 years as an equipment rental sales rep. Had a successful career, worked at a Cat dealer, a regional rental house, and a large national company after we got acquired. I recently left to build an AI tool, specifically for contractors. Here's what I saw from the inside: all the software tools in rental are built for the vendor, not the customer. Pricing benchmarks, fleet dashboards, utilization analytics, all of it faces the rental house. Contractors just get invoices and pay. So I built a rental intelligence tool for the buyer side. Upload an invoice, see if your rates are fair, flag unnecessary charges, and benchmark against your market. Rate the vendors, and give your team 1 dashboard that combines your entire rental picture/process. The problem I'm running into is trust. I think some people are skeptical of a former sales rep collecting their data, even if the tool is built to help them. So I'm genuinely asking, what would make you trust something like this:

Quantity take-offs involve 3 steps: 1. Working out what to measure 2. Building assemblies 3. Then measuring They are actually unbelievably simple. This video is a deep dive on how to perform construction quantity take-offs