Writing an email for an internship

Open
#449 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
content, documentation

Research direction

Create a Google Doc in your own Drive for a fictional engineering internship application to Vonda. Include a subject line, send-ready formatting, and the five requested points: motivation, background, current work, future goals, and why Vonda should offer the internship. Enable reviewer comments and share the document link in an issue comment.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:Issue
Learning Objectives
  • Write an email applying for a fictional internship
Why are we doing this?

The first stage in applying for any job will be writing to someone at the company to introduce yourself and explain why you are a good fit for the role. This assignment will give you an opportunity to practice writing in this way.

Draft an email to apply for an engineering internship at a fictional company called Vonda. Make sure to include the five things below:

  1. Why you want to become a software developer
  2. Your background and your past
  3. What you are doing at the moment
  4. Where you see yourself in the future
  5. Why Vonda should give you the opportunity to do an internship

The email should be formatted in a way that is ready to be sent. Make sure you include a subject title and pay attention to the formatting (font type and size, alignment etc).

Maximum time in hours

1

Submission & Review

Create the Google Doc in your own Google Drive.
Ensure the document can be opened and commented on by reviewers - you can find out how to do that here.
Share the link to the document in a comment on this issue in your planner.

Dominant language
JavaScript
Stars
0
Forks
397
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.