can probably remove coursework at this point and drop education to the bottom as youve been out of school for 2 years
#Laid off after 1 yoe, any resume advice appreciated
signal rampart
swe work experience is pretty meh… doesnt really sound like u did anything. Did you spend the entire year working on the auto population system?
should include how and what u used to create said autopopulation logic as well? Java? Database? APIs… etc
inland zinc
swe work experience is pretty meh… doesnt really sound like u did anything. Did ...
prob around ~3-4 months. PMs kept changing the scope whenever I asked about an edge case when debugging (learned a lot from that). I also had to make sure it worked on the new code and legacy code of the product which hasn't been touched at that level in a long time, there was a lot of bad coding practice and unexpected behavior that I had to fix first. At the same time, confirm with PMs about new/expected behavior on them. I guess I can add that to the bullet point.
the rest of the things I worked on were various bug fixes and feature requests in different areas of the product. It was a startup so I just got assigned to the highest prio dev work possible to me.
inland zinc
can probably remove coursework at this point and drop education to the bottom as...
would it be better as
work -> projects -> school -> skills?
or
work -> projects -> skills -> school?
signal rampart
prob around ~3-4 months. PMs kept changing the scope whenever I asked about an e...
confirming behavior isnt anything.. extraordinary. thats pretty expected
i would however add points on bug fixes and whatever other features u created
signal rampart
would it be better as
work -> projects -> school -> skills?
or
work -> projects...
um 2nd one is fine
signal rampart
worked on various bug fixes and feature requests
- at the least u should expand on the features u implemented. What did these features do? what did you use to create these features? what impact did these features have (more traffic? more $$$? latency improvements? etc)?
thays what recruiters wanna see
they wanna see tangible things u did
not that u talked to clients about a deadline like yeah sure that is important sometimesbut they wanna know what youve done code wise
inland zinc
for expanding on those, I can't really think of another big specific feature as I worked on lots of small-mid bugs/requests. would something generalized work like:
"reduced time and space complexity on various parts of backend and frontend allowing for faster loading and processing times."
or does it need to be more specific?
signal rampart
how did u reduce time and space complexity?
reducing time complexity is reducing latency so u just said u reduced latency by reducing latency if u dont think about it much
what did u do? did u use different libraries? did u refactor legacy code to utilize newer updated code like java 8 to 17 or whatever the highest one is
or python 2 to 3 etc
but latency didnt improve on its own, what did you do?
inland zinc
makes sense. I mainly did refactoring code for those so a bullet point would prob be:
Reduced latency and improved coding structure on various parts of the backend and frontend by refactoring code to utilize faster algorithms, removing unused code, and breaking down complex functions into smaller, abstractable functions.
this direction makes more sense, just thinking of how to phrase it better.
signal rampart
“faster algorithms” what about the algorithms were faster?
vs the previous, slower, algorithm
- Refactored legacy Java code to utilize DRY principles via object oriented programming, increasing code usability and readability.
- Reduced system latency by XY% by optimizing Java algorithms to use….