Sofia Marchetti

Act as an experienced interviewer and run a mock interview with me.

Role I am interviewing for: {{role}}
Company or type of company: {{company:not specified}}
Interview type: {{interview_type:a mix of behavioral and role-specific questions}}
My background, in brief: {{background}}
Number of questions: {{count:6}}

How to run it:
1. Ask ONE question, then stop and wait for my answer. Never ask the next question in the same message.
2. After I answer, give feedback in this format:
   - What worked: one or two specific things.
   - What to improve: the most important one or two things. Be direct. For example: no concrete example, too long, did not answer what was asked, no result given, said "we" throughout so my own contribution was unclear.
   - A stronger version: show how my own answer could be restructured, using only the facts I gave. Do not invent experience for me.
3. Then ask the next question.

Question mix:
- Start with an easy opener.
- Include behavioral questions ("Tell me about a time when...") and expect a clear situation, what I did, and the result.
- Include questions specific to the role and its seniority.
- Include one hard one: a weakness, a failure, a conflict, or a gap in my background.
- Ask a follow-up when my answer is vague, the way a real interviewer would.

At the end, give me:
- An overall assessment, honestly: would this performance likely move me to the next round?
- My two biggest strengths and my two most important things to fix.
- Three questions I should ask the interviewer for this role.

Start by greeting me briefly and asking the first question.

Rewrite the email below so the reader understands it on the first read and knows exactly what I need from them.

Who it is going to: {{recipient}}
What I want to happen after they read it: {{goal}}
Tone: {{tone:friendly and professional}}

How to rewrite it:
- Open with the request or the main point. Background comes after, and only what the reader needs.
- One request per email if possible. If there are several, number them.
- Give any date or deadline as a specific day, not "soon" or "ASAP".
- Short paragraphs. Cut greetings that say nothing, apologies I do not owe, and anything repeated.
- Keep it sounding like me. Do not make it more formal than the original.
- Do not add facts, promises, or dates that are not in my draft. If something essential is missing, list it under "Missing" instead of inventing it.

Return:
1. A subject line under 60 characters.
2. The rewritten email.
3. "What I changed", in two or three bullets.

My draft:
{{draft}}

Write a spreadsheet formula for me.

Spreadsheet program: {{app:Google Sheets}}
What I want the formula to do: {{goal}}
How my data is laid out (which columns hold what, which row the data starts on, the sheet name if it matters): {{layout}}
A few example rows, if I have them: {{examples:none provided}}

Give me:
1. The formula, ready to paste, in a code block.
2. The cell to put it in, and whether to drag it down or whether it fills by itself.
3. An explanation of each part from the inside out, in plain words.
4. What it returns for my example rows, or for a small example you make up if I gave none.
5. What will break it: blank cells, text stored as numbers, extra spaces, merged cells, dates stored as text. Give the fix for each one that applies to my case.
6. A simpler or more robust alternative, if there is one. For example, a lookup that does not break when a column is inserted.

Rules:
- Use functions that exist in the program I named. If the best function is only in newer versions, say so and give a fallback.
- Use my real column letters and sheet names, not placeholders.
- Assume my regional settings use {{separator:commas}} to separate arguments.
- If my description could mean two different things, show both formulas and explain the difference.
- If this would be better done with a pivot table, a filter, or a helper column than with one giant formula, tell me.

Help me plan a project.

Project: {{project}}
What "done" looks like: {{definition_of_done}}
Deadline: {{deadline:flexible}}
Who is working on it and how much time they have: {{team:just me, part-time}}
Budget or other limits: {{constraints:none}}

Produce:

1. Scope: what is included and, just as important, what is not. List any assumptions you are making.

2. Milestones: 3 to 6 points where something real is finished and can be shown or checked. Each one needs a clear test for "this is done".

3. Tasks under each milestone:
   - Concrete and small enough to finish in a day or two.
   - An estimate for each, in hours or days.
   - What it depends on.
   - Who does it, if there is more than one person.

4. Timeline: put the milestones on a calendar, working from the estimates and the time available. Identify the critical path, meaning the tasks where a delay moves the end date.

5. Risks: the 5 things most likely to delay or sink this. For each: how likely, how bad, the early warning sign, and what to do now to reduce it.

6. First week: exactly what to do in the first five working days.

7. Decisions needed: anything that has to be decided or found out before work can properly start.

Rules:
- Be realistic. Estimates should include testing, review, and waiting on other people. Add a buffer and say how big it is.
- If the deadline is not achievable with the time and people available, say so, and show what would need to change: scope, deadline, or resources.
- Put the riskiest or most uncertain work early, so problems show up while there is still time.
- If there is something I need to tell you before you can plan this properly, ask me first.

Write a product description.

Product: {{product}}
Who buys it: {{customer}}
Where it will appear: {{channel:an online store product page}}
Brand voice: {{voice:clear, warm, and direct}}
Length: {{length:120 to 160 words, plus bullets}}

Structure:
1. Headline: what it is and the main reason someone wants it, in under 10 words.
2. Opening: one or two sentences about the buyer's situation or problem, in the words they would use.
3. Body: the two or three benefits that matter most to this customer. Tie each one to the feature that delivers it. For example: "The 20-hour battery gets you through a long-haul flight and back."
4. Bullets: 4 to 6 key specifications or included items, for people who scan.
5. A closing line that removes a doubt, such as the warranty, the return policy, or who it suits.

Rules:
- Use only the facts I give you. Do not invent specifications, materials, certifications, awards, reviews, or guarantees.
- Be specific instead of using superlatives. No "best-in-class", "revolutionary", "game-changing", "premium quality", or "elevate".
- Make no health, safety, or environmental claims unless I supplied them.
- Write the way someone knowledgeable would describe it to a friend.

Give me two versions with different opening angles, and say which kind of buyer each one suits.

Product details and specifications:
{{details}}

Build me a study plan.

What I am learning or preparing for: {{goal}}
Deadline or exam date: {{deadline}}
Hours I can realistically study per week: {{hours_per_week}}
Where I am starting from: {{current_level}}
Materials I have (books, courses, past papers): {{materials:none yet}}
How I learn best, and what has not worked before: {{preferences:not sure}}

Build the plan like this:
1. Break the subject into its main topics. Mark which carry the most weight for my goal and which depend on others, so I learn them in the right order.
2. Check the numbers honestly: is the time I have enough? If not, say so and tell me what to prioritize and what to drop.
3. Lay out a week-by-week schedule. For each week: the topics, what to do (read, practice, review), and what I should be able to do by the end of it.
4. Build in what makes learning stick:
   - Practice that makes me retrieve things from memory, such as problems, self-testing, or explaining aloud. This should take more time than re-reading.
   - Spaced review of earlier topics, scheduled in, not left to chance.
   - Full practice tests or realistic projects in the final stretch.
5. Leave one catch-up session per week unassigned. Plans without slack fail.
6. Add a checkpoint every two weeks: a specific way to test myself, and what to change if I am behind.

Then give me:
- A typical single study session, minute by minute.
- The three most common ways people fail at this particular goal, and how this plan avoids them.

Rules:
- Size everything to the hours I gave. Do not assume I will find more.
- Be specific: "do 20 practice questions on topic X", not "review topic X".
- If you recommend resources, describe the type to look for. Do not invent specific titles or links.

Proofread the text below. Fix errors; do not restyle it.

English variant: {{variant:keep whatever the text already uses}}

Fix:
- Spelling, grammar, punctuation, and capitalization.
- Words that are clearly the wrong word (their/there, affect/effect, and so on).
- Inconsistencies: a name spelled two ways, mixed tenses, mixed date or number formats.

Do not:
- Change my word choices, sentence rhythm, or tone because you would have written it differently.
- Shorten, expand, or reorder anything.
- "Fix" things that are deliberate, such as fragments used for effect or informal phrasing.

If a sentence is genuinely unclear or could be read two ways, leave it as it is and list it under "Unclear", with what you think I meant.

Return:
1. The corrected text.
2. A table of changes: original, corrected, reason.
3. "Unclear", if there is anything.

Text:
{{text}}