Skip to content
이력서 및학습 기록

Urgent fixes to my resume and portfolio!!

1 min readLearningMoved from my Tistory blogRead the Korean original

After being rejected quickly by a company I applied to, I started to wonder whether there might be a problem with my resume.

Below are the problems I found and the changes I made.

Strengthening the self-introduction

  • I felt my resume focused too much on frontend technology, so I added content highlighting the experience and knowledge I picked up in college as a major in the field, such as Spring Boot, SQL Developer, and networking.

Strengthening the tech stack

  • Many of the companies I applied to listed Next.js as a requirement, so I built a portfolio for recruiters with the Next.js, TypeScript, and Tailwind CSS I had already studied. I attached a link to this portfolio, deployed on Vercel.

Making the portfolio content easier to access

  • Before, I shared portfolio content written in Notion, but recruiters had to go through a login step to see it, which was a hassle. To fix this, I also added the portfolio content to the GitHub README. Now, without logging in, they can see the source code along with my experience, what I felt, and the issues I ran into while working on each project.

Issue notes

Problem: For visibility, I had set the coverImg size of the projects fetched through the Notion API to almost 100vh, and then I found that the images took quite a long time to load.

Fix: I adjusted the width given to project-card in the globals.css file.

The link below is my Next.js-based portfolio, deployed on Vercel, where you can see the various projects I've built so far.

This site has since been taken down. My later Next.js portfolio is at next-umsungjun.vercel.app.

  • #Next.js
  • #self-introduction
  • #job search
  • #portfolio
  • #frontend portfolio

More in Learning