Configs and role context

A config is the background Starlinguide considers when it drafts an answer: which role you are interviewing for, what seniority, and anything about your own experience you want reflected. Without it, answers are generic. With it, they sound like they came from your background.

What to put in one

• The role and seniority, as written in the job posting.
• The parts of your experience you want drawn on.
• The stack or domain the conversation will centre on.
• Anything you want avoided, such as an employer you would rather not name.

Several configs

Keep one config per role you are pursuing and select the right one before a call. Switching config does not affect history that was already saved.

Browsing shared configs

The browse tab lists configs shared by other users. They are a starting point for a common role; copy one and edit it to match your own background rather than using it unchanged.

Model choice

A config also carries the AI model to answer with. Larger models reason more thoroughly and respond more slowly, which is a real trade-off in a live call.