How Do I Know What I Don't Know
Personal essay by engineer Dakota Fabro on mapping your own knowledge gaps — a practical reflection for people building technical careers.
Resource Hub
2467 hand-picked resources, updated every week. Search it, filter it, or just browse a collection and see what catches your eye. Want today’s headlines instead? Read the free AI news feed.
Filtered by tag
Answers come only from resources in this hub, with the sources listed underneath.
45 resources
Personal essay by engineer Dakota Fabro on mapping your own knowledge gaps — a practical reflection for people building technical careers.
Free IEEE-USA livestream webinar on navigating career evolution for engineers amid changing technology and workplace demands.
Details: Registration page explicitly states "No Admission Charge." IEEE members can also claim a PDH certificate, but attendance itself is not restricted to members.
Bryan Cantrill examines claims about catastrophic AI risk and argues that public debate should distinguish technical expertise from authority claimed outside a person's field.
Essay by engineer Sunil Pai on proving yourself as a senior engineer, burnout, and being a good teammate. Free to read.
The site of Prometheus, an AI startup co-founded in November 2025 by Jeff Bezos and Vik Bajaj (co-CEOs) that is building AI tools to speed up engineering and manufacturing of physical products. It raised $12 billion at a $41 billion valuation in June 2026, per CNBC.
Research news from the University of Oxford's Department of Engineering Science: robotics, energy, biomedical engineering, AI and more.
Why I recommend it: A university news page, so it highlights its own wins. A handy way to spot new research before it hits the headlines.
A clear, patient walkthrough of how full-text search actually works inside a database: inverted indexes, term dictionaries, postings lists, tokenizers, BM25 scoring, and how Postgres does each part. Written by Patrick Reynolds and Eric Ridge and published 22 September 2026. Free to read, no sign-up.
Why I recommend it: The best free explanation I have found of what a search engine is doing under the bonnet — useful even if you never touch a database, because it shows why a search box returns what it returns. It is published by PlanetScale, who sell hosted Postgres, so the closing pitch is theirs; the explanation itself stands on its own.
IEEE's research library of journal articles, conference papers and standards across computing, electrical engineering, AI and robotics.
From the site: Search and browse IEEE journals, conference proceedings and standards; abstracts are free, full text usually requires a subscription or purchase.
Why I recommend it: Paywall warning: searching and reading titles, abstracts and citations is free, but most full papers need a subscription, an institutional login or a per-article purchase. Some papers are open access and free in full. Check your school or public library for access before paying, and look for the same paper on the author's own site or arXiv first.
Personal site of Ian Duncan, a software engineer and entrepreneur writing about engineering, AI and life. Essays range from a beginner-friendly guide to AI models to critical takes on AI culture and the apocalypse narrative.
From the site: I
Question banks for more than 100 technical roles — Node.js, Azure, Golang, Kubernetes, OAuth and more — each with sample answers, updated regularly. Free to read with no sign-up.
From the site: Ready-to-use technical interview questions and structured guides for developer roles and frameworks, from Remix to Magento. Updated September 2026.
Why I recommend it: Written for the people doing the interviewing, which is exactly why it is useful — you get to see the questions and the answers they are grading against.
Technical writing on legacy modernisation, monoliths and microservices, technical debt, cloud migration and where AI coding tools break down on large old codebases.
From the site: Check out all latest posts from vFunction including modernization strategies, cloud migration best practices, and company updates.
Why I recommend it: technical rather than promotional, though vFunction sells modernization software. The pieces on AI assistants meeting million-line codebases are the honest ones.
A vetted marketplace matching senior engineers, researchers and AI specialists with companies. Free for engineers to apply and be matched; companies pay only on hire.
From the site: Hire global, AI-first engineers with Index.dev. Skip delays and scale your tech team with pre-verified, secure, and compliant talent to build faster.
Why I recommend it: Free on the candidate side — you are the product being placed. Expect a real vetting process rather than a quick apply button.
Articles on building and managing remote engineering teams, offshore hiring, and the day-to-day of software delivery — free to read.
From the site: Explore the nCube Blog for expert insights on software development, team building, and the latest tech trends. Stay updated and empower your business with knowledge.
Why I recommend it: A staffing company's blog, so it argues for hiring remote teams. Useful for understanding how distributed engineering teams actually get staffed and run.
IEEE pre-university STEM education resources, lesson plans and programs for students and educators.
Engineering and technology news site covering AI, energy, space and hardware, free to read with an optional paid ad-free tier.
From the site: Explore Interesting Engineering for cutting-edge articles, news, and insights on technology, innovation, and the future of engineering worldwide.
Why I recommend it: Broad and fast-moving, sometimes breathless. Fine for spotting stories, worth checking the original source before repeating one.
Official news from CERN, the European particle physics laboratory: accelerator and experiment updates, computing and engineering write-ups, and knowledge-sharing pieces, filterable by topic and audience (general public, students, educators, policymakers). Free to read, no account.
Why I recommend it: Worth following if you want technology news written by the people doing the work rather than by a tech press cycle. The Computing and Knowledge sharing topics are the useful filters for a career audience — CERN publishes plainly about large-scale computing, data handling and open-source work, and the writing is aimed at non-specialists.
Blue Origin's internship listings — paid engineering, business and operations placements, with the application windows and locations for each.
Why I recommend it: Aerospace internships close early — most summer openings are filled by the previous autumn.
Engineering and policy writing from Palantir on data platforms, government deployments, defence technology and how the company approaches privacy controls.
Why I recommend it: Read it critically — it is a company blog on a contested subject, which makes it useful primary material for understanding the industry's own arguments.
Announcement explaining why the Rune IDE was rebuilt from first principles in Go and released under the GPLv3, including a contributor program that shares revenue with outside contributors.
Why I recommend it: A clear read on how open-source projects actually get funded and how new contributors can get paid for their work.
Personal essays from OpenAI's president on engineering careers, hiring, self-teaching and building technical teams.
Why I recommend it: His writing on how he taught himself and how he hires is the useful part — read those posts first.
The official source for the Linux kernel, including release archives, the full kernel documentation and guides for submitting your first patch.
Why I recommend it: If you want to contribute to real open-source infrastructure, the newbies documentation here is the actual front door.
A LeadDev article by Annie Vella on running a technical discussion you do not have all the answers for — framing the problem, drawing people out, and closing with a decision.
Why I recommend it: Free to read, though LeadDev asks for a free account after a few articles. The point that you can lead a discussion without being the expert is the one to take into your next meeting.
A fellowship from a16z for aspiring forward-deployed engineers — people who sit with customers and build software directly against their problems.
Why I recommend it: The forward-deployed engineer role is one of the fastest-growing job titles in AI — this is a paid-attention way in before the market floods.
Observability platform with a free-forever tier for distributed tracing, metrics, OpenTelemetry support and AI-assisted debugging. Useful for engineers learning modern observability and incident response.
AI-powered job search engine focused on IT, engineering, and science roles, with profile-based matching rather than manual keyword search.
Why I recommend it: Good complement to ai-jobs.net if you want matching done for you instead of browsing listings yourself.
Chip Huyen writes clearly about building real machine learning and AI systems: evaluation, data, deployment, and the parts that break in production.
Why I recommend it: Read her posts on evaluation. It is the skill most people building with AI skip.
Western Digital's candidate hub with current openings, hiring events, and what the company looks for across engineering, manufacturing, and operations roles.
Why I recommend it: Company-run hiring hubs like this often list roles and events before they hit the big boards. Worth a look if hardware or manufacturing is your lane.
Free, senior-taught software engineering courses built for career acceleration, with pathways in web, mobile, cybersecurity, data, and AI-native applied engineering.
Why I recommend it: I often recommend CodePath to clients breaking into tech or leveling up their engineering skills without taking on bootcamp debt. The courses are rigorous, free, and taught by engineers who actually hire.
A publisher covering cloud native, DevOps, open source, and AI-native software engineering news and analysis for developers, platform engineers, and engineering leaders.
Why I recommend it: One of the few tech news sources I trust to go deeper than the press release. If you are trying to understand what is actually happening in AI-native engineering, start here.
The September 2 Beige Book finds scarce AI engineers but weaker demand for some junior technology and administrative-support roles.
From the site: The September 2 Beige Book finds scarce AI engineers but weaker demand for some junior technology and administrative-support roles.
Why I recommend it: A useful data point showing that AI is reshaping hiring unevenly—senior AI talent is scarce while some entry-level demand softens.
Free electrical engineering reference library with textbooks, worked examples, technical articles, calculators, and an active forum covering everything from basic DC theory to embedded design.
Why I recommend it: If you are moving toward hardware, robotics, or manufacturing tech, their free textbooks are more useful than most paid courses.
Fast Company look inside Shopify's decision to let engineers adopt AI tools without central approval, and how it changed expectations for output.
Why I recommend it: This is the emerging standard: AI fluency as a baseline job requirement, not a bonus. Plan your skills accordingly.
LeadDev piece on why quantum computing's bottleneck is software, not hardware, and what conventional engineers can learn to move into the field.
Why I recommend it: A rare early-entry lane. If you already write code, the on-ramp described here is shorter than most people assume.
Newsletter breaking down system design and backend engineering concepts with clear diagrams — interview-grade explanations of how large systems work.
Why I recommend it: Use the diagrams as interview prep. If you can redraw one from memory and explain the tradeoffs out loud, you are ready to talk about it in a system design round.
India-based 4-week open-source engineering internship where you solve real GitHub issues, earn MSME-recognized certificates, and build verified proof of work.
From the site: India's 4-week open-source engineering internship. Solve real GitHub issues, earn MSME-recognized certificates, and build verified proof of work.
Why I recommend it: If you need real, verifiable engineering experience on a resume, shipping merged pull requests beats another certificate. Great for students and career switchers building a public track record.
Free virtual work experience that walks you through real engineering tasks and adds you to the talent network.
Why I recommend it: Great resume line for career changers with no industry experience yet. It is real work you can talk about.
Enterprise-scale software outsourcing firm hiring engineers across Latin America.
Why I recommend it: Strong option for long-term contract work instead of one-off gigs.
Elite marketplace connecting top software, design, and finance talent with enterprise clients.
Why I recommend it: The screening is tough; treat the application itself as interview practice.
Freelance network matching senior engineers with fast-moving startup clients.
Why I recommend it: Vetted freelance marketplaces skip the resume black hole — you are screened once, then matched.
A year-long career accelerator that places Black software engineers, data scientists, and managers into small squads of 7 to 9 peers, with senior industry mentors, career roadmapping, accountability, and interview preparation.
In plain terms: This year-long career program connects Black software engineers and tech managers into small peer groups. You can create career roadmaps, receive regular accountability, and work with others to reach your professional goals.
Why I recommend it: Applications open each fall and close by mid-December for the following year. The squad accountability is what makes people actually follow through.
Developer-focused publication for engineers working across different tech stacks and roles.
Why I recommend it: Hands-on developer writing — good for keeping skills current between roles.
Career intelligence, industry deep dives, and Big Tech analysis for senior engineers and engineering leaders, by Gergely Orosz.
In plain terms: This newsletter offers inside perspectives on Big Tech, startups, and the software industry. You can read its career insights and industry analysis to help navigate engineering and technology leadership roles.
Why I recommend it: Read this before a tech interview loop or a comp negotiation — it tells you how the other side thinks.
MIT's resume guidance with samples by field, plus advice on translating technical projects and research into recruiter-readable bullets.
In plain terms: This guide from MIT outlines five practical steps for creating a clear, well-structured resume. You can use it to format your document, write strong bullet points about your accomplishments, and tailor your experience to specific job descriptions.
From the site: Five steps to writing a great resume. Your resume provides an overview of your experience and is often an employer's first impression of you.
Why I recommend it: Especially useful if your experience is projects and coursework rather than job titles.
Slide deck of advice from working technology architects and engineers: how to open strong, when to ask clarifying questions, what depth is expected at junior vs. senior level, and how to talk through architecture, scaling, and performance.
In plain terms: This slide deck shares advice from working tech professionals on handling technical interviews. Use it to learn how to explain your coding process, tackle tough questions, and tailor your answers for junior or senior roles.
Why I recommend it: Lead with your strongest projects — interviewers dig into whatever you highlight.
Created by Justin Smith — Launchpad Library
Talent network connecting engineers and operators with fast-moving startups.
In plain terms: This free talent network connects engineers and operators with early-stage startups. You can sign up once to get direct introductions to founders who are actively hiring.
From the site: Join the speedrun talent network. One signup. Warm intros to founders. Hundreds of placements across the portfolio. Free for candidates, always.
Why I recommend it: Startup networks like this move fast. Keep your profile current so you are in the batch when they source.