Advices on Internship Applications

GENERAL REMARKS

INTERVIEWS

Situation 01

Situation 02

Situation 03

Situation 04

Other situations

Additional remarks

  • Resume should matching the position
    • It might seems trivial, but ~30% of resumes received by employers do not!
    • Also see: match your keywords with those of the position/employer
  • Unnecessary Details
    • Do not list everything you did in every project, focus on things related to the position (yes, it might mean that you have a different Resume for each application!)
    • Keep the balance between the parts of the Resume (e.g. don’t list more hobbies than professional experience)
      • Most (industrial) employers are mostly interested in practical experience (i.e. “Professional Experience” part) rather then theoretical one (“Education”)
  • Meaningless Objective or Summary
    • It’s better not to have an “Objective” or “Summary” section than a vague one
    • If you have one, keep it short and meaningful
  • Too Long or Too Short
    • Also see: 1 page is perfect
    • Also see: If you don“t have much experience/education, don’t fake it. Think both hard & soft skill asked/required by Employer. Maybe some personal projects could illustrate one of these?
    • BUT, don’t get too obsessed about making the resume fit in 1 page and make it too dense (⚠ multicolums, font too small)
    • Again, focus on what the Employer might be interested in (cf. the job offer)
  • Demo of Work
    • Try to “prove” as much as possible your claims: add links to the code of your projects on Gitlab/Hub, websites that list prices you won, provide Recommendation letters…
  • *Don’t Explain the Project Rather Explain Your Role*
    • Maybe you have worked on a really big project. Don’t try to brag about the size or importance of that project. Rather try to explain your role/impact on that project.
    • See above: a link to the project repository with a good README explaining the project could be sufficient
    • Questions to be answered:
      • What part/module of that project did you work on?
      • What innovation/improvement you brought to that particular part of the code?
      • Why you were an important member of that project.
  • Take Care of Layout and Spacing
    • Visual appeal is a very important part of your resume.
    • See also: Your Resume is your (only) image in the eyes of the Employer
      • Things that are emphasized should be related to offer
      • Visual emphasis should be semantically coherent: e.g. if you highlight in blue elements concerning Machine Learning, then all ML elements (and only ML elements) should be in blue
      • Visual elements must be perfectly aligned
  • Favor Bullet Points Over Long description
  • Use Numbers to Explain Your Impact / Measure your impact
    • Example: I improved the initial loading time by 30%
  • Give Your Resume File a Proper Name
    • Add your First/Last name (and, eventually, the date of submission) to the file name (using YYYY-MM-DD ease visibility when sorting files by name)
    • The easier you make the Employer’s life the more they will like you
  • Include Your (professionnal) Profiles
    • We are in 202+! Your presence on the web is almost mandatory (at least professionnaly)
    • But include only professional elements: Gitlab/hub, LinkedIn, Stackoverflow, Medium…

RESOURCES

Let’s have Fun

  • Some of the ISI team’s researchers Resumes are on the web: try to spot what is wrong in them

Date: 2023-09-28 Thu 17:24

Author: Guillaume MULLER, Maxime LEFRANÇOIS…

Created: 2023-09-28 Thu 17:24