惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News and Events Feed by Topic
Malwarebytes
Malwarebytes
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cybersecurity and Infrastructure Security Agency CISA
F
Future of Privacy Forum
C
Cisco Blogs
T
The Exploit Database - CXSecurity.com
A
Arctic Wolf
S
Securelist
K
Kaspersky official blog
S
Schneier on Security
T
ThreatConnect
T
Tenable Blog
Spread Privacy
Spread Privacy
T
True Tiger Recordings
AWS News Blog
AWS News Blog
F
Fox-IT International blog
量子位
T
Threatpost
V
Vulnerabilities – Threatpost
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
GbyAI
GbyAI
宝玉的分享
宝玉的分享
腾讯CDC
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
U
Unit 42
雷峰网
雷峰网
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
O
OpenAI News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
MyScale Blog
MyScale Blog
小众软件
小众软件
A
About on SuperTechFans
Last Week in AI
Last Week in AI
Y
Y Combinator Blog
博客园 - 三生石上(FineUI控件)
美团技术团队
Google Online Security Blog
Google Online Security Blog
P
Proofpoint News Feed
MongoDB | Blog
MongoDB | Blog

DEV Community

Gemma 4: The 128K Multimodal Powerhouse in Your Terminal How to Consolidate Your QA Toolstack: A Practical Buyer's Guide Schema Types 2026 Idempotency Keys: The API Safety Net You're Probably Not Using How to let Claude see my Plaid bank data Kiro Did It: Build a Simple Portfolio Website with Kiro IDE | From Prompt to HTML Prototype Islands of Commerce: What Marketplace Founders Can Learn from 60 Years of Island Biogeography React Pointer Hooks: Hover, Long-Press, Double-Click, Scratch, and Click-Outside Without the Bugs Engineering decisions for my video call tool VBScript Still Lives: How a Custom Go VM Brought Classic ASP to Linux and Mac What Happens When You Teach Old Scripting Languages New Runtime Tricks? I Tested 6 AI Coding Assistants for a Month. Here's What Actually Works. Extendscript Still Has Life Afriex Webhook Integration Guide: Signature Verification, Event Handling, and Production Best Practices The Blind Alleys of Veltrix Configuration How an ESP32 Turned a LEGO WALL-E Into a Real Working Robot The Flawed Promise of Real-Time Event Handling SSH Login Taking Forever? Check Your DNS Settings Found 897 Fake Followers on DEV.to. Here's How I Proved It. Retry logic, Kafka consumer lag, and the hidden failure pattern that Kubernetes won’t catch WebMCP Might Be the Most Important Announcement at Google I/O 2026 Build a Secure API with Rails 8 - Part-3: Auth Controllers I A/B tested 4 LLMs on the same 500 queries. The results surprised me. Google I/O 2026’s Smartest Developer Release Wasn’t a Model, It Was the Runtime - Managed Agents in Gemini API OSS Monthly Recap: What My Daily Commit Challenge Taught Me About Open Source “Culture” GemmaNotes Cognitive Debt: AI Is Building Your Systems. Do You Actually Understand Them? GeekNews Frontend Weekly Deep Dive - 2026-05-25 I Built a Universal Silicon Loader That Runs on Any SOC (No Bootrom Exploit) Docker容器化部署Node.js应用最佳实践 I Put a Neural Network in a Thermometer — Then It Got Out of Hand Building MGZon: Developer Portfolio + AI Bot + Social Network (9 min demo) Bearing Life (L10): What the Catalog Number Really Tells You Longhorn Volume Health: The Gap Between 'Healthy' and Actually Working Stop Prompting. Start Specifying: How Spec-Driven Development Fixes AI Coding TIL a PowerPoint file is just a zip — so I converted .pptx to Word entirely in the browser 로컬 LLM 셋업 가이드 (v18) Cx Dev Log — 2026-04-24 github's agent audit api is the boring feature that matters # From Teaching Code to Building Real-World Applications Vivado 2026.1 and Linux: why this decision matters beyond the headline Vivado 2026.1 y Linux: por qué la decisión importa más allá del titular ORA-00206 오류 원인과 해결 방법 완벽 가이드 Entidades finas e composição: o design que escolhi para a nova plataforma 10 Open Source Tools Every Developer Should Know 🔥 SSH Config File Mastery: Turning `~/.ssh/config` Into a Productivity Tool I tried to create a programming language... in python I Replaced 70MB Node.js Log Viewer with a 172KB Zig Binary I Turned npm outdated into a CI Gate — Here's How Don't fall for the Claude Mythos hype Vestige: A Gemma 4 Brain Tracker That Won't Blow Smoke Up Your Ass Gemminate: Transforming Static Textbooks into Interactive Learning Journeys with Gemma 4 Where Did All the Code Playgrounds Go? I built PROOFER - Privacy first Chrome extension that proofreads your texts using Gemma 4 I Automated My Entire Digital Product Business on a $13/Month GCP VM. Here's the Architecture. Beginner's Mind in Engineering and AI How I use AI agents to turn ideas into public demos I Built a Quotation Generator for Kenyan Street Welders Using Gemma 4's Vision The Math Behind Neural Networks — Explained Like Nobody Did for Me 🧨 Understanding TPC with IEEE802.11h What I’m Starting to Look for in Engineers An npm Downloads Comparison Chart in 300 Lines of Vanilla JS — Nice-Tick Math and API-Direct Fetch Vitreus: Local-First Spreadsheet Intelligence with Gemma 4 Transfer Fees, Metadata, and Soulbound Tokens: A Tour of Solana Token Extensions I got tired of re-explaining my codebase to ChatGPT — so I built a VS Code extension Revisiting My Phone AI After Gemma 4: The Upgrade I Didn't Know I Needed I built a privacy-first PDF merger in 7 hours — here's the stack and the lessons Google I/O 2026 made me ask an uncomfortable question: are we still coding, or are we managing builders? SSR with JavaScript: Escaping Node.js Clunkiness with AxonASP My CKA Exam-Day Experience: What Went Right, What Went Wrong, and Lessons Learned Gemma 4 Soft Tokens: The Rise and Fall of 16x16 Words ⚡👀 Two weeks ago, I built a private AI brain on my phone using Gemma 4. Yesterday, Google dropped a new variant that made everything I built feel like a beta test. 256M parameters. MoE architecture. Apache 2.0 license. I broke down what changed and why it mat I got tired of clicking through the Stripe dashboard, so I built a CLI Getting Data from Multiple Sources in Power BI: A Practical Guide to Modern Data Integration Google Is No Longer Just a Search Engine I built GemmaPod - A truly composable and portable AI agent solution powered by your local LLM Gemma 4 E4B caught three planted fabrications in 50 seconds — on a laptop, no cloud How to build an AI-powered content moderation pipeline for user comments Running Gemma 4 on a Modest Machine: Unsloth vs LM Studio vs llama.cpp vs Ollama AI Makes Building Cheap. Our Product Architectures Still Assume It’s Expensive. I built an in-browser Roku TV remote with ~80 lines of TypeScript. Here's how Roku's ECP API actually works The Direction of Blame babbled notes: a sound-to-music agent for people who could not make music before How I Built a Live SQL Workshop Where Students Can't Break Anything Rescuing a Stranded Protocol: Re-Skinning Legacy Code for the Trestle DeFi Flywheel SOLID Heuristics Reveal Incomplete Domain Knowledge — Nothing More AllasCode Intitute / FullAgenticStack: The Intent-Based Router Introducing LogicGrid — Multi-Agent AI Orchestration for .NET AI Prompt Injection, Drupal SQLi Exploitation, and Nmap for Hardening AI Agents & Python Workflows: Anthropic Skills, Jupyter Challenges, and Edge Deployment SQLite Optimization, PostgreSQL Async Queries, & DuckLake Dataframe Spec RTX 5080 Undervolt Benchmarks, CGO-Free CUDA API Binding, & AMD GPU Compatibility Fix Microsoft Burned Its 2026 AI Budget on Claude Code in Six Months. That's the Real Story. Why I Started Learning FastAPI in 2026 I Abandoned Ghost for Months — Then Came Back and Finally Finished It Building an Open MIT-Licensed Ephemeris Engine in C — JPL Moshier Ephemeris 4 Smart Ways to Manage Retries in Side Projects Securing Web APIs: A Practical Guide to Authentication & Authorization Methods Google I/O 2026: AI Built an OS in 12 Hours. I Spent Mine Sorting Screenshots. 🤦 Half a Day, Not a Week: One Nix Flake for Three Machines
The Thank-You Email Almost Nobody Sends (And Why That's Your Edge)
Sarah Mitche · 2026-05-25 · via DEV Community

Only 24 percent of job candidates send a thank-you email after an interview.

Meanwhile, 80 percent of hiring managers say a thank-you note influences their evaluation, and 68 percent say it directly affects their hiring decision.

That gap is the largest free advantage in modern job searching. A 100-word email that takes 10 minutes to write changes how a hiring manager thinks about you. Most candidates skip it entirely. The ones who send it move themselves forward in a way the others cannot.

Here's how to actually write one that works.


What a thank-you email is actually for

The thank-you email is not a politeness ritual. It does three specific things.

It reinforces your interest in the role. Hiring managers are evaluating multiple candidates, and enthusiasm is part of the decision. A candidate who follows up signals they care. A candidate who goes silent signals indifference, even if that wasn't the intent.

It keeps you top of mind. Most interview decisions happen over days or weeks. A thoughtful email lands in the interviewer's inbox while they're still forming their impression. That timing matters.

It gives you a second chance. If you stumbled on a question, forgot to mention something important, or wished you had answered differently, the thank-you email is your last chance to fix it. One additional sentence framing your strongest qualification can change the impression you left.

And it signals basic professionalism. When two candidates are equally qualified and one sends a personalized thank-you while the other goes silent, the choice is straightforward.


When to send it

Within 24 hours. Same day if possible.

A morning interview should produce a thank-you by end of business. An afternoon interview deserves an email that evening or first thing the next morning. A Friday interview gets sent Friday evening or Saturday morning, not Monday. Waiting the full weekend looks like you forgot.

For panel interviews, send individual emails to each interviewer within 24 hours. Reference something specific that each person discussed so the emails do not read like copies. This takes 20 minutes total and matters more than people assume.

The 24-hour window matters because interviewers often debrief within a day or two. An email that arrives during that window can directly influence the conversation. An email that arrives after the decision is made changes nothing.


The five-part structure

Every effective thank-you email follows the same structure. Keep it to 100 to 150 words total.

Greeting. Use the name they introduced themselves with. If they said "call me Sarah," use Sarah, not Ms. Johnson.

One line of thanks. Be specific about what you appreciated. "Thanks for the time today" is generic. "Thanks for walking me through the engineering org structure today" is concrete.

Reference one specific conversation point. This is the most important sentence. Mention something concrete you discussed: a project they described, a challenge the team is facing, a roadmap item they mentioned. This proves you were engaged, not going through the motions.

Reaffirm your interest briefly. Connect your skills or experience to what you learned. One to two sentences maximum.

Close warmly but professionally. Express that you look forward to hearing from them. Offer to provide additional information if helpful.

That's it. No need to recap your resume. No need to oversell. The structure works because it is short, specific, and human.


What to actually write: a worked example

Imagine you've just finished an interview for a senior backend engineer role at a fintech company. The hiring manager mentioned the team is migrating from a monolith to microservices.

Here's what an effective thank-you email looks like:

Subject: Great speaking with you about the Senior Backend Engineer role

Hi Jordan,

Thanks for the time today. I particularly enjoyed hearing about the migration from the monolithic Rails app to microservices, and the tradeoffs your team is weighing on service boundaries.

The work resonates with experience I had at my current company, where I led a similar decomposition over 18 months. Happy to share more detail about the patterns that worked and the ones we had to walk back.

Looking forward to next steps. Let me know if there is anything else that would be helpful.

Best,
Sam

It's 95 words. It references a specific conversation point. It connects to relevant experience without rehashing the resume. It offers value without pushing for a decision. It ends warmly.

This kind of email lands. The generic "thanks for your time, I look forward to hearing from you" version does not.


What not to include

Some habits weaken thank-you emails consistently.

Salary or benefits questions. The thank-you email is not the time to negotiate. Compensation conversations happen after an offer, not before.

A full recap of your qualifications. They already have your resume. One brief reference to a relevant skill is enough. Repeating your experience makes the email feel transactional.

Apologies for your interview performance. Saying "sorry I was nervous" or "I wish I had answered that better" draws attention to weaknesses the interviewer may not have noticed. Don't.

Desperation or pressure. "I really need this job" or "please let me know as soon as possible" comes across as pushy. Express enthusiasm without urgency.

Generic flattery. "Your company is amazing and I would be lucky to work there" adds nothing. Reference something specific instead.

Unrequested attachments. Unless they specifically asked for a portfolio piece or work sample, don't add anything. Keep it clean.


The rejection version

Almost nobody writes a thank-you email after being rejected. This is exactly why doing it works.

Subject: Thank you for letting me know

Hi Jordan,

Thanks for letting me know. While I'm disappointed, I genuinely enjoyed learning about the team and the work you're doing on the payments platform.

If similar roles open up in the future, I would welcome the chance to be considered. I was impressed by the team and the direction of the product.

Best wishes,
Sam

Hiring managers remember gracious candidates. Roles reopen. Teams grow. The candidate who stayed professional after rejection ends up on a short list when something new comes up. It happens often enough to be worth the five minutes it takes to write.


Following up if you don't hear back

If the interviewer gave you a timeline, wait until one business day after that deadline before following up. If they didn't, wait five to seven business days after your thank-you email.

Keep the follow-up short:

Hi Jordan,

I wanted to follow up on the Senior Backend Engineer position. I'm still very interested in the opportunity and wanted to ask if there are any updates on the timeline.

Happy to provide any additional information that would be helpful.

Best,
Sam

If you don't hear back after the follow-up, wait another week, then send one final check-in. After that, move on. Three unanswered emails is the maximum. Beyond that crosses from persistent to pushy.


The math actually works

24 percent of candidates send a thank-you email. 68 percent of hiring managers say it influences their decision.

For 10 minutes of writing, you're moving yourself into a small group of candidates who consistently demonstrate professionalism and follow-through. The math is one-sided. Send the email.


If you're preparing for upcoming interviews, make sure your resume is doing its job too. WriteCV runs an honest ATS score with per-bullet feedback in 30 seconds.