Google Gemini Mastery — Search, Workspace and Multimodal Work

Week 1 — meet the tool, get an account, and learn the screen before you learn the prompting.

1. Meet Gemini — what it is and who makes it

   Gemini is Google's assistant wired into Search, Gmail, Docs and Android. It is at its best at answering a question that needs a current fact, because it can search while it answers. It is at its weakest when you want a strong opinion — it summarises the internet rather than arguing — and knowing both halves is what separates somebody who uses it well from somebody who trusts it blindly.

   The lesson

   Gemini is a assistant wired into Search, Gmail, Docs and Android made by Google. The models behind it are the Gemini family, from a fast version to a large reasoning one, with a very large context window. None of that matters on its own — what matters is that you know what kind of worker you have hired. At answering a question that needs a current fact, because it can search while it answers is the job you hand it. When you want a strong opinion — it summarises the internet rather than arguing is the job you keep.

   Most people come to a course like this expecting a list of magic words. There is no such list. What there is, is a tool that produces an answer with sources attached, which is either its greatest strength or a way to be confidently wrong five times at once, and produces it at a speed no human matches — which means the skill is not in writing the prompt, it is in knowing what a good answer looks like so you can tell the difference.

   Here is the first thing to try, worded the way you will word things for the rest of the course:

   PromptCopy

   Search the web and tell me what entry-level data analyst roles in India asked for most in the last three months. Give me the sources, and mark anything you could not confirm.

   Read the answer twice. The first read is for the content; the second is for the shape — did it answer the question you asked, or the question it found easiest? That second read is the habit this whole course is built on.

   Example A grounded answer you can open and check is worth more than a confident list you cannot.

   Practice Open Gemini, ask it the one question you would normally put to a search engine about your own field, and write down two things: whether the answer was right, and whether it would have taken you longer to find it yourself.

2. Signing in: what is free, what is paid, and what you actually need

   You do not need the paid plan to finish this course. Start on the free tier — the free tier in the Gemini app and in the Google account you already have covers most of this course. Upgrade only when you hit a wall you can name: a longer file, a newer model, or a rate limit you keep meeting.

   The lesson

   Every one of these tools has a free tier that is good enough to learn on and a paid tier that removes a limit. the paid Google One AI plan raises the limits and adds the assistant to more of the Workspace apps. The mistake is buying the paid plan in week one, before you know which limit you hit — you end up paying to remove ceilings you were never going to touch.

   Work out your own honest usage first. How many questions a day do you actually ask? How big are the files you upload? Do you need the newest model, or the fast one? For revision, for drafting, for coursework, the answer is usually the free tier.

   If your college or workplace provides an account, use it: a Google Workspace plan with Gemini included is how most people in a job get access, and asking your placement cell whether one exists costs nothing.

   Example Summarising a two-hour lecture video you were sent, and asking follow-up questions about it, costs nothing and saves an afternoon.

   Practice Create the account, find the plan page, and write down in one line which limit you would hit first in your own week. It is usually a message cap or a file-size cap, not the model.

3. The screen: where every control lives

   A tour of the interface you will live in — one box in the Gemini app, and a "help me write" button that appears inside Gmail, Docs, Sheets and Slides. Every panel has a reason to exist, and half of them are the difference between a chat and a system.

   The lesson

   The interface of Gemini is one box in the Gemini app, and a "help me write" button that appears inside Gmail, Docs, Sheets and Slides. That sentence is worth slowing down on, because the single biggest cause of bad output is not a bad prompt — it is a good prompt typed into the wrong place.

   The history list is your memory of what worked. Name your conversations. The temporary or private mode is for anything you would not want in an account's history. The settings panel holds the personal instructions that apply to everything, which is where your context belongs rather than repeated at the top of every message.

   Do this once, properly: use the in-document help once in Docs and once in Sheets, because those two are different skills. It takes fifteen minutes and saves you those fifteen minutes every week after.

   Example The button inside Docs is the underrated part: the assistant appears where the work already is, so you stop copying text between two windows.

   Practice Spend fifteen minutes doing nothing but clicking. Open every panel, rename one conversation, and save one setting you will want again. Fluency with the screen is what stops you re-explaining yourself every session.

Week 2 — how Gemini reads text, the four-part prompt, your own work, and what to do when the answer is wrong.

1. How Gemini reads what you type

   Context, instructions and roles. Gemini can search the web while answering, and can also read a document you attach — but it will not always tell you which of the two it did. Understanding what the model can see — and what it has already forgotten — explains almost every disappointing answer you will get.

   The lesson

   Gemini can search the web while answering, and can also read a document you attach — but it will not always tell you which of the two it did. This is the machinery. A model does not remember your last conversation the way a person does; it is handed text and asked to continue it well. Everything you want it to know has to be in that text, in the same window.

   There is a difference between a system instruction — the standing context, set once — and a message, which is this request. Put your standing context in the standing place. "I am a final-year mechanical engineering student applying for data roles" belongs in your profile, not typed again at the start of every chat.

   And there is a hard limit. When a conversation gets long enough, the earliest turns fall out of view. Symptoms: it contradicts an instruction you gave ten messages ago, or forgets the file you uploaded. The fix is a new conversation with a written summary of where you got to, not a longer argument.

   Example Ask "what is the current fee for X" and you may get a number from search or a guess from memory. Ask "search the web and give me the page you used" and you get the difference for free.

   Practice Ask the same question twice: once on its own, once after a short paragraph of setup about who you are and what you need. Compare the two answers and write down the difference. That gap is the thing you are learning to control.

2. The four-part prompt: role, task, context, format

   Almost every good prompt has four parts: who the model should be, what it must do, the facts it must use, and the shape of the answer you want. Leave out the fourth and you get an essay when you wanted a table.

   The lesson

   Write the four parts as four lines, in this order. ROLE: who it should answer as. TASK: the single thing you want done, as an instruction, not a wish. CONTEXT: the facts, pasted, not referred to. FORMAT: the exact shape of the answer — "a table with three columns", "five bullets, no more than twelve words each".

   FORMAT is the part everybody skips and the part that saves the most time. An answer you have to restructure by hand was not really an answer. Ask for the shape you are going to use: if it is going into a slide, ask for slide bullets; if it is going into a spreadsheet, ask for rows.

   Here is the same request done both ways — first as people usually write it, then in four parts:

   PromptCopy

   Weak:  tell me about data analyst jobs
   
   Strong:
   ROLE:    A hiring manager for entry-level analytics roles in India.
   TASK:    List what you screen for in a fresher's first 30 seconds.
   CONTEXT: I am a 2026 B.Com graduate with Excel, basic SQL and one
            dashboard project. No internship yet.
   FORMAT:  A table: skill | what a fresher shows | what most get wrong.
            Five rows maximum. No introduction.

   The second prompt is not longer because long is good. It is longer because it contains four things the model cannot guess, and the guess is where the useless answer came from.

   Example "Answer with the source and the date it was published, or say you could not find one" is the single most useful sentence to add to any factual question here.

   Practice Take a task you did last week without AI and write the prompt in four labelled lines. Then run it, and rewrite only the part that failed — not the whole prompt.

3. Gemini for the work you actually have

   Assignments, revision, email, applications, meeting notes. A pasted video link becomes structured revision notes with timestamps, and a rough email becomes one you would send to a professor. The test of a tool is whether it removes an hour from your week, not whether the demo looked clever.

   The lesson

   The highest-value use of Gemini for a student or a fresher is not writing essays. It is compression: turning a 40-page chapter into the six things you actually have to remember, turning a messy set of notes into a revision sheet, turning a job description into a list of what to prove.

   The second highest is structure: given a blank page, ask for three possible outlines and pick one. Being stuck is usually a problem of options, not of effort.

   Here is a prompt worth keeping verbatim — it is the one that turns a document into something you can study:

   PromptCopy

   Here is a lecture video: [link]
   
   Give me:
   1. Structured notes in 8-10 bullets, each with the timestamp where it is said.
   2. Five questions an examiner would set from this video.
   3. The two parts most students misunderstand, and why.
   
   Everything must come from the video. Say so if something is not covered.

   Notice the last line. Asking for the gaps is asking the tool to mark its own work, and it is the single most useful line you can add to a study prompt: the material it could not summarise is the material you have not understood yet.

   Example Give it a YouTube lecture link and ask for notes with timestamps, then questions it would set from the video.

   Practice Pick the one task you repeat every week — the one that is boring rather than hard — and rebuild it in Gemini today. Time it. Then keep the prompt that worked, saved and named.

4. When the answer is wrong: iterate instead of restarting

   A bad answer is information. Its failure mode is confident summarising: a neat answer assembled from sources that partly disagree, with no sign that they disagreed. Keep the conversation, name the fault, and correct one thing at a time — restarting from scratch throws away everything the model has already got right.

   The lesson

   There are four things that usually went wrong, and each has a different fix. It answered a different question — restate the TASK as one sentence. It made things up — supply the facts yourself and say "use only these". It wrote too much — ask for the length first. It sounded like a machine — ask it to rewrite for one specific reader and cut every third word.

   Say the fault out loud, in the message. "This is too long for a WhatsApp message and it sounds like a brochure." A model cannot fix a problem you have not named, and naming the problem is also how you find out what you actually wanted.

   Follow-ups that work: "shorter", "only the parts that are true for a fresher", "rewrite the second sentence three ways", "what would you have to check before I send this?". That last one is worth using before anything goes out with your name on it.

   Example Ask "do your sources agree with each other? where do they differ?" and the tidy answer usually turns into a more honest one.

   Practice Take the worst answer you have received this week and correct it in three follow-up messages without retyping the original prompt. Notice how much faster it converges.

Week 3 — documents and tables, Search grounding and YouTube understanding, the API, and one boring task automated.

1. Files, tables and long documents

   Uploading a PDF, a spreadsheet or a screenshot and asking questions about it: Gemini reads PDFs, images, audio and video, and can work inside a Google Doc or Sheet rather than pasting text in. This is where these tools stop being a chat and start being work, and where the failure modes are worth knowing.

   The lesson

   Gemini reads PDFs, images, audio and video, and can work inside a Google Doc or Sheet rather than pasting text in. The two failures to expect are the ones nobody warns you about: a long document is summarised as it is read, so a detail on page 60 can be missed; and a table with merged cells or a scanned page is likely to be read wrongly.

   So the working method is: ask narrow questions, and ask the tool to quote the line it is answering from. "From the attached file only, what does clause 4.2 let me do? Quote the sentence." If it cannot quote it, it did not read it.

   For a spreadsheet, ask for the formula and an explanation instead of the computed column — describe the columns in words and ask for the formula plus one line on each part — then you can fix it yourself next month when the columns change.

   Example Upload a photo of a printed timetable, a handwritten page, or a diagram you cannot read, and ask it to make it useful — this is the multimodal part that actually saves students time.

   Practice Upload one real document you already own — a syllabus, a marksheet, a project report — and ask three questions whose answers you already know. When it gets one wrong, read the passage it quoted before you blame the file.

2. Search grounding and YouTube understanding — Gemini's own feature

   Two features, one habit: Gemini will search while it answers and show where the answer came from, and it will watch a video you give it and answer questions about what was actually said. Between them, most of the "I need to check something quickly" work moves here.

   The lesson

   This is where Gemini earns its place next to the other assistants. A model that cannot look anything up is answering from memory; a model that searches can be checked. For a student doing research, that checkability is the entire feature.

   Ask the question, then ask for the source and the date. Open the source. If there is no source, treat the answer as a draft, not a fact. For video, give the link and ask for timestamps so you can jump to the exact minute rather than trusting a summary of a summary.

   Here is the shape of it, in the form you will actually use:

   PromptCopy

   Search the web for the current eligibility rules for [scheme or exam],
   as they stand today.
   
   For each rule:
   - state it in one line
   - give the source URL and the date that page was published
   - mark anything you could not confirm as UNCONFIRMED
   
   Do not fill gaps with what is usually true.

   The mistake is reading the summary and never opening a source. A grounded answer with three links you did not click is not more reliable than a memory-based answer; it just looks more reliable.

   Example A three-hour recorded revision session becomes twelve timestamped bullets, and a factual question comes back with the page it came from so you can open it.

   Practice Take one question you would have searched for, ask it here with "give me the source and the date", and open the source. Do that five times and you will know when to trust it.

3. The Gemini API and your first script

   Google serves Gemini through an API with a generous free tier for experimentation, native handling of images and audio, and an SDK for Python and Node. You do not need this to finish the course, and you do not need it for a fresher job either — but an afternoon here is what turns "I have used Gemini" into "I have built with it", which is a different sentence in an interview.

   The lesson

   Google serves Gemini through an API with a generous free tier for experimentation, native handling of images and audio, and an SDK for Python and Node. The idea is simple: the same model you have been chatting with also answers a web request, so you can put it inside a script, a spreadsheet or a page. A key identifies you; a request sends the text; a response comes back as data.

   The reason to try it once, even if you never build anything: it makes the chat version less mysterious. You see that the whole conversation is text in and text out, that your instructions are literally lines of a request, and that "the model" is one parameter among several.

   A first call looks like this:

   PythonCopy

   from google import genai
   
   client = genai.Client()      # reads GEMINI_API_KEY
   
   r = client.models.generate_content(
       model="gemini-2.5-flash",
       contents="Explain what a data analyst does in three concrete sentences.",
   )
   
   print(r.text)

   The mistake is assuming the free quota is unlimited. It is metered per day, and a loop over 500 images will stop halfway — handle the error and write down where you got to.

   Example A script that photographs pages of a textbook and returns the text is a two-hour project with this API, and it is the kind of thing that makes a portfolio entry look real.

   Practice Get a key, run one request that works, and change one word in it to see the answer change. That is the whole of the first afternoon.

4. Automate one boring task with Gemini

   Automation is not about building a system. It is about doing one repetitive job the same way every time, in less time than last time, and being able to do it again next month.

   The lesson

   Pick the task by how often it happens, not by how impressive it would be. A weekly report you can half-generate beats a clever pipeline you build once and never open again.

   Turning a folder of screenshots into text, or turning any new video into the same notes format every week.. Whatever you choose, write the steps back out in plain English afterwards — "Step 1, open the sheet, Step 2, paste the names —" because the written steps are what you follow when the tool changes next quarter.

   And keep a copy of the prompt next to the task. A prompt that lives only in your chat history is a prompt you will rewrite from scratch in March.

   Example A weekly routine: every lecture recording gets the same notes prompt, and the output lands in the same Drive folder. The value is that the format never changes.

   Practice Name the task you repeat most often that involves typing, then write the prompt for it and run it three weeks in a row from the same saved place. Three runs is the point at which you know whether it is genuinely automated.

Week 4 — a finished portfolio project, the privacy rules, the limits, and the Google certification paths.

1. Build the portfolio project: a revision system built from recorded lectures

   Take one real subject and build a folder of timestamped notes from its recorded lectures, then an index page that links each topic to the minute it is explained. It is the thing you will talk about in the interview, so it has to be small enough to finish in a fortnight and concrete enough to show a person in one minute.

   The lesson

   Take one real subject and build a folder of timestamped notes from its recorded lectures, then an index page that links each topic to the minute it is explained. Finish it before you start the next one. A half-built idea shows nothing; a small finished thing shows that you can finish.

   Use the tool as a collaborator, not an author: ask it for a plan, a critique and a checklist, and write the work yourself. In the interview the questions will be about the decisions — why this, why not that — and only the work you did yourself has answers.

   Write one paragraph beside the project: what problem it solves, what you used, and what you would do differently next time. That paragraph is the interview.

   Example The finished artefact is one page with twenty topic links, each opening the exact minute of a video. It is genuinely useful and takes a fortnight.

   Practice Show it to one classmate and watch where they get lost. That is the user-testing habit an interviewer will ask about.

2. Ethics, privacy and what never to paste

   These tools send what you type to somebody else's computer and keep it in a history. Never paste passwords, government ID numbers, bank or card details, medical records, or another person's private data — and never paste a company's confidential document.

   The lesson

   There is no version of this tool where your text stays on your laptop. Everything you type is sent to a server, kept in a history you can usually see, and may be reviewed or used to improve the product depending on the plan.

   Check what the assistant is allowed to read. An assistant with access to your Drive can quote a document you forgot was there, and a screenshot pasted into a chat may include a name, an address or a bank detail in the corner.

   The practical rule for a fresher: replace the real thing with a stand-in. "Client A", "my friend's phone number", "the amount in the offer letter". The tool rarely needs the real value to do the work, and the stand-in costs you nothing.

   And the professional rule: never let an assistant write into a shared document that other people depend on without reading every line first. If your employer has an approved plan or a policy, that policy is the answer, not your judgement about how sensitive a file really is.

   Example Your Google account links this assistant to your mail, files and calendar, which is exactly why the sharing settings matter more here than anywhere else.

   Practice Go through your last five conversations and delete anything containing a real phone number, a client name, or a document you did not write. If you cannot find the delete button, that is the lesson.

3. Limits, hallucinations and how to check

   These tools predict plausible text. Search grounding makes it right more often, and also makes it harder to tell when it is wrong, because the formatting always looks sourced That is a mechanism, not a moral failing — and the habit it demands is the habit of asking "where did this come from?" out loud, every time, before you use an answer.

   The lesson

   A model does not look things up unless it has been given a way to look things up, and even then it can attach a real number to the wrong claim. Search grounding makes it right more often, and also makes it harder to tell when it is wrong, because the formatting always looks sourced

   So the rule is: numbers, dates, names, citations and legal or medical claims get checked in a primary source before they leave your hands. Everything else — drafts, structure, explanations, practice — is fair game.

   Three questions to ask before you trust an answer. Where did this come from? What would make it false? Who is the original source, and can I open it? If the third one has no answer, you have writing material, not facts.

   Treat every number with a link as unverified until you have read the page it came from — including the ones that look official.

   Example Ask for a current statistic with a source, then open the page and read the sentence around the number. The number is often real and the claim built on it is not.

   Practice Ask for one statistic with its source, then open the source. Sometimes it exists. Sometimes the citation is invented, and the number is close enough to a real one to be dangerous. Either way you will remember the exercise.

4. Get certified: the official Google paths

   A Way2Fresher certificate for this course is free and lives on this site. Beyond it, Google publishes its own learning and certification material — and the rail on this course page links to it.

   The lesson

   There are two things called a certificate and they are not the same. The one this site issues records that you finished a structured course and built the project at the end of it — it is free, and it is yours to print. The ones Google issues record that you passed their own material.

   Google publishes free courses and skill badges through Google Cloud Skills Boost, plus its own AI learning paths. The skill badges are the closest thing to a recognised certificate, and the introductory ones are free.

   Get both, in that order. The project is what an interviewer asks about; the certificate is what gets past a filter that looks for keywords. The links to the official paths are in the rail beside this lesson, each labelled with who issues it.

   And put the work on the certificate, not the other way round: a certificate with no project behind it is a line on a resume, and it lasts exactly until the first technical question.

   Example Ask it to turn a job description and your resume into ten questions you would struggle with, then answer them out loud with the timer running.

   Practice Finish every lesson here, take your Way2Fresher certificate, then open one official path and work through it with the project you have already built. Being certified in the tool you can already use is a small additional step.