#Looking for 2025 summer internships, any feedback greatly appreciated
1 messages · Page 1 of 1 (latest)
this resume basically is what my article should answer
basically ur bulletpoitns arent well written imo
u just say the end result + some number usually
Ex.
• Developed new shopping cart feature using Python Django for farmers to manage bulk orders, boosting sales by 25%
Like me saying:
I used react to build a dashboard. made numbers go up by 25%
cool? i guess
Thank you Justin for your feedback! I had originally written the bullet points for a non-technical audience, but after reading your article, I understand why there needs to be more emphasis on technical capabilities.
Regarding the bullet point you mentioned: "Developed new shopping cart feature using Python Django for farmers to manage bulk orders, boosting sales by 25%"
Would it be better to say something like this: "
Developed a Python Django shopping cart feature that streamlined bulk order management for farmers. The challenges involved optimizing backend API performance using SQL database indexing, handling large datasets for order management, and implementing real-time inventory tracking"
Too long the latter one.
Maybe something like:
Developed a bulk inventory management system for farmers by implementing new api routes, reindexing our sql database for performance, and implementing real time inventory tracking.
Could adjust it
but hope can see lots useless words
Can cut to the core faster
Can maybe expand on it later points such as
- Implemented real time tracking by xyz xyz xyz
@lime marlin Thank you so much! I really appreciate the feedback and take it as a gift.
What would you say is the experience that stood out the most to you, and which experience would you say needs the most rewriting?
Ur first experience stands out to me, and all experiences need rewriting
Its all too simplistic
@lime marlin Thank you so much for the feedback! I have rewritten my resume to address your feedback and have attached it to this message.
More specifically, I have added more technical details for each bullet point to answer the "how". These are examples of challenges I have faced (e.g. optimizing API performance, ensuring data consistency, ensuring real time updates, securing access to API)
Would you say this on the right track?
like even just looking at the bulletpoint that i stated, all you have there is still
"Developed a bulk inventory management system using [tech], boosting sales"
What if i just wrote:
I wrote a react homepage that boosted sales by 100%?
do u know if im a good or a bad dev?
My point is that I still have zero clue are u a good or bad dev, cause all you say is:
I use some technology that resulted in some X number of improvement
I can say:
I use react that resulted in 100% faster page load
I use python to analyze millions of data points
I use google auth and jwt to increase sign up?
Like okay? and what?
some ur bulletpoints dont even make sense, how does google auth and jwt tokens increase sign up for ex?
right?
ur numbers are just don't make any sense + ur bulletpoints basically are the same as before
how about I remove the numbers first, if that is what is bothering you?
It's not what is bothering me
it just ur numbers are random + ur bulletpoints are unimportant
What in ur resume would u consider important bulletpoints?
to show me who u are as a dev
The only thing I get is, u can use some framework, but nothign about "why is this important" nor how u did it
with some framework
My original idea was to have a high level description of the feature I built, why I built it in the first bullet point for each experience.
For the subsequent bullet points, I expanded more upon the "how" and the technical challenges.
That is okay, but u dont do that right now either
or i guess, it's like just feels like u state
i use tech
is what i mean
Ex.
I developed an inventory management system that lead to XYZ % of reduction.
I implemented a backend API route + microserviecs
Secured them with JWT token
Added a database
^Right? Like above i'd question? okay? it seems unimportant
It like ur almost stating the pure obvious
What did I get from you as a dev?
Would you say this bullet point is closer to what you want
• Optimized SQL database query performance by creating global secondary indexes, reducing webpage load time by 20%
Yes
is closer
but i think it still, hm.
not quite
let me think how
Yeah, i think this is fine actually.
Just I feel that this is a bit weird. Also, what sql database are u using?
i didnt know u could do global secondary indexes on a sql database?
sorry I meant secondary index, not global
I wish it was more like:
- Reduced query time by X% by creating global secondary indexes to fit our data access patterns from our backend servers.
I guess this just shows a bit more of the "insight" necesasry when creating a global secondary indexes
I guess the problem is "optimized" by creating an "index" is so vague
but overall minor critique
u are right this is more of what i would like to see
I really appreciate your insights and perspective from a more technical point of view.
I was wondering how would the bullet points likely be perceived from someone who is non-technical
I guess this just means who is your reader? Imo it is to write more on the technical side, than for the lay person
I assume a recruiter
My goal is to optimize that Im a decent dev
🤷, tbh i think this is just a matter of perspective.
I think end the day, a senior dev / someone technical will read ur resume
and a recruiter will barely look at it
for even 10 seconds
i find that most the time u can get through resume screening just having enough technical words
and really only drilled down later
so my goal is to the technical reader reading it that im a decent junior dev
and not to just put in random numbers, and styles that i think was adapted from a more finance / business background
tradition
since finance / business students / industry > anyone non-technical, their perspective is just impact, and numbers, since no one questions
how did they do it + do they have the skill
but if someone in a tech company reads ur resume, they might question? wait? does this guy actually know react / react native? so on
That's a good point. So you are saying we should write the resume as if a senior dev will be reading it thoroughly?
Not throughly, but they will "scan it"
Hmmm
Interesting
I was under the impression that a recruiter will be the one who determines if a resume passes screening
tbh, i dont think anyone reads the resume screening xD
😆
but that just my opinion
it feels ive seen "basic resumes" pass through
Regarding the impact, I was told by several recruiters to include numbers and demonstrate "business impact."
Would you say my resume is an example of a "basic resume."
Numbers aren't bad, but u over do it
i would consider it below basic
b/c i dont know who are even in a technical sense other than i got spammed with random numberse
that dont make contextual sense
a basic resume id say is literally could just talk about CRUD and prove to me ur an okay dev
You are point #3, where you got told to put numbers, and put numbers everywhere
(And again) why should I care about these numbers? Right? Why is it important
I'll remove some of the numbers that do not make contextual sense.
What is your opinion on these bullet points
• Implemented real-time inventory tracking, integrating WebSocket for live updates and Redis caching for fast data retrieval
• Enhanced e-commerce transaction accuracy using PostgreSQL data aggregation and subqueries to ensure data consistency
I tried to at least state the purpose of the technologies I used and why/how I used them
Yes
agree
is a lot better those points
cause there is context
relative to the other ones
• Implemented real-time inventory tracking, integrating WebSocket for live updates and Redis caching for fast data retrieval
This one could adjust a bit by doing:
Implemented real time inventory tracking by integrating ...
rather than a random comma
I originally tried doing the "by integrating" but the text exceeded one line.
This leads to almost an entire line being wasted on my resume (dangling newline)
I guses the other thing is when I read:
• Enhanced e-commerce transaction accuracy using PostgreSQL data aggregation and subqueries to ensure data consistency
I do wonder, why does this ensure data consistency
It is a good "sentence" in that ik u can do postgresql
i guess i wonder what it means accuracy through aggregation and subqueries
isn't the postgresql already the state of truth?
what are you syncing to?
great question!
I used subqueries to perform complex data validations and checks within the database, ensuring that the data remains consistent and free of anomalies. While PostgreSQL is the source of truth, these techniques help maintain data integrity and accuracy through validation.
also interested to hear your thoughts on this bullet point
• Deployed 10+ services onto AWS EC2 using Docker for containerization and CI/CD pipelines for reliable delivery
I intend to demonstrate my ability to deploy (ship) software to the end user using cloud computing technologies such as AWS/Docker. I tried to be more specific regarding the purpose of each technology being used in order to demonstrate my technical knowledge.
@lime marlin
I am planning to revise the second bullet point of my first experience (at the bank).
Does this bullet point go into more depth about technical details?
• Developed microservices to aggregate login data from web and mobile platforms and better detect unusual login activity.
One of the major challenges I faced was that the login data for different platforms (mobile,web) came from different sources (different Kafka topics).
The challenge was to combine these data into a unified source so the user can easily view their login history and detect any unusual activity.