#Need Resume Review PLS HELP. Got 0 Processes I don't know what i am doing wrong

1 messages · Page 1 of 1 (latest)

fallen merlin
#

Requesting a review as I need help and I got nothing so far. Additionally, @half fern would appreciate any help you could offer as I have seen you give really great advice

fallen merlin
#

bump

half fern
#

If you're going to include coursework (which I rarely advise), just group it all under courses/coursework, don't distinguish by what's planned

I'd move skills to the bottom and let your technical experience/projects speak for itself

All of your project bullets can be reduced and and made clearer. You don't have to include technologies in the bullets if they're already listed and self-evident.

  • e.g., bullet 1 -> "Developed a file compressor/decompressor that can reduce file sizes by 40%..."

Your bullets for your first two experiences are not particularly clear. I would clarify what you did and what the business impact is so that anyone can understand - even I'm having trouble trying to parse it lol

Some of your impact metrics don't seem to have a correlation (and some smell like BS e.g., "boosting team productivity by 15%" - how was this measured?), so I would work on this. I would also avoid bolding both metrics and technologies because it makes readability worse - in your case, I would just recommend sticking to bolding tech

fallen merlin
#

@half fern was able to make some updates. Wanted to hear your thoughts on the resume. Additionally, wanted to see your thoughts on if its good to diversify experience like showing leadership, hackathons. I have done these but chose not to put them

last anvil
#

june 2025 is cooked

half fern
#

Bullets in experience are still weak in the sense that you’re not communicating what your contribution is to the business - try to tell me what you did for the business (including what area of product you worked on), then expand by telling me how you did it. You’re leaning too much into tech here. Try to dumb it down as simply as you can, so that the takeaway is nice and easy to read

Diversifying experiences is an effective strategy for student pipelines yes

fallen merlin
#

Hi @half fern, thanks for the feedback. I had a quick question to see if I understand your feedback. For example for the first bullet point experience under Fortune 500, would i say something like this "Engineered a fault tolerant workflow that automates a software release process using Temporal and Java, saving engineers 2 hours weekly and $10,000 annually"

half fern
#

I rarely find the saving hours aspect compelling, you're better off just talking in terms of direct costs. Imo both the contribution and project itself feel weak, so it would help if you can explain what you did so we can brainstorm something new instead of trying to reword your bullet as-is. I don't understand where it being fault-tolerant comes into play at all, just sounds like you're pushing in buzzwords for the sake of it

If you go impact-first, it'll be easier to understand this one specifically: "Saved $10,000 annually by automating a software release process using Temporal and Java"

fallen merlin
#

I updated my description, do you think this may have better clarity of what i did.

image.png
#

I used Temporal and Java to automate a manual software release process which has numerous steps like merging PR's, modifying files, running shell scripts, etc... Since i used temporal, this means my workflow is resistant against network failures due to Temporal's features of fault tolerance, state maintainence, retry mechanisms. For example, with Temporal, if i am running the workflow with 30 steps and there is a network outage on the 27th step, instead of restarting the entire workflow and performing all the tasks again, I can continue from the point of failure with step 27. I initially talked about hours since the software release process was performed manually before my project.

half fern
#

Why was it a 30-step process, and what prompted your project?

#

Bc at a glance, it sounds like I or someone else could just scrap together a Github actions workflow doing basically the same thing within a day - to improve your point, you need to make clear what was compelling about this project

#

Not saying your work is that trivial, it's just how you're communicating it really downplays the presumed complexity and need

fallen merlin
fallen merlin
half fern
fallen merlin
#

i would say it removes the dependency and need for human interaction with the entire software release. With temporal, we are able to create a software release process system that never fails. This is due to the deterministic nature of temporal, ability to handle transient failures like high latency in API Calls, etc.. So with a manual process there is a chance of human error and the CI/CD process failing. However with the project, our deterministic nature ensures that everytime we run the workflow we are going to have the same result of a successfull release of Software where our builds pass. Additionally, in case of major outages, our workflow can preserve state which may be cost effective compared to manual process or a non-temporal workflow

#

I would say the main impact is the difference between manual work and the project would be risk of human error in messing up the process vs Temporal's workflow reliability and consistency. Additionally the software is released every week and is "required" by teams who actively use and contribute to the software which is why its important the release is delivered on a timely manner

half fern
#

The issue here is that you're not exactly explaining what's different between a normal CI/CD process at a company you're likely applying to vs this one. Why was this so impactful that you had to put it at the top?

Typically, a software release process (regardless of how extensive it is, some go on for days/weeks, even for weekly/monthly releases) is simply a process that works. Automation would be either a QoL thing or it would be a cost saver as it frees up devs/QA/product

If it takes 2 eng hours / wk to go through manual release (mind you, some places take 2 hours to even get a build pipeline running), you're saying that the opportunity cost is: $50-$100 / hr (on avg) * 2 hrs / wk * 50 wks / yr => $5-10k saved in a year. Are you saying that your (only) contribution to this company is effectively a net loss for other firms? Where they wouldn't even bother to invest eng hours because it's a QoL issue and there are other priorities at hand?

#

Rather than think about the cases you had to work around at work, I recommend digging into why it was important. Your manager wouldn't approve this project if it wasn't worth it in some regard - so you need to be able to explain the business gain more precisely. Fault-tolerance is the least of my concerns here

fallen merlin
#

Hi @half fern, wanted to hear your thoughts on the updated description

fallen merlin
half fern
#

"Automated a 30-step manual software release process using Java to cut engineering downtime by 80% and resist pipeline failures, saving $10,000 annually"