Awadesh Pratap Singh University Students: Frontend Internship Questions to Ask on Day One

On day one of a frontend internship, ask about repository access, coding standards, tools, review process and what “done” means for your tasks. In a 14-day internship you have no time to guess, so the questions below are grouped into day one, days 2-7 and days 8-14, with a note-taking sheet to record every answer.

Why a 14-day frontend internship needs a question plan

A two-week internship is short. If you spend three days waiting for repository access or discovering that the team uses a different package manager from the one on your laptop, a fifth of your time is gone. Most delays in frontend work are not about difficult code. They come from unclear setup, unwritten style rules and vague expectations about what a finished task looks like.

The free two-week online internship at CareerSwami runs for 14 days, includes a free offer letter and a free completion certificate after successful completion, and is offered across 26 tracks. Whatever track or company you work with, the question bank here applies. Adapt the wording to whoever is guiding you, whether that is a mentor, a team lead or a task coordinator.

A good rule: ask each question once, in writing where possible, and record the answer. Written answers protect you when instructions change and give you material for your final report.

Day one questions: access, setup and scope

On day one, the goal is to remove blockers. Ask these in your first message or first call.

Repository and access questions

• Which platform hosts the code (GitHub, GitLab, Bitbucket, or shared files), and who grants access?
• Will I get write access, or do I work on a fork and send pull requests?
• Which branch should I start from, and what is the branch naming rule?
• Is there a README or setup document? If not, who can walk me through the setup?
• Do I need any environment file, API key or sample data, and how do I receive it safely?
• Is the code confidential? Can I mention or show the work in my portfolio afterwards?

Tooling questions

• Which Node.js version and package manager (npm, yarn or pnpm) does the project expect?
• Which framework and version is in use: plain HTML/CSS/JavaScript, React, Vue, or something else?
• Which editor settings, linters or formatters must I install?
• Which browsers and screen sizes must the work support?
• How do we communicate daily: email, chat or calls, and at what time?

Scope questions

• What is the one deliverable I should finish by day 14?
• Which tasks are fixed and which are optional extras?
• Who do I ask if I am blocked, and how quickly can I expect a reply?

Days 2-7 questions: coding standards and review

Once your setup works, shift to how the team writes and checks code. These questions prevent rework.

• Is there a style guide, an ESLint or Prettier configuration, or a component naming convention?
• How are CSS rules organised: plain CSS, CSS modules, Sass, Tailwind or a component library?
• Are there accessibility expectations, such as semantic tags, alt text, keyboard navigation and colour contrast?
• How should commit messages be written, and how large should a pull request be?
• Who reviews my code, and what is the typical turnaround?
• Are there design files (Figma or screenshots) I should match, and how close must the match be?
• Should I write tests, and if so with which tool?
• How do I report progress: a daily update, a weekly summary or a task board?

Days 8-14 questions: delivery, feedback and evidence

In the second week, you need clarity on completion and on what you can take away.

• What counts as done for each task: merged code, a working demo, or a reviewed pull request?
• What feedback format will I get, and when is the final review?
• What must I submit to qualify for the completion certificate?
• Can I keep a link to my pull requests or a screen recording for my portfolio?
• Can the mentor comment on my work in a short reference message, if they are willing?

Frontend internship question scorecard by priority

If you can only ask a handful of things, use this table to decide what comes first.

Note-taking sheet for day one answers

Copy this into a notebook or document. Fill it in as answers arrive, and note the date and who told you.

Illustrative example: turning vague answers into a clear plan

This example is illustrative and not a real case. Suppose a student is told on day one: “Build a responsive course card section for the landing page.” The student asks the questions above and records the following.

• Repo: a fork, with pull requests to the main repository.
• Tools: React with a stated Node version, and Prettier on save.
• Design: a Figma link with a mobile and a desktop view.
• Done means: a pull request with a short description and two screenshots, reviewed by the mentor.

The student then builds a 14-day plan from those answers:

1. Days 1-2: set up the project, confirm it runs, and read the design file.
2. Days 3-5: build the card component with semantic HTML, mobile layout first.
3. Days 6-7: add the desktop layout and a basic keyboard focus style, then request a first review.
4. Days 8-10: apply review comments and check the layout at several widths.
5. Days 11-12: tidy the code, write the pull request description and take screenshots.
6. Days 13-14: final review, submission and a short reflection note.

Without the day one answers, the same student might have used the wrong framework, skipped the design file and lost the first week.

Awadhesh Pratap Singh University students: using your syllabus to frame frontend questions

The only official document tied to APSU that is relevant here is a search excerpt from the Department of Computer Science’s M.Sc. Computer Science CBCS syllabus with CO/PO mapping, dated 2020. The excerpt mentions topics such as basic computer organization and C programming basics, and gives the university address as Rewa (M.P.) 486003. Because this is an excerpt from 2020, open the current version on the university website before relying on it.

What does that mean in practice? If your coursework leans towards fundamentals such as programming basics, a frontend internship will likely introduce things your syllabus may not cover directly: HTML, CSS, browser tools, Git and a JavaScript framework. That is not a problem, but it is a reason to ask setup and standards questions early rather than assume you already know the team’s way of working. Use what you learned about logic and structure, and ask openly about everything else.

The material available does not state any rule on internships, project work, credits, evaluation or whether online internships are recognised for your programme. Those rules may be set by the university or by your affiliated college, so confirm them rather than assume. Do not treat the internship as academic credit unless your department confirms that in writing.

Verification steps before or during your internship

1. Ask your department office or class coordinator whether your programme has an internship, training or project requirement, and request the regulation or circular in writing.
2. Check the current syllabus on apsurewa.ac.in for your own course and year, rather than relying on the 2020 document.
3. If you want the internship noted in your records, email your head of department asking what proof (offer letter, certificate, report) is accepted.
4. Ask whether your college or the university sets the rule, and who signs any permission form.
5. Check the semester calendar for exams so your 14 days do not overlap with them.
6. Keep your offer letter, daily notes and certificate together in one folder for any later query.

Month one and beyond: questions for after the 14 days

The brief for many students is a “month one” view. Since this internship lasts 14 days, treat the month after it as follow-through. Ask or do the following:

• Which skills did the mentor suggest improving next: JavaScript fundamentals, a framework, testing or accessibility?
• Can the finished work be turned into a small portfolio project with a short README?
• What would the mentor change if the project continued?
• Which two or three tasks from the internship can you describe in a resume line without exaggeration?

Describe only what you did. Do not claim a stipend, a job or academic credit, because none of these come with the CareerSwami internship.

How to ask questions without slowing the team

• Batch related questions into one message instead of sending five separate ones.
• Show what you already tried: the error message, the command you ran and what you read.
• Offer a default: “Unless you prefer otherwise, I will use the existing lint config.”
• Summarise decisions in writing: “Confirming: I will submit by pull request on day 12.”

Frequently Asked Questions

What should I ask first on the first day of a frontend internship?

Ask where the code lives and who gives you access. Then confirm the tool versions and the single deliverable expected by day 14. These three answers unblock everything else.

Is a 14-day internship long enough to build something meaningful?

Yes, if the scope is small and clear, such as one component, one page or a set of fixes. The question bank above helps you narrow the scope early.

What if I have no access to the repository on day one?

Message your mentor at once and ask for an expected time. Meanwhile, read the README, set up the tools locally and study the design files so the waiting time is not wasted.

Do I need to know React before starting?

Not always. Ask on day one which framework is used. If it is new to you, request a starter task and a short list of resources, and revise HTML, CSS and JavaScript basics first.

Will the internship count as credit at Awadhesh Pratap Singh University?

That cannot be assumed. The internship offers a free offer letter and a free completion certificate, not academic credit. Ask your department in writing whether any such recognition exists for your programme.

How should I record what I learn each day?

Use the note-taking sheet above for answers and keep a short daily log: what you did, what blocked you and what you will do next. It becomes the basis of your final report.

Can I show my internship work in my portfolio?

Only with permission. Ask on day one or by day 10 whether the code and screenshots can be shared, and keep the reply in writing.

What if my mentor does not answer quickly?

Follow up once with a short, specific message, and meanwhile work on tasks that do not depend on the answer. If delays continue, raise it with the programme coordinator.

Related Frontend Development guides

• Sri Sathya Sai University: Frontend Internship Service Project Building a Community Web Tool
• K.K. Modi University Students: Frontend Internship CSS Architecture with BEM and Variables
• Sarvajanik University: Frontend Internship Cross-Browser Testing Matrix for Beginners
• All Frontend Development internship guides