How? Any design principles you've implemented?

What does this mean?

This doesn't help that much. I think we can drop this and add a more valuable bullet instead in this or other projects. Justification: most projects your competitors will create are solo projects, so you're kinda boosting them in comparison because of your statement :)

It would be good to hyperlink the projects!

It would be good to tell the reader what criteria the awardee needs to meet to earn it! Justification: people outside of nova scotia does not know what a Sexton Scholar is

I don't think these are necessary and might contribute to negatives instead of positives (justification: projects age, and I don't want to expedite that aging process by claiming something is from university course or high school)

For certifications, we generally go look after more technical certificates, like AWS Cloud Practitioner. I think we should drop everything here in favour of those technical certificates, or remove them completely to add room for more projects

Can this expire?

I think we should get rid of this -- let's only talk about one subject for each bullet.

You definitely want more unit tests, and also, unit tests do not future-proof anything! It just makes developers know "oh crap, the code should follow this path instead of the other way around" if they make any dumb breaking changes. If your library changes, that can be potentially future-breaking. Same thing with deployments as well!

Like what libraries and frameworks? I thought "recursion" was more of a concept that didn't need any libraries or frameworks?

This is probably doing you a lot worse than you think -- this means that you've kept 7% of the bugs you've found and haven't addressed it for some reason, which is bad!

This sounds cool af, where's the link??

I'd probably split this down to more categories so you can talk more about it. For example, devtools, libraries, frameworks, platforms, etc

No way to prove this; does not belong on resume

I feel like you know a lot more skills! For example, Python?

Heads up - they might ask why you switched university in some interviews, so prepare for that :)

GPA?

over a thousand --> 1000+

Also, not to pick any skepticism but how did you measure "1000+" here?

Good place to talk about how many students you've trained to add metrics

Any theory or practicalness of designing a new GUI? How does that impact the user experience? Anything you've done special to improve the user experience?

How does making standards reduce operating costs? How does that improve functionality?

What does this mean? I'd probably prefer you to talk about the infrastructure rather than "I wrote new codes and sometimes written stuff over pre-written code"

You mentioned unifying things, but how did this impact the user workload exactly? Did you mean developer workload?

Confusing sentence -- is there an example?

Not relevant on your resume; we should drop it

Hard to measure metrics, but is there a way for you to qualify or quantify the improvement you've done other than directly saying that you've improved it?

Probably a wrong verb to start with -- you don't really "partner up" with the professor. You do work within the curriculum created by the professor so you're more-so a delegate. Maybe we should drop this part and go straight to "Planned and implemented..."

Like what?

I'd also put this under "Work Experience:

Just "Work Experience" is good enough

You should swap Sentinel to be moved to the top, then ResuRalph, since starting dates are used as tiebreakers for reverse chronological order

Would prefer if GitHub was underlined to better visually differentiate what's clickable vs not

No need to place a period after May

What did you actually design? Why is it robust?

I'd also focus on quantity over quality for projects, so let's try to limit the projects to 3 bullets max. Maybe 2.

This is a word that every software engineers go nuts for. How did you make it scalable? It's probably worth to even dedicate a whole new bullet for it.

Bullet trails for a bit long here. I wonder if it can be shortened.

Would love to hear the actual time-metric here instead of percentages.

What "client" does this refer to? Human, bot, application, etc there's a lot of clients in the world that it's probably valuable for you to specify which!

You clarify the type of storage here but not on the compute. I wonder if you can just get rid of Azure Blob Storage and just start off with something like "Implemented and managed Azure services..." and let them figure out the specific service from there on

I still don't understand the value of putting "100%" here. All deployments should be "100%" so it feels like you're stating a redundant obvious. I think we should choose a different metric.

same here

I see that you've just increased the number, but some recruiters do ask how you've gotten that number. How will you describe it? We can discuss this on Discord

Would like to see Months as well

Would like to see these on the same line now that we've shortened it! Gives us another vertical line to work with.

you should put Azure and OpenAI somewhere here as well :)

Same here as well, it helps more to say CSS than CSS3 for ATS purposes

It helps more to say HTML instead of HTML5 for ATS purposes

no need to say this

Many of these are expired! Would it help strategically if we were to just not show the validity period at all?

I think you should mention "user experience (UX)" in the bullet above, and only use "UX" here so glossary flows easier.

no need for this comma

I think a percentage isn't the best metric to show off here -- ideally, we should be reducing user input errors down by like 99%. If there's a user input error that isn't captured by your sanitation system and causes a service-side bug, then it could actually be a negative thing to show off here.

over two days,

No need to place this

what's this in more tangible data, like in milliseconds? I want to see if denoting the actual speed is better than denoting the optimization

I don't understand what this means exactly. I feel like all deployments are always a 100% deployment, so I think this is a redundant metric. I wonder if there's another metric you could use?

Would prefer to have space in between the hyphen

Would prefer to have space in between the hyphen

by how much? Do you have an example latency you've saved?

Same comment about accuracy actually being pretty low here

This is actually pretty low given today's standard of fitting models to have crazy accuracy. I'd probably change these metrics to something else, or blow it up a bit more >90%

If you are putting down relevant coursework (which imo is only used as a filler, and should be overridden by more interesting projects), make sure that these relevant coursework stay relevant for ALL job applications you put in there -- make sure to tailor it so you don't end up saying you worked on mobile computing when the job description asks for knowledge in JWT or something

Lots of value in adding your university start and end date under Education!

You can put your website link here as well if it's hosted online!

I'd prefer to hyperlink these labels instead of listing the entire URI next to each label

Not much value putting address here, so I'd get rid of it

There's less value in putting your portfolio website as part of your project list since there's a dedicated free space you can put in your header. I'd probably look to replace this one for some other interesting project.

Don't really see the value of saying Full-stack developer here when the previous wx title was Software Engineer Intern, so I'd probably choose one and keep it for consistency. My bias would be Software Engineer Intern since it looks like you are doing more backend stuff.

어떤 파트가 30%인거지? 디테일 추가 필요햐

얼마치?

어떻게 자세히?

얼마나?

굳이 안넣어도 될 듯

프젝 추천 더 하자면,

"Vibe Coding" 이라고 들어봤어? AI를 직접적으로 쓰고 너의 멘토처럼 물어보고 거의 이거 하나만 의존한다라는 그런 프로젝트인데

하나 만들어보는거 어때?

왜냐면 지금 백엔드 프젝이 많이 없는데 아마 그걸로 하나 만들면 좋을 것 같아. 예를 들어서 어떤 특이한 API 를 하나 만든다거나

시작 날짜를 Sep 2021로 왜곡하는걸 추천해. 더 자연스럽거든. 지금은 3년제로 오해할 수 있고, 뭔가 이런 것에 대해 특이한 질문들을 많이 물어볼 것 같아.

잘했어

하나 아쉬운 점이 있다면 너무 아티피셜하다? 라는 느낌. 그냥 다른 프로젝트 포크 하고 다른 데이터만 살짝 쌓은 느낌이 Readme 에서 너무 진하게 나거든. 아마 Readme 를 만져줘야 할거야. 어떻게 쓰는지도 꼭 알려주고

끝낸거면 그냥 May 2025 로 남겨도 돼.

(May 2025 - May 2025 가 아니고 그냥 "May 2025" 하나만)

개인적으로 따로 아이콘을 넣는 것보단 텍스트 위에 바로 Hyperlink를 넣는 것을 추천해. 그러면 깃헙을 모르는 사람이여도 프로젝트가 이걸 누르면 이동하겠구나--라고 생각하니깐.

예를 들어 ATS 같이.

이미 깃헙은 상단에 놨으니깐 이 아이콘은 빼는게 더 나을듯 해

좋아좋아

뭔가 $90은 뒤 45%에 비해 조금 싼 느낌이 있거든. 이걸 연으로 바꾸면 $1080 이니깐 "Saving $1000+ every year" 로 바꾸면 좋을 것 같아. 큰 숫자로 가자구

이건 첫 토픽인 Design Document 하고 살짝 다른 얘기인것 같아서 다른 불릿으로 스플릿 하는게 더 좋을 것 같아.

얼마나 더? 돈으로 따지면 얼마나 더 좋을거야?

얘도 뭔가 두 가지 것들을 말하고 있는 것 같아서 두 가지 다른 불릿으로 스플릿 하는게 더 좋을 것 같아. 물론 둘 다 Action Statement 로 갈아 만들고

이건 새로운 불릿을 하나 만드는 것을 추천해

이게 Result로 완전히 와닿지는 않는 것 같아. 나는 오히려 저 Powerful Feature 를 조금 더 설명하는게 더 나을 것 같다고 생각해.

굳이 너가 만든 feature 가 아니라도 그게 왜 좋은지 어떻게 만들었는지를 대충 안다면 쓰는게 나는 더 이득이라고 생각해.

예를 들어서

Delivered X features to empower Y for clients, enabling RESULT

...로 일단 포맷을 바꿔보자

나는 저 위에 있는 40% 보다 이 "significant time" 과 "cost saving" 에 초점을 맞추는게 더 좋지 않을까 싶어. 돈과 시간은 회사에겐 금은보화같은 존재니깐

개인적인 궁금인데 어떻게 이 데이터를 확보했는지 알려줘 아마 다른, 믿기(?) 계산이 더 쉬운 데이터를 주는게 더 확실할 것 같아서

아마 저 위에 있는 Dash Social 을 두 개의 experience 로 나눈다 하면 아마 자리를 더 확보할 수 있도록 이 VP internal를 빼야 할거야

이거 아마 두 가지 다른 Work Experience 로 나눠야 할거야. ATS 들이 이걸 어떻게 해석할지 몰라서 그게 머신들이 이해하기 더 좋을거야

뭔가 Tool들을 많이 껴놓은 느낌이야

레스토랑 가서 웨이터가 신나게 음식 설명하는데 내가 그 음식의 지식이 많이 없어서 헷갈리는 것 같은 비유

추천하는 건 좀 더 무지식해도 알아들을 수 있는 것 아니면 적어도 Tool 이 아닌 "WHAT YOU DID & RESULT" 를 더 크게 설명하면 좋을 듯

예를 들어서

Developed a schema validation service with SQLAlchemy to reduce operational pain in manually approving database changes, saving $[x] for the company every year.

여기서 X는 어떻게 부풀리냐면: 저 서비스를 쓰거나 도움을 다이렉트로 받는 직원 수 * 그 직원들의 평균 시급 * 그 직원들이 이 서비스를 한 달에 1시간당 얼마나 많이 사용하는지 * 12개월 그러면 대충 돈으로 계산됨

돈만큼 어그로 잘 끌리는게 없거든

Sep.

Sep.

Halifax, NS 랑 날짜랑 스왑해도 괜찮을듯 포맷 비슷하게 가게

이런 건 단어 위에 Hyperlink 해두는 것을 추천. 이메일 링크딘 깃헙같이

여기 있는 불릿들도 여기에 있는 것보다 더 많이많이 써놓으면 좋아. 일 마다 요구하는 스킬들이 다 다르니깐 최대한 맞춰가면서 쓰면 좋아

그리고 프젝들도 일 어플리케이션 봐가면서 교체해햐해

예를 들어서 web dev 잡이면 k-beauty 같은 것들을 많이많이 추가해주면 좋고

same here

VP internal 이란 직업 이름이 아쉽긴 한데 그래도 이젠 relevant experience 를 많이 쌓았으니 공간이 모자라면 버려도 될 것 같아

빼도 될 것 같아. 일해보니깐 design doc을 만지는게 결국엔 end user 랑 일하는 거니깐 비슷한 건 안넣어도 될듯해

45%는 아마 돈으로 환산하는게 더 나을 듯해

똑같은 formula 로 계산하면 대충 값이 나오니깐 해봐바.

또한 REST API "wrapper" 가 뭔지 잘 모르겠어. 그냥 REST API 를 만든 것 같은데 그냥 그렇게 적는게 더 나을 듯?

그리고 어떤 것들을 해서 저 값을 줄였는지 조금 더 디테일 추가하는 것을 추천해.

"Synthesized design documents through daily SCRUM meetings" 가 뭔가 잘못된 것 같음. 시작이랑 끝맺음이 어울리지가 않아서... 아마 Design Document 에 포인트를 두면 더 좋지 않을까 싶어.

예:

Wrote design documents [FOR WHAT], scoping and detailing the project milestones and dependencies to help manage the workflow across [NUMBER OF TEAMS OR MEMBERS].

지금 보니깐 "enhancing maintainability" 가 무슨 뜻인진 잘 모르겠어. 아마 바꿔야 할 듯? 이거 context 를 까먹었는데 다시 설명해 줄 수 있어?

베이스가 잘 깔려있는데 요 두가지 질문만 답할 수 있다면 좋을듯:

• "enhanced functionality" 가 어떤 functionality 인가요
• "optimized client workflow" 는 돈과 시간의 관점에서 얼마나 세이브를 한건가요

테스팅은 몇가지 유형이 있어: - 유닛 테스트 - 인테그레이션 테스트 - 캐너리 테스트 - 페네트레이션 테스트

Pytest 보니깐 아마 유닛 테스트인 것 같은데 그러면 일단 100% 코드 커버레지는 적어놓는게 좋고

pipeline 이나 다른 CI/CD 툴이 있으면 이 테스트를 automated 했다는 것을 밀면 효과가 진짜 좋아

Agile 만 쓰기에는 좀 더 질 좋은 라인도 있을 것 같아서 일단 보류해놓자

제일 좋은 시나리오는 Result 가 돈, 시간, 아님 다른 실직적인 데이터로 계산하는게 베스트고

일단 넘어가자

뭔 말인진 알겠는데 그 뽀인뜨가 살짝 아쉬워 - Ensured seamless interaction --> Action - between the tech stacks by writing and maintaining Vue.js codebases --> What you did - to deliver a dynamic user experience --> Result

이걸 완전 압축해서 풀어보면 "I used vuejs" 라는 말만 되는 거여서 좀 더 섬세하게 들어가면 좋을 듯 해

여기서 내가 역으로 물어본다면 아마 제일 첫번째로 물어볼게 "What part of the codebase did you take the primary ownership of?" 이나 "What did you actually build with Vue.js?" 같은 것들을 물어볼 것 같아

그럼 아마 "Ensured seamless interaction FOR WHAT EXACTLY using WHAT DID YOU DO WITH VUEJS EXACTLY to deliver a dynamic user experience". 여기서 "a dynamic user experience" 는 더 알맞는 phrase 로 교체하는걸 추천

한 라인이라도 세이브 한다는 의도로 빼도 될 듯 이미 GPA 써놨으니깐

100% 더 많이 알거임

여기서 내가 이런 말을 할 줄은 몰랐는데

AI 도 껴보는거 어때? Amazon Q CLI 나 뭐 그런 것들 있잖아 VSCode extension 같은 것들

AWS 의 어떤 서비스를 이용했는지 세분화 하는 걸 추천해

얜 딱히 language 가 아닌 Dev Tool이여서 밑에 있는 Developer Tools 카테고리에 넣는 걸 추천함

그냥 MySQL만 넣어도 될거야

스페이스 넣기

아마 요걸 빼야할듯 공간 만들려면

스페이스 줄일려고 한 것 같은데... 아마 ATS 시스템이 잘 읽을 수 있을지 모르겠다 날짜가 2개가 아닌 4개여서

아마 바꿔야 할 듯

May 2024 -> Apr 2025 로 하던지 아님 그냥 두 가지 텀을 따로 쓸지가 그럼 고민이 되는데

개인적으로 따로 넣는 것을 추천함 대신 다른 곳 지워보자

No period after "May"

sub-500ms can be either really slow or really fast all depending on context. For example, league of legends ping versus downloading a video. I would probably choose a different metric here so it's less confusing and more "wow"y

no need for this - analysis is a close synonym already

I wonder if adding the soldier class (병장 = Sergeant) works out in your favour better

Would still prefer to add a declaring statement somewhere that you didn't actually finish the degree here to not confuse them

with what?

did you get 100% of the coverage? This is important!!

double "and"s in the same sentence - you should wait the "and" until the last item in the list

by how much?

use English-form numbers if you aren't talking about a big quantitative data you want them to focus on, e.g. "three"

no need for this

you can probably hyperlink this as well with mailto:

btw, you should tailor the bolded characters depending on what jobs you apply for. For example, right now you are really boasting a lot of frontend stuff. If you wanted more emphasis on AI, bold the ML related words. If you wanted more emphasis on cybersec related things, authNZ stuff

how?

such as

no need for this tilde

FYI, they may ask you about these numbers so prepare to explain how you got them!

resume without trailing 's'

employee

York University - AI & Data Society

Keep it in the same location format

on the

practice

There's a benefit of keeping this sentence this way (you show off A+ first), but you can also write it more like an action statement (so you can show off what you did).

Action statement here would just be walking this sentence the other way, so it should be a simple change if you decide to take it

missing period

missing period

adapting

should drop this comma

Not really sure if the team member amount is relevant here, especially so since you've now proven you can work in a team with your internships, so we could probably drop this here and in the QuickCash one as well

some of these kinds of fragments we can probably slash off and reword instead - similar to "which".

ThreeJS here but Three.js in the project stack list - we should probably keep it consistent

iOS with a lowercase i?

Not a nit but just surprised on the pure time length of the project lol

May be still relevant - may not be very soon - let's drop this bullet if we need to

by how much and with what metric?

like what exactly? what's the contribution? how does it help?

missing period

more of analyzing the overall strength of the bullet here - this is just saying you worked in Grant Thorton and not much after that. I wonder if you can describe what you did in your work rather than trying to prove you worked there?

=> Engineered

let's try to drop "which" in future bullets and see if we can just write stuff in a sexier way (I do like the contents in your bullet here, so it should be simple reorganization of words)

duplicate of 2nd bullet - probably unneeded

Usually having these kinds of words show that we can make this sentence better just by swapping the order of things in which they appear:

"Root caused bugs through analysis of system design documents and recorded the runbook to prevent similar issues from propagating in the future." (something along those lines)

Curious if this isn't breaking any severe NDA under national security

should this be hyphenated?

It's generally not advisable to use a first person language in your bullets

No need to capitalize these

Let's drop this in preference for the second action verb "Collaborated"

Is the hyphen intentional?

React is a library - I think you should make a new section called "libraries" and put a bunch of random libraries in there

You 10000% know more languages than this! (forgetting python at the very least)

Make sure this section is long enough to fill the resume

typo - space and comma should be swapped

up-to-date

"and"

"Squarespace". Also is "Dalhousie Student Union" a "company"?

the 1st bullet seems to cover this.

Also, if the work experience isn't related to your job, you can probably spend less bullet points in here, so let's aim for 2-3 bullets at most, and fill the rest up with projects.

action statements

is "tailor" the right verb? In any case, we should probably start off with the strongest verb instead of the current "collaborated". E.g. "Tailored newsletters using SimplyCast to promote initiatives from departments of the University and Student Union, amassing over 40,000+ impressions"

in the above example, we can even combine the bullet before this, making it a stronger bullet in general and saving space.

"and"

Regularly is a weak verb - we should probably start the statement with just "Designed and delivered newsletters"

missing comma, should be SimplyCast,

Probably should revise this - feels a bit empty even though it's following the action statement format.

How about: "Developed the dynamic display of student data in the admin dashboard using MongoDB (and if you used something else, add that here, ie Axios, Mongoose, etc), amplifying the admin experience for managing students." or something else if you know better

Action statement

how?

design principles*

What website? Can you hyperlink? Also, be as specific as possible -- what did YOU do? and what did YOUR actions create WHAT results?

You should probably pick one or the other, and not both. Generally, this project-based course experience would be under projects over experience though due to the lack of proper leadership (95% of 4th year students know nothing lol)

No need for this specifier

what graph? This is a good example of where action statements can help you.

how?

should generally avoid symbols and prefer English words, e.g. "and"

What software? And what did it result in?

This seems to be talking about the same thing as the bullet before this. We should probably drop this bullet and make room for something unique

and saved how much time with this?

all-in-one

missing comma, should be ClosedXML,

You should make this into an action statement: https://www.lakeheadu.ca/sites/default/files/uploads/104/ResumeWorkshopHandout2016.pdf.

Also generally, you should try to be as specific as possible to clearly draw out what you did and resulted in what

You should stick to abbreviated or full month name format (Experience seems to use full month name, so pick and stick with what you prefer)

You should drop this - after you get into University, then secondary school is no longer relevant

Should this be a separate bullet?

Another case of "you can definitely optimize this because you probably don't need this set of words". For example, "Created a user-friendly UI to provide precision control of the beamformer" is a more concise and optimized sentence

Can we just say UI?

Can we fit this inside a singular sentence?