About to Graduate Masters in Computer science with no offers

[hardy surge]

I’ve applied for 1,500 roles with no interviews. Please review my resume to help me identify and fix any issues. any help will be apricated

[hardy surge]

bumping up

[dense rapids]

@hardy surge Your Data Engineer experience is how your intern work experience should also look like. It seems clear as to what you did, how you did it and the resultant impact it had.
-> Reorder sections most recent comes first, such as:
EDUCATION -> EXPERIENCE -> PROJECTS -> SKILLS-> CERTIFICATIONS(make this section concise, use pipe(|) symbol to put them in 1-2 lines, they take up too much space.)

1. I’d remove the summary section.

• Express it through your work experience bullet points.

2. Talk about the actual work you put in with the technologies you used in the Intern experience instead of simply listing a bunch of technologies.
3. Make it more concrete/specific as to what you did with those technologies. Right now it’s just a bunch of keywords without explicitly stating what was done through those technologies.
4. PROJECTS:

• The first projects’ first bullet point is redundant, it’s already stated “Leader Election and Log Replication” you don’t need to restate it again in the result/impact - just say enabling fault-tolerance across a network of [X number] of containerized nodes…
• Fix capitalization in the second point of the first project, no need to capitalize after the first(action verb), mention the took you used for testing there.

Use GPT something like this below, if it helps:

• You are an expert resume writer with over 20 years of experience working with job seekers trying to land a role in tech.

• Here's a bullet point I have in my resume no action needed for now if you understand please respond with "Yes".

• Here's my bullet:
 <Insert Bullet>

• GPT: Yes.

• Rewrite this bullet point using this structure: "I accomplish X by the measure Y that resulted in Z"

• For example, "I lowered hospital mortality rate by 10% by educating nurses in new protocols which translates to 200 lives saved per year"

• Use compelling language and keep the bullet point within 35-50 words

• GPT: …

• I don't know how metrics/success was measured. Please give me suggestions where and how I can add quantifiable metrics in this bullet.

• GPT: ….

Remove Extracurricular section.

• Adjust EDUCATION section dates with just months. For present imo change it to Expected: May 2025 or Expected Graduation: …

PROJECTS SECTION:

• Project 2:

• Repetitive usage of action verb across both points, use different strong action verb for #2.

• Check out an example provided by Claude below:

Distributed Consensus System (2024):
• "Engineered fault-tolerant consensus by implementing Raft algorithm, demonstrating successful leader election across 5-node clusters with simulated network partitions and node failures"
• "Built client-server architecture by implementing gRPC streaming, achieving consistent state replication across nodes with automated recovery from 3+ failure scenarios"

No-Code Data Pipeline Creator (2023):
• "Developed no-code ETL platform by integrating PySpark with GCP services, validating 20+ transformation workflows across structured and unstructured test datasets"
• "Strengthened data pipeline security through OAuth 2.0 and chunked uploads, enabling secure processing of datasets up to 10GB with automatic retry mechanisms"
• "Automated testing workflow by implementing GitHub Actions CI/CD, achieving 90% test coverage and reducing deployment time from 30 to 5 minutes"

Scalable Image Classifier (2021):
• "Built scalable ML system using AWS auto-scaling, handling 50 concurrent classification requests while maintaining <200ms latency in load tests"
• "Enhanced system reliability through SQS queues and loose coupling, demonstrating zero message loss across 1000+ test events during component failures"
• "Streamlined cloud infrastructure using AWS CDK, reducing 1000+ lines of configuration to 200 lines of type-safe infrastructure code"

Text Summarizer (2020):
• "Enhanced text summarization by implementing custom APES metric with Pegasus model, improving ROUGE scores by 15% on standard NLP benchmarks"
• "Designed scalable architecture using microservices, demonstrating stable performance under 3x load increase in stress testing scenarios"

=====================================

Here’s a concise version per Claude:

Distributed Consensus System (2024):
• "Engineered fault-tolerant consensus using Raft algorithm, enabling successful leader election in 5-node clusters during network failures"
[Shorter but keeps: What (consensus), How (Raft), Impact (survived failures)]

No-Code Data Pipeline Creator (2023):
• "Built no-code ETL platform integrating PySpark with GCP, enabling non-technical users to create 20+ types of data transformations"
• "Implemented OAuth 2.0 and chunked uploads for secure 10GB+ dataset processing with auto-retry capabilities"
• "Automated deployments via GitHub Actions CI/CD, achieving 90% test coverage and 6x faster deployment cycles"
[Removed redundant technical details but kept core achievements]

Scalable Image Classifier (2021):
• "Built auto-scaling ML system on AWS handling 50 concurrent requests at <200ms latency"
• "Implemented SQS queues for service communication, achieving zero message loss across 1000+ test events"
• "Reduced infrastructure complexity using AWS CDK, cutting configuration code by 80%"
[Much shorter while retaining key metrics]

Text Summarizer (2020):
• "Enhanced Pegasus model with custom APES metric, improving ROUGE scores by 15% on standard benchmarks"
• "Deployed microservice architecture demonstrating 3x load handling in stress tests"
[Removed technical jargon but kept measurable impacts]

-> Now when you look at these above:

• They are almost 1/2 as shorter and yet clearly demonstrate the work done with impact.

• They maintain a clear what/how/impact structure, like a cause-effect of your tasks.

• The focus should be primarily on key achievements, since your resume is ideally supposed to be a highlight/elevator pitch of your achievements/accomplishments.

• Your bullets should avoid redundant technical terms.

• Try inserting quantifiable metrics but only where you can not necessarily in every point, the last point above in Text Summarizer project provided by Claude is decent and can be used as:

• Deployed a clean microservices architecture capable of handling 3x load in stress tests or something like that.

[hardy surge]

Thanks @dense rapids , Really appreciate the feedback

[hardy surge]

@dense rapids heres anew version based on your comments let me know hat you think about it , is it too verbose ??

[restive pike]

quantify these, you state the impact but have no number

dumb down ur descriptions in general and clearly state the business/customer-level impact of your techy solution, first person reading ur resume is HR not an engineer

overall tho projects r super cool and ur experience is solid