#Looking to move to fullstack. How does my resume look?

1 messages · Page 1 of 1 (latest)

tired pebble
#

Updated my resume to be a png

winged swift
#

please read through pinned google doc AND the example resume in the doc, which is found pinned in #339595755851612161

#

after reading through the doc, please feel free to look at this example to better help with bullet points

tired pebble
#

ok thanks!

tired pebble
#

Just updated it how does it look now?

winged swift
#

getting better

#

are u using google docs to make ur resume or something?

#

either way, overall format is getting there

#

need to fix left margins, losing a lot of space there

#

fix dates, they shouldnt be all misaligned

#

most bullet points still need work

#

capitalize “Redis” in first bullet (and all technologies in general)

#

the first bullet in ur sde position is confusing… not really understanding how a range slider (assuming its what im thinking about) is able to do this

#

“onboarding of new interns and developers” weak

#

“Installation and support for live demos for customers” weak

#

“Resolved bugs on a C# legacy system with over one million lines of code”
->
“Refactored legacy C# code to reduce bugs in the system by 20%”

#

“Refactored and improved design to better fit…” weak

#

“Created a db using MongoDb…” weak
->
you should probably say what your app actually does…

example:
*Created a web app for users to create, update, and delete their housing information using React, TypeScript and HTML.”

  • Integrated MongoDB to store and retrieve house data from users.
#

move education to bottom

#

can go ahead and remove coursework, its been more than 3 years since youve taken the classes

surreal field
#

Build your resume using a Latex template, the formatting could be greatly improved

tired pebble
#

Ok Great bullet points thanks for the advice going to do another round of editing thanks!

tired pebble
# winged swift the first bullet in ur sde position is confusing… not really understanding how a...

So the explanation for what I was doing is kind of long to explain. I had to build a range slider using wpf. How it would work is a user would make a query with another service and that service would send a start and date time and some ids to my service. My service would then send a message to our map application everytime the user dragged the thumbs on the slider, or the playback timer would tick. That message would be in a json format and sent via observers from redis.

#

What would be the best way to summarize that?

tired pebble
#

Ok one more round of editing done

#

What else would I have to update.

#

Sorry about the lack of changes for the range slider I could not figure out a better way to explain it 😦

#

Also I moved this over to a Latex template

winged swift
#

did u do anything else at the student sde job? u were there nearly 9 months

#

same thing with ur current job, anything else u did? its been 2 years. I would try and take a trip down memory lane and see what you can pull out

#

Integrated React…
->

  • “Created a web app to create… using React, HTML and CSS.”
#

CSV Parser :

  • Developed a CSV Parsing program using Java to sanitize and order CSVs with up to 500,000 lines of code.
#

maze app is pretty weak.. did u use any algorithms? design patterns?

#

put skills above education

tired pebble
#

So for the student SDE job a lot of what I was working with was third party tools and some minor bugs fixes that needed to be fixed. I figured that a lot of it wouldnt be too interesting or relevant to the job search. On an older iteration of this I mentioned that I made a csv file or something like that from a kendo grid. Should I include that?

#

For the maze I mosttly just used a stack to create it. Should I include that or is it a little too weak?

#

And my current job has mostly also been some minor bug fixes. For example I spent a couple months a while ago fixing some null errors and some race conditions in our software. I dont suppose a lot of people would be interested in hearing about that either. And another thing that I spent a lot of time on was the installation and setup of our software for demos and clients. Also something that may not come off as that exciting to employers.