Setting up context in Get-Offer
How to set up your role, stack, language and answer format so hints stay closer to your experience.
What a context is
A context is a behavior profile for the assistant. It stores your role, technologies, answer language, resume, additional data and hint format.
Use one context per task. An HR interview, live coding and system design each need a different focus.
- HR: short first-person answers, STAR/PAR stories, facts from your experience.
- Technical interview: stack, code examples, constraints and trade-offs.
- System Design: requirements, components, data, reliability, scaling and questions for the interviewer.
- Interview in English: the answer language and the terms you want to see in hints.
Context fields
Here is what each context field is for. Fill in only what will actually help in a specific interview.
| Field | What to write |
|---|---|
| Name | A short preset name: Senior React, Python interview, HR English. |
| Role | The position and level you're interviewing for. |
| Answer language | auto, Russian, English or another language for a specific meeting. |
| Resume | Your experience, projects and achievements that can be used in answers. |
| Technologies | The stack that should appear in explanations and examples. |
| Additional data | Facts about the company, the job, constraints, answer style and things to avoid. |
| Answer length | Short, medium or extended hint format. |
| Answer format | Terms, examples, STAR/PAR or your own template. |
| Transcript settings | Language, keywords and speech recognition format. |
Example for a Python backend role
A practice example: replace the experience and achievements with your own facts. Technical interview has a template you can copy; topics to review are in the question catalog.
| Field | Value |
|---|---|
| Role | Middle Python backend developer |
| Technologies | Python 3.12, FastAPI, PostgreSQL, Redis, Docker |
| Resume | Three years of API development. Built a background job queue and integration tests. Don't add unconfirmed achievements. |
| Answer language | English |
| Length and format | Medium; terms and examples |
| Additional data | Give a short answer first, then an example and the constraints. If there isn't enough data, suggest a clarifying question. |
Recommendations
A good context isn't a long one. Its job is to give the assistant a frame so the answers sound like you, not like an article from the internet.
- Create a separate context for each important job opening.
- Before the interview, remove irrelevant technologies and outdated facts.
- For behavioral questions, add 3-5 stories with results and metrics.
- For live coding, add the language, the framework and what's expected when you explain complexity.
- After the interview, update the context for the questions where your answers were weaker.