This page needs a newer browser to run its tools. You can still read everything here.

Resume, Portfolio & GitHub Profile Module 11

Review, measure and automate interview questions

Interview questions on review, measure and automate: short warm-ups, then what each harder question tests, the first step of a good answer and its follow-ups.

8 questions: 3 warm-ups and 5 with model answers · Levels: Fresher to senior

Warm-up questions

Short questions with short answers, each answered in full.

Fresher to mid

How do you ask someone to review your resume so that the feedback is useful?

Answered in the lesson Resume reviews and tracking your applications
Fresher to mid

What is a response rate, and when can you compare two of them?

Answered in the lesson Resume reviews and tracking your applications
Fresher to mid

What does "resume as code" mean, and why would you do it?

Answered in the lesson Resume as code: JSON Resume, Typst and CI

Questions with model answers

What each question tests, the first step of a good answer and the follow-ups to expect.

Fresher to mid

Two people review your one-page resume. One says to cut your projects to make room for coursework; the other says to expand the projects and drop the coursework. How do you decide, and what do you change first?
What it tests

Settling conflicting feedback with a rubric and the posting instead of by who sounds surer, and making the change you can check.

First step

Ask each reviewer which rubric item the advice serves and which line they mean. Then score both proposals against the posting you are applying to: the version whose lines answer more of its must-haves with evidence is the one to keep.
Follow-ups
- Both reviewers are senior engineers. Does that change anything?
- How would you know later whether the change helped?
- What if the posting asks for neither projects nor coursework?
From the lesson Resume reviews and tracking your applications
Model answer, Pro. Model answers open with any pass; prices are in the notice on this page.
Opening the model answers with your pass…
Model answers open with any MySmartCoPilot pass.
Pro pass · 1 week₹79$2.99
30 days₹179$5.99
1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so the model answers can’t be opened at the moment. If you have a pass, enter your licence key.
Choose a pass I have a licence key
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

After six weeks your log shows 2 responses from 20 applications with your old resume and 6 from 20 with the new one. A friend says the new resume tripled your chances. What does your log support, and what do you do next?
What it tests

Reading response rates by group, spotting a second difference such as the channel, and planning a fair comparison with enough applications.

First step

Split both versions by channel before comparing them: if the new version's weeks also had the referrals and a campus drive, the channel may explain the gap. Then count the applications in each group, since in a group of five one reply moves the rate by 20 points.
Follow-ups
- Within job portals the old version did better. Now what?
- How many applications would you want before you decide?
- Would you go back to the old resume?
From the lesson Resume reviews and tracking your applications
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

Your CI says resume.json is valid against the JSON Resume schema, but the PDF it builds shows no lines under one of your projects. What happened, and what do you add so it cannot happen again?
What it tests

Knowing what a JSON Schema can and cannot catch, why a template can lose data without an error, and turning a silent loss into a check that fails with a reason.

First step

Compare the project's keys with the keys the schema defines. The JSON Resume schema accepts keys it does not define, so a misspelt key is valid, and a template that reads the correct name finds nothing there.
Follow-ups
- Why did the template not fail?
- Where in the pipeline does the new check go?
- Would you make the schema stricter instead?
From the lesson Resume as code: JSON Resume, Typst and CI
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

You want your resume repository to be public, so reviewers can see the pipeline, but employers need your phone number on the PDF they receive. How do you set it up?
What it tests

Separating public and private data, knowing what a public repository and its workflow runs expose, and checking for a leak before anything is published.

First step

List everything the public will see: the repository's files and their history, and whatever the workflow keeps or publishes. Keep the phone number out of all of them, then decide where the full PDF is built instead.
Follow-ups
- The number was committed last month. What now?
- Can the workflow use a secret to build the full PDF?
- How would you test that nothing leaks?
From the lesson Resume as code: JSON Resume, Typst and CI
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to senior

A recruiter who uses a screen reader tells you your resume PDF has no headings to jump between. How do you build PDFs that work for her and for a parser, and prove it on every change?
What it tests

Knowing what tags, a title and a heading structure give assistive software, how a build can enforce them, and how to check the extracted text automatically.

First step

Find out what the PDF lacks: whether it is tagged, whether it has a title and a language, and what text an extractor gets from it. Those are the properties every build must then enforce, with a check that fails when one is missing.
Follow-ups
- Is a tagged PDF enough on its own?
- What does your CI check, and why check twice?
- After a teammate's template edit, every build fails. What do you look at first?
From the lesson Resume as code: JSON Resume, Typst and CI
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes

All Resume, Portfolio & GitHub Profile interview questions · The Resume, Portfolio & GitHub Profile track

Warm-up questions

How do you ask someone to review your resume so that the feedback is useful?

What is a response rate, and when can you compare two of them?

What does "resume as code" mean, and why would you do it?

Questions with model answers

Two people review your one-page resume. One says to cut your projects to make room for coursework; the other says to expand the projects and drop the coursework. How do you decide, and what do you change first?

After six weeks your log shows 2 responses from 20 applications with your old resume and 6 from 20 with the new one. A friend says the new resume tripled your chances. What does your log support, and what do you do next?

Your CI says resume.json is valid against the JSON Resume schema, but the PDF it builds shows no lines under one of your projects. What happened, and what do you add so it cannot happen again?

You want your resume repository to be public, so reviewers can see the pipeline, but employers need your phone number on the PDF they receive. How do you set it up?

A recruiter who uses a screen reader tells you your resume PDF has no headings to jump between. How do you build PDFs that work for her and for a parser, and prove it on every change?