Perplexity Mastery — Research With Sources You Can Check

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

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

   Perplexity is Perplexity AI's answer engine that searches first and answers second. It is at its best at a question whose answer is somewhere on the web and needs a citation. It is at its weakest at anything where the sources disagree and somebody has to decide — it will summarise the disagreement rather than resolve it — and knowing both halves is what separates somebody who uses it well from somebody who trusts it blindly.

   The lesson

   Perplexity is a answer engine that searches first and answers second made by Perplexity AI. The models behind it are a choice of frontier models behind a search-first interface, plus its own research modes. None of that matters on its own — what matters is that you know what kind of worker you have hired. At a question whose answer is somewhere on the web and needs a citation is the job you hand it. At anything where the sources disagree and somebody has to decide — it will summarise the disagreement rather than resolve it 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 a short answer with numbered citations, which is a different product from a chat, 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

   Research the entry-level data analyst market in India right now. Give me the three things employers ask for most, the three things they complain freshers are missing, and the source for each one.

   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 Two lists with sources behind them — one you can act on this week, and one you can bring to an interview as an observation.

   Practice Open Perplexity, 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 gives unlimited basic searches with a daily allowance of the better modes. 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 plan raises the daily allowance on the deeper research modes and adds file uploads to the mix. 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 team plan with shared collections is how most people in a job get access, and asking your placement cell whether one exists costs nothing.

   Example For a company you are interviewing at, five free searches will get you further than an hour of reading their website: funding, leadership, competitors, recent news, and what employees say.

   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 — a search box that returns a short answer with numbered sources, followed by the sources themselves, and a mode selector for depth. 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 Perplexity is a search box that returns a short answer with numbered sources, followed by the sources themselves, and a mode selector for depth. 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: ask one question in each mode and compare the number of sources each one used — that number is what the mode actually changes. It takes fifteen minutes and saves you those fifteen minutes every week after.

   Example The mode selector is the important control: a quick search, a deeper research pass, and a reason step by step are three different jobs.

   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 Perplexity reads text, the four-part prompt, your own work, and what to do when the answer is wrong.

1. How Perplexity reads what you type

   Context, instructions and roles. It answers from pages it has just read, so what it knows is limited to what the search returned, and its citations are the whole evidence. Understanding what the model can see — and what it has already forgotten — explains almost every disappointing answer you will get.

   The lesson

   It answers from pages it has just read, so what it knows is limited to what the search returned, and its citations are the whole evidence. 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 about something with almost no web coverage and it will tell you it found little, which is more honest than a chat window inventing an answer from memory.

   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 "Only use sources published in the last 12 months" changes the answer completely on a fast-moving topic, because recency is a filter it can actually apply.

   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. Perplexity for the work you actually have

   Assignments, revision, email, applications, meeting notes. Forty minutes of tab-hopping before an interview becomes a two-page brief with every claim linked. 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 Perplexity 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

   Research [company]. I have an interview for [role] in one week.
   
   Give me:
   1. What the company actually does, in three lines, with a source.
   2. News from the last 12 months, newest first, each with a date and a link.
   3. Three competitors and how this company differs.
   4. Three things an interviewer there would expect me to know.
   5. Anything negative or risky that has been reported.
   
   Cite every claim. Mark anything you could not verify as UNVERIFIED.

   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 Research a company you are interviewing at and produce a brief with funding, competitors, recent news and the risks — every line sourced.

   Practice Pick the one task you repeat every week — the one that is boring rather than hard — and rebuild it in Perplexity 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 is a confident summary of sources that disagree, presented as a single answer. 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 Two salary reports give different numbers. Ask "where do these disagree, and why?" and you usually get the honest version: different geographies, different seniority, different years.

   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, Citations, focus modes and collections, 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: It reads uploaded PDFs and documents, and its collections keep the sources of a research thread together so you can return to them. This is where these tools stop being a chat and start being work, and where the failure modes are worth knowing.

   The lesson

   It reads uploaded PDFs and documents, and its collections keep the sources of a research thread together so you can return to them. 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 — ask which of the cited sources actually used the formula, rather than trusting the summary — then you can fix it yourself next month when the columns change.

   Example Upload a syllabus plus three job descriptions and ask what the overlap is — the collection keeps the four sources attached to the answer for later.

   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. Citations, focus modes and collections — Perplexity's own feature

   Every claim comes with a numbered source, the source list can be restricted to academic papers, videos, Reddit or a single domain, and a collection keeps the sources of a whole research thread together. That trio is what makes this a research tool rather than a chat with a search button.

   The lesson

   Because you can check it. A source list turns an answer from something you have to believe into something you can verify in thirty seconds, and verification is the skill every interviewer is testing when they ask "how do you know?"

   Use a focus mode narrow enough to matter, then read the top two sources before the answer. When a claim matters, use the citation as the beginning of your own research rather than the end of it — the citation tells you where to look, not what to write.

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

   PromptCopy

   Focus: academic sources only
   
   Question: What does the research say about how much sleep affects
   academic performance in university students?
   
   Give me:
   - the consensus finding, with the strongest single citation
   - any study that disagrees, with its citation
   - the sample sizes, so I can judge how much weight each one carries
   - what the research does NOT establish
   
   Cite everything. No claims without a source.

   The mistake is citing a citation. Naming the paper a summary pointed at, without opening it, is how a wrong number travels from one assignment to the next.

   Example Restrict a search to academic sources and ask for what the literature says about a topic; then ask the same question across social sources and compare the two answers.

   Practice Build one collection for a real piece of work — an assignment, an interview, a project — and add ten sources to it over a week. Then write two paragraphs from it without leaving the collection.

3. The Perplexity API and your first script

   Perplexity exposes its search-backed models over an API that returns citations alongside the answer, so a script can build a sourced brief rather than an opinion. 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 Perplexity" into "I have built with it", which is a different sentence in an interview.

   The lesson

   Perplexity exposes its search-backed models over an API that returns citations alongside the answer, so a script can build a sourced brief rather than an opinion. 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 openai import OpenAI
   
   client = OpenAI(
       api_key="YOUR_PPLX_KEY",
       base_url="https://api.perplexity.ai",
   )
   
   r = client.chat.completions.create(
       model="sonar",
       messages=[{"role": "user", "content": "What did [company] announce in the last six months? Cite sources."}],
   )
   
   print(r.choices[0].message.content)
   # the response also carries a citations list — keep it, it is the point

   The mistake is throwing away the citations array. Half the value of this API over the others is that it tells you where the answer came from, and a script that discards that is a script that cannot be audited.

   Example A script that takes a list of twenty companies and returns a sourced three-line brief on each is the classic use, and it is the shape of many real analyst tasks.

   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 Perplexity

   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.

   A weekly brief on a market, a competitor set, or an exam notification page — the same five questions, the same 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 Set a weekly reminder, run the same brief for the companies you have applied to, and read the changes rather than all of it.

   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 Perplexity AI certification paths.

1. Build the portfolio project: an interview research brief for one real company

   Pick a company you have genuinely applied to and build a two-page, fully sourced brief: what they do, the last year of news, the competitors, the risks, and the three things you will be expected to know. 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

   Pick a company you have genuinely applied to and build a two-page, fully sourced brief: what they do, the last year of news, the competitors, the risks, and the three things you will be expected to know. 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 Finished, it is two pages where every line has a link, plus five questions you would ask the interviewer that show you did the reading.

   Practice Ask a working professional in that field to read it and mark anything that is wrong or out of date. Being corrected is the fastest way to learn what a good brief is.

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.

   Never research a named private individual, and never paste an unpublished document into a search-backed tool — the point of these tools is that everything goes out and comes back with sources attached.

   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: research about a company is normal; research about a named person is not, and it will read badly if it is found. 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 Research threads record what you were looking into, and a search for a client, a candidate or a competitor is visible in the collection you saved it in.

   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. It is only as good as what the search returned, and popular sources are not better sources — an aggregated blog often outranks the primary document it copied 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. It is only as good as what the search returned, and popular sources are not better sources — an aggregated blog often outranks the primary document it copied

   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.

   Prefer the primary document: the official notification over the news story about it, the company's own filing over the summary, the published paper over the article describing it.

   Example Ask for the salary for a role and you will get three sources that all copied the same original number. Follow the chain once and you will see it.

   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 Perplexity AI paths

   A Way2Fresher certificate for this course is free and lives on this site. Beyond it, Perplexity AI 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 Perplexity AI issues record that you passed their own material.

   Perplexity does not issue certifications. Its own help material and the API documentation are the honest starting point, and its documentation is genuinely good on grounding. For a recognised certificate, pair this course with a provider-neutral research or analytics credential.

   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 Build a sourced one-pager on the company and the role, then use the sources list as your own revision sheet an hour before the interview.

   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.