Skip to content

Follow-up why keeps the original answer + Principal brief - #1

Open
ginxx009 wants to merge 18 commits into
mainfrom
feature/followup-and-principal-brief
Open

ginxx009 wants to merge 18 commits into
mainfrom
feature/followup-and-principal-brief

Conversation

@ginxx009

@ginxx009 ginxx009 commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Mic/interviewer questions still replace the board.

After an answer is on screen, type a follow-up (why?, go deeper) and hit Go / Assist. The original answer stays. The why is appended under it.

Load briefing on setup fills the Principal Engineer hiring-manager playbook (agentic coding first).

28 unit tests. Does not push to main.

Go/Assist after an answer appends instead of replacing. Mic still
starts a new interviewer question. Load briefing fills the Principal
Engineer hiring-manager playbook. 28 tests green.
@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 90ce3281-d335-4d9c-bdad-6adbc8daa83b


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

macOS Speech now gets resume/job vocabulary so 'agentic' is less
likely to become 'agency'. Skip filler like 'me too'. Prompt must
infer messy ASR and must not invent percents.
Do not invent Copilot years or impact if they are not on the resume.
HARD FACTS from that box override a thin resume. Extra ASR fixes for
'agents including' and 'older cars are' (Cursor).
Architecture questions must come from the resume. Agentic facts stay
for agentic/tool questions only. ASR: prodded→product.
Ownership and scale answers must come from that list, not Dynaskills.
…ation recap

6-9 spoken sentences. Agentic must be one loop with a gate. Architecture
must drop an alternative. Check-in questions stay short.
Principal answers must name a dropped alternative, a business outcome
from facts, and how a standard actually spread on the team.
Map TSEKMO EventBridge/S3/RDS as the data path. Do not invent a
PHP-to-Node warehouse story.
ETO still maps to ETL. Do not open data answers with I don't have experience.
Lead data answers with Accenture Kafka then TSEKMO, never I don't have ETL.
Do not pitch generic microservices. Rank debt by blast radius and delivery drag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant