OpenAI Forward Deployed Engineer: $280K Role and Interview Loop
OpenAI pays $280K for Forward Deployed Engineers (FDEs). The hiring process is explicitly not LeetCode-style, implying a different interview loop focused on practical deployment and customer-facing AI work. No further detail on the actual loop is provided in the post content.
AI-Augmented 1:1 Prep: 5-Minute Prompt Workflow
Dave Kline describes a shift from ad-hoc 1:1 meetings to a structured 5-minute AI prep routine using five specific prompts, claiming it materially improves meeting quality and outcome clarity.
Shopify's River: Public AI Work as Institutional Learning
Tobi Lütke describes River, Shopify's internal AI coding agent living in Slack, designed with one hard constraint: it only works in public channels, not DMs. This forces all AI-assisted work into the open, creating a 'Lehrwerkstatt' (teaching workshop) where knowledge spreads osmotically. In 30 days, 5,938 employees used River across 4,450 channels; it opened 1,870 PRs in one week (~1 in 8 merged PRs). Merge rate climbed from 36% to 77% over two months purely from collective human feedback, not model changes.
Forward Deployed Engineering 101: The Role, Playbook, and 30-Day Entry Path
A practitioner guide to the Forward Deployed Engineer (FDE) role in Applied AI — covering why AI companies need FDEs, the three-phase job (Audit, Evals, Deployment), decision rules for when to use agents vs. code vs. manual work, and a concrete 30-day learning roadmap for consultants, PMs, and software engineers entering the field.
Anthropic internal practice: how Suzanne stays in the loop with Claude
An Anthropic employee shares that colleagues use a specific practice (via a linked resource from Suzanne) to stay current with Claude's capabilities and understand ongoing work. The linked content is not available in the bookmark, leaving the actual method unresolved.
How to Become an AI Engineer Without a CS Degree: A 12-Month Portfolio Roadmap
A detailed 12-month curriculum for breaking into AI engineering without a CS degree, structured around six phases: Python fundamentals, LLM API mastery, RAG systems, agents, evaluation/deployment, and job search. The core argument is that a portfolio of three shipped projects carries more weight than credentials for most AI engineering roles, with salaries ranging from ~$120K entry to $200K+ with experience.
grill-for-unknowns: An Agent Skill for Surfacing Unknowns Before Implementation
Nico Bailon built the open-source Claude/Codex agent skill 'grill-for-unknowns,' merging Matt Pocock's grilling/grill-with-docs skills with Thariq's four-quadrant 'Finding Your Unknowns' framework (known knowns, known unknowns, unknown knowns, unknown unknowns). The skill and its source article detail concrete techniques—blindspot passes, brainstorm/prototype cycles, interviews, source-code references, implementation notes, and post-implementation quizzes—for reaching shared understanding with an AI coding agent before and during implementation, producing durable artifacts (ADRs, launch packets, CONTEXT.md) instead of leaving alignment buried in chat.
Encode Engineering Domain Knowledge as Agent Infrastructure
> Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually.
Frontier Model Prompting and Orchestration Patterns from the Last Seven Days
> /last7days of Fable 5 and GPT-5.6: What Thousands of Upvotes Say Actually Works > > For the first time, the two newest frontier models are live at the same time, and the window is one week old. Call it the /last7days. I pointed [/last30days](https://x.com/slashlast30days) at [Claude Fable 5](https
Codex Hack: Build a 'Voice' Skill by Mining a Trusted Colleague's Slack/Email History
> another codex hack: for internal facing comms, make it read the last 3 weeks of slacks from someone at your company you trust and admire. ask it to understand what he/she pushes back on, what piques their interest, what they ignore, how they communicate with their team, etc. create a skill that yo