#CS Undergrad Graduating May 2023 Looking for Full-Time Positions

79 messages · Page 1 of 1 (latest)

midnight sinew
#

Hey everyone, I was hoping to get some feedback on my resume. I am trying to make it into one page, and trying to figure out which part I should take out to make it all fit. There is nothing on my GitHub, as these projects were private. Any suggestions are appreciated!

keen oyster
#

can drop CC

slender idol
#

Follow the same style in education like experience

midnight sinew
midnight sinew
slender idol
#

you must maintain consistency. use a style, don't use style within your tex

midnight sinew
#

and I see multiple other resumes doing it the same way that I do it

keen oyster
#

the resume format is fine lol

#

i think you should reword the last bullet in ur recent sde experience

midnight sinew
#

lol alright - you think that's all I need to change then? I have one quantitative statement for Starbucks, just none for Northrop :/

keen oyster
#

it sounds a little clunky possibly. Maybe can say something like

#

Refactored Java Spring Boot application to leverage Azure Elastic Cloud, leading to ….

#

or something of that nature

#

oh nvm

#

i guess thats what the first bullet says

#

can u explain what the last bullet is conveying?

#

here

#

communicated and implemented features

any big features u can think of? or can u drop some examples features u did and maybe we can expand that out to dig some metrics

#

i would also probably drop the communicated bit

#

can just say “Implemented …”

midnight sinew
#

so the first bullet mentions that I used Java Spring Boot with Elasticsearch, and with the last one, I'm trying to focus more on the ELK stack, which includes the Logstash setup

slender idol
keen oyster
#

i would also maybe consider dropping the dates on the projects? one of them is 5 years old, do/will you remember the implementation details of the project if asked about it in an interview?

midnight sinew
midnight sinew
#

I get that it will look better

keen oyster
#

that one is just so maybe recruiters dont look at it like 🤔

midnight sinew
midnight sinew
midnight sinew
# keen oyster can u explain what the last bullet is conveying?

oh my bad, I thought you were talking about the Starbucks last bullet point, but I came up with a new one if you think it's better than the last one for Starbucks, since it's a little repetitive?
"Setup ELK Stack on Microsoft Azure, ensuring all data is up-to-date and its integrity is maintained."

#

it makes it fit on one line which imo looks better

#

but I'm not sure how popular ELK stack actually is

keen oyster
#

i would maybe spell out ELK so it hits more “buzzwords” and ensures we arent assuming people will know what ELK even is

midnight sinew
#

ok "Setup Elasticsearch, Kibana, and Logstash on Microsoft Azure, ensuring all data is up-to-date and its integrity is maintained."

keen oyster
#

“Designed and implemented data management system on Microsoft Azure, using Elasticsearch, Logstash, and Kibana to ensure real time data accuracy and integrity” ?

midnight sinew
#

for the other point at Northrop, I remember creating a component that rendered custom-designed UI to the user, so I could say "Implemented custom UI renderer..."

midnight sinew
midnight sinew
keen oyster
midnight sinew
#

okay I could reword the last Northrop bulletpoint as:
"Implemented a custom UI renderer to display user-designed real-time satellite-monitoring dashboards."

keen oyster
#

yeah, what technologies did u use? and what benefits did this dashboard have?

#

did it make it easier for users to debug issues or whatever? just something to think about

midnight sinew
#

from what I understand, it allowed the users to be able to quicker act on satellites with potential issues, but I wasn't really given the details of what the tool was used for

#

the point was to identify values that were out of range

#

I also added a couple features to graphs, such as limit lines

keen oyster
#

ok so maybe can dig into that. Not sure how it worked with your job but what was the problem statement when the task was given to u? did they say before hand like oh it takes users 20 minutes before they catch issues with satellites

#

so we need a tool that can help reduce that time

midnight sinew
#

would it help if I mentioned them again in later bullet points?

midnight sinew
keen oyster
#

i see

#

so maybe just say

#

“Implemented custom UI….., reducing time to catch fatal errors in satellites” or something of that nature

midnight sinew
#

okay, this is what I ended up changing it to:

#

I really appreciate your help on this KJ! 🙂

slender idol
#

remove the widow words because they are a lot.

#

also avoid using complete sentence. (I, me, myself, a, the...)

#

for each client --> for clients

#

Back end, front end are either a compound word or one word. if compoud then it is Back-End, if not, Backend.

#

Focused on providing --> provided?

midnight sinew
slender idol
midnight sinew
#

thank you!!

midnight sinew
#

it just sounds wrong to me

#

but I am not a writer :)

slender idol
midnight sinew
#

okay, I'll give those a shot!

distant burrow
#

a lot has been covered on formatting/writing; i will add a few observations from a technical standpoint:

  • 'boosting search perf.... 13,000%': i would be more interested in the underlying numbers behind this (X latency to Y latency), and what technology was originally being used (demonstrate technology migration and the result in a digestible manner)
  • 'ground software application' is confusing in isolated context - nobody knows what this means. mentioning satellite in the next point connects the dots a bit, but not directly/explicitly enough. you mention in this thread that the application is for checking/monitoring satellite info in some manner, just summarize it in a few words in the first point.
  • 'designed and tested efficient algos"... details on this? certain algorithm names? why were they efficient? this is a potentially interesting point that could have more substance
midnight sinew
# distant burrow a lot has been covered on formatting/writing; i will add a few observations from...
  1. hmm, I thought the first bulletpoint made it fairly clear that it was Elasticsearch causing this increase? it was due to offloading the database load onto Elasticsearch, so they ended up running alongside each other, I don't remember the latencies though
  2. I will work on that one
  3. there were no specific algorithms used, it was more of writing code to display labels and lines correctly, so good amount of object manipulations, and I said it was efficient because it was approved by other devs to be used in the application
distant burrow
midnight sinew
midnight sinew
distant burrow
#

that's something... just be prepared for interviewers to ask you details about it (whether or not you have the answers). fwiw, i've done a similar thing in the past (SQL alongside elastic), and i was asked further questions - hence my suggestions here