Most "how it works" pages stop at a marketing diagram. This one walks you through a real 45-minute interview with GirGit AI — from the moment you click the installer to the moment you close the meeting and clear your session.
If you have ever wondered *what does the overlay actually feel like in the third minute of a behavioral round*, this is for you.
Step 1 — Install and sign up (under two minutes)
Head to girgit-ai.com and grab the installer from the #download section. Windows 10/11 (64-bit) is fully supported; macOS 10.15+ is in public beta.
- Run the installer — it is small, no GPU required, no admin gymnastics.
- Sign up with email. Your first 10 minutes are free — you can run a complete trial interview without paying.
- Top up later via UPI, debit, or credit card. Most candidates start with ₹150 (~$1.10), enough for a full 30-min round.
Step 2 — Upload resume, paste the JD
This is the single most important step and it is the one most people rush. GirGit's answer quality depends on context.
- Upload your resume as a PDF. Use the same one you sent the recruiter — bullet phrasing matters.
- Paste the full job description into the JD box, including the "responsibilities" and "what we look for" sections. Do not paraphrase.
- Optionally add a short note like *"focus on backend, deprioritize the React stuff"* if the JD lists everything but the role is narrower.
GirGit will now anchor every answer in your actual experience — your old projects, your tech stack, your scale numbers — instead of producing a generic LLM monologue.
Step 3 — Start the meeting and the overlay
Open Zoom, Microsoft Teams, Google Meet, Webex — whatever your interviewer uses. Click Start Listening in GirGit.
The overlay is a small, draggable panel that floats above the meeting window. It has three things you actually care about.
- A status badge showing Listening → Generating → Answer ready.
- The answer pane — structured points, code blocks, or a short narrative depending on the question type.
- A transcript pane so you can re-read what the interviewer just asked if your brain skipped over it.
When the interviewer says "please share your screen," the overlay stays visible to *you* but becomes invisible in the shared video. This is the property no other tool gets reliably right; GirGit is built around it.
Step 4 — The pipeline, observed live
Here is what the 0.8-second pipeline actually looks like in practice during a typical question.
| Time | What happens | What you see |
|---|---|---|
| 0.0s | Interviewer finishes asking the question | Status: Listening |
| 0.2s | Transcript locks, query is built from resume + JD + question | Status: Generating |
| 0.6s | Model returns a structured response | First bullets begin streaming |
| 0.8s | Answer is fully ready | Status: Answer ready |
By the time you finish your "let me think about that for a second" filler line, the answer is already on screen.
Step 5 — Behavioral rounds
Behavioral questions are where GirGit's resume context shines. Ask GirGit *"tell me about a time you handled a conflict"* and a generic LLM gives you a generic STAR template. GirGit pulls a specific project from your actual resume, references the team size you listed, and fills in the structure with your real history.
- Answers default to STAR format (Situation, Task, Action, Result) for behavioral questions.
- Numbers from your resume (latency cuts, user counts, cost savings) are surfaced when relevant.
- If the JD emphasizes leadership or collaboration, GirGit weights those framings automatically.
Step 6 — Coding rounds
When the interviewer pastes a problem in the chat or shares a CodePair / HackerRank link, GirGit's coding mode kicks in. Supported languages include Python, Java, C++, JavaScript, Go, Kotlin, Swift, TypeScript and more.
- Returns a complete working solution, not a hint.
- Adds time and space complexity notes inline.
- Calls out edge cases (empty input, overflow, off-by-one) before you hit them.
- For system design, gives a layered breakdown: API, data model, caching, scaling.
For online assessments where AI alone is risky, you can book the OA / Coding Round Help option from the on-site modal — a real engineer remote-into your screen and helps you solve it live. This is unique to GirGit.
Step 7 — After the interview
When the call ends, you simply close GirGit. The billing meter stops the second you stop the session — no rounding up, no monthly drip.
- Session transcripts are kept only as long as you want them — clear them from the dashboard.
- Your remaining balance stays on your account; there is no expiry because there is no subscription clock.
- If you have a follow-up round, just start a new session. Resume and JD stay loaded.
Things candidates ask before their first session
- Will the interviewer hear me typing? No — GirGit is silent and uses no audio output.
- Will it pop up if I share my whole screen? No — the overlay is hidden from screen-capture APIs across Zoom, Teams, Meet, Webex, and BlueJeans.
- Can I read straight off it? Yes, but you should *paraphrase*. The whole point is to sound like you, not a teleprompter.
- What if the audio fails? Use the troubleshooting guide; usually it is a Windows audio routing toggle that takes 20 seconds.
The best interview tool is the one that disappears the moment you stop needing it — and shows up exactly when you do.