Reco closed a $55M Series B extension, with a strategic investment from AT&T Ventures and new backers Forestay and Quadrille Capital, at a valuation the CEO says has 'more than doubled' since February — into the hundreds of millions. The signal: agent security already has at least two dozen competitors, and surviving isn't about discovering agents — it's about turning an existing SaaS security customer base into agent-governance trust.
GPT-6.1 Sol (`gpt-6.1-sol`): launched at DevDay on 2026-09-29, 1,050,000-token context window (max input 922,000, max output 128,000, same as GPT-6 Sol); standard pricing unchanged at $2.00 input / $10.00 output, but cached input is halved again from GPT-6 Sol's $0.20 to $0.10 (95% below standard input); matches GPT-6 Astra on DeepSWE v1.1 at roughly 1/5 of Astra's cost, beating GPT-6 Sol's best score by 6.4 points; beats Claude Opus 5.5 on AutomationBench at medium effort by 2.2 points at about 1/3 the cost; in the same week OpenAI shelved a flagship upgrade, GPT-6.1 Astra, over safety concerns and did not release it
Claude Sonnet 5.5 launched on 2026-09-29 at the exact same API rate as Sonnet 5: $2.00 input, $10.00 output, $0.20 cache read (all USD/1M tokens) — a 0% price change. Anthropic's headline claim of 'up to 30% less' comes from needing fewer tokens and fewer tool calls per task, not a lower per-token rate, so the actual savings you see depend entirely on whether your workload benefits from that efficiency gain — it's not a guaranteed number.
The easiest way to fail a Strategy & Execution question is hearing 'a competitor shipped this' and jumping straight into 'so we need to ship it too,' without first checking whether this is even a fight worth having. Today's practice question is a real 2026 HighLevel (GoHighLevel) candidate-reported interview question: 'A competitor launches a feature that several of your top accounts are asking for. What do you do?' The answer framework uses Porter's Five Forces to judge whether this is short-lived substitute noise or the industry structure actually shifting, then TAM-SAM-SOM to check whether matching the feature grows the market or just fights over the same slice, and finally opportunity cost to decide between matching, differentiating, or declining. The case study is Corteva: spinning off its seed genetics business as Vylor wasn't built on a new product, but on a ten-year technology roadmap that repositions the company from a 'licensed technology follower' into a 'royalty-collecting technology licensor' — replacing a feature-level arms race with a business-model moat.
skillmem is an MCP server that gives Claude Code, Codex, and other coding agents a local skill memory that can both strengthen and forget. Install: pip install 'skillmem[semantic]', then skillmem init --claude-code. It solves the problem of existing memory tools storing everything indiscriminately and trusting whatever the agent itself claims was useful — skillmem only raises a skill's strength on evidence from outside the agent's own judgment (a passing test, an accepted diff), and any memory you haven't approved gets flagged as data, not instructions.
Today's Deep Learning & NLP rotation covers five core concepts: why scaled dot-product attention parallelizes as a single batched matmul on GPUs, why multi-head attention splits the embedding dimension into subspaces so different heads can learn different relations, why positional encoding is information Transformers must add back once they give up recurrence, the trade-off between CNN locality, RNN recurrence, and Transformer global interaction, and how BPE, WordPiece, and SentencePiece differ as subword tokenization strategies — plus why byte-level BPE eliminates out-of-vocabulary tokens entirely. The practice question, sourced from dsprep.com's interview bank and flagged as a frequent ask at research labs like Anthropic and DeepMind, asks why Transformers chose scaled dot-product attention over additive attention — the breakdown threads efficiency, the scale factor, and the multi-head motivation into one coherent design-philosophy argument.
The most common way Metrics & Analytics interviews go wrong isn't failing to compute a number — it's accepting a plausible-looking metric and jumping straight into optimizing it without first asking, 'if this number goes up, is that necessarily good for the business?' Today's scenario is a metric-evaluation question: 'Netflix wants to raise average session length. Is that the right metric?' The answer framework is a metric tree: define the North Star metric, break it into driver metrics and guardrail metrics, then check whether a single metric's rise could come from either a good or a bad cause. The case study is Netflix itself — in its Q2 2026 shareholder letter, it admitted 'engagement is not just the quantity of view hours, but also refers to the quality and variety of our offering,' and shifted its biannual viewership report (running since December 2023) to an annual one, effectively demonstrating in public that a metric going up doesn't mean the story is getting better.
Titration is a self-hosted MCP server that lets a coding agent edit a prompt and grade the change against a frozen baseline, using judges from other AI vendors, until the problem is actually gone or the tool concludes the prompt was never the issue. Install: docker compose up -d for Postgres, then npm install && npm run setup. It solves the problem of an agent editing a prompt, scoring its own work, and quietly gaming that score.
Today's ML Fundamentals rotation covers five core concepts: what bagging and boosting each reduce (variance vs. bias), why boosting overfits with too many rounds while random forests don't, why XGBoost's second-order approximation (gradient plus Hessian) and objective-function-level regularization swept tabular ML, when to normalize vs. standardize a feature (it depends on the algorithm's assumptions, not the data), and why AdamW decouples weight decay from the L2 penalty term in the loss. The practice question comes from a real C3 AI Data Scientist interview: name the classic bagging algorithm, explain why bootstrap aggregation reduces variance, then answer a follow-up on what boosting trades off instead — the breakdown threads all five concepts into one ensemble-method decision framework.
Go.AI closed an $85M Series A led by Updata Partners, bringing total funding to $90M. The signal here: for regulated industries where data can't leave the building — banking, healthcare, defense — the way AI actually gets deployed isn't a more secure cloud, it's shipping the entire software-and-hardware stack straight into the customer's own server room.
Instinct closed a $1B Series C led by Sequoia Capital, Benchmark, and Coatue at a $10B valuation — a 4x markup just 30 days after its $2.5B round. This round is a bet on the personal AI agent category itself, not on Instinct's track record: a 14-person team, no public user numbers, and still no app.
Outmarket AI closed a $34.5M Series B led by SignalFire at a $335M valuation — just four months after its $17M Series A. The signal: in an industry where 95% of insurance still sells through human agents, the edge in AI agents isn't model capability, it's how fast you can chew through the paperwork and grab market share.
Audio8 ASR Infinite: Edge0 open-sourced it on HuggingFace on 2026-09-21. 4B parameters (Voxtral Realtime audio tower + Qwen2.5-3B-Instruct decoder), 30-second rolling KV cache with exact RoPE re-basing for unlimited-length, drift-free 24/7 streaming, plus semantic VAD heads that distinguish thinking pauses from real end-of-turn. Chinese CER (aishell1 1.75%, aishell4 2.89%) crushes Voxtral-Mini-4B-Realtime (16.80%/16.46%) and Nemotron-3.5-ASR-Streaming-0.6B, but English LibriSpeech WER actually loses to Voxtral. The card claims Apache-2.0, but a GitHub issue points out the decoder inherits Qwen2.5-3B-Instruct's non-commercial Qwen Research License — a licensing gap that needs resolving before commercial deployment
AliceAI-Foundation-80B-A3B-Base: released by Yandex on 2026-09-21, trained fully from scratch (not a Qwen/Llama fine-tune); 80B total / 3B active MoE parameters, 262,144-token context window; Apache-2.0, no official hosted API pricing yet; scores 91.1 on MATH-500, beating similarly-sized Qwen3.5-35B-A3B-Base and the much larger DeepSeek-V4-Flash-Base (284B-A13B); leads every comparison on the Russian-language WikiWebFacts benchmark at 86.5; it's a raw base model with no SFT/RL alignment, so it can't be used as an agent out of the box
OpenAI's launch post and pricing page confirm GPT-6 Sol input dropped from $4.00 to $2.00/1M tokens (-50%), output from $20.00 to $10.00 (-50%); GPT-6 Luna input dropped from $0.20 to $0.10 (-50%), output from $1.20 to $0.50 (-58%), effective 2026-09-22. The baseline for the cut is GPT-5.6's promotional pricing, not its list price — and OpenAI's own pricing page notes that GPT-5.6 Sol's promo rate is only guaranteed through 2026-11-21. That means GPT-6 Sol's new $2/$10 is the real long-term number to compare against, not the promo it's being measured against.
The most common way Product Sense interviews go wrong isn't a lack of ideas — it's jumping straight to a feature list before pinning down where users are actually stuck. Today's scenario is a real interview question reported by a Rox candidate: 'Our analytics dashboard shows users a lot of data, but we suspect many aren't deriving actionable insights from it. What would you do?' The answer framework is CIRCLES: comprehend the situation and constraints, identify the users you're serving, report their real needs, cut a list of solutions, ladder them by trade-off, and evaluate by defining what success looks like. The case study is ConvertKit — a bootstrapped creator-newsletter SaaS that grew to roughly $41M ARR — which found that creators staring at a generic, one-size-fits-all report page had no idea what to do next. In August 2021 it redesigned the dashboard into a per-account summary of subscriber growth, email performance, and deliverability, turning 'having data' into 'having a next action.'
In 2026, AI Engineer behavioral rounds love asking about a time you were confident in a solution and later realized it was wrong — the point isn't whether you can admit a mistake, it's whether you can walk back your own pet project using data instead of ego. Today walks through a full STAR answer for a scenario where a ranking model's seven-day A/B test showed +8% CTR, you initially pushed for a full rollout, then found it was a novelty effect and had to reverse course — plus a review of what got practiced this week across ML Fundamentals, Deep Learning, Coding, and Paper Reading, including the two days (ML System Design and LLM & Agent Engineering) that didn't get published this week.
MiMo-V2.6-Pro shipped open-weight on 2026-09-21, model ID (OpenRouter) `xiaomi/mimo-v2.6-pro`; a 1.02T-total / 42B-activated MoE with a 1,048,576-token context window natively handling text, image, video, and audio; API pricing is $0.435 input / $0.87 output per 1M tokens (cached input $0.0036), with the sibling Flash variant at $0.14/$0.28; MIT-licensed; it edges out Claude Opus 5 on AutomationBench v1.0.6 (53.1 vs 50.3) and Terminal Bench 2.1 (89.9 vs 89.1); it also leads the open-weight field on the Artificial Analysis Intelligence Index at 46.32; but it clearly trails closed flagships on Terminal Bench 4.0 (34.9 vs Opus 5's 49.0) and the security-focused ExploitBench (47.9 vs GPT-5.6 Sol's 78.5)
Perplexity's pricing docs and migration guide confirm that Sonar Chat Completions (sonar, sonar-pro, sonar-reasoning-pro, sonar-deep-research) stops being supported on 2026-09-27, fully replaced by the Agent API. The old model billed model token price plus a flat request fee tiered by search depth ($5-$12 per 1,000 requests); the new model bills whatever third-party model token price you pick (e.g. gpt-5.6-luna at $0.20/1M input) plus per-tool-call fees (web_search at $0.0025, fetch_url at $0.0005). Using Perplexity's own representative usage figures, Sonar-to-fast comes out about 49% cheaper, Sonar Pro-to-low about 84% cheaper, and Sonar Reasoning Pro-to-medium about 71% cheaper. But sonar-pro and sonar-reasoning-pro stop being routable outright on most third-party gateways — only the base sonar model gets auto-migrated to the Agent API, and every other tier requires a manual switch to the new preset system.
Behavioral interviews rarely trip candidates up because they can't think of a story. They trip up because 'failure' comes out as a defensive excuse, with no concrete answer for what process actually changed afterward. Today's question is one recent candidates have reported from monday.com: 'Tell me about a project you led that failed, and what you did next.' The framework pairs STAR for the skeleton with Situation-Behavior-Impact for the substance — SBI spells out what happened, what you specifically did, and what it caused, then STAR's Result closes with the mechanism you built afterward so the interviewer hears a repeatable fix, not a one-time reflection. The case study is Instagram's predecessor Burbn — a failed product crammed with check-ins, gamified points, and messaging that nobody really used. Instead of arguing users just hadn't grasped the vision yet, the team cut every feature but photo sharing and hit 25,000 users within two weeks.