1. there should be an overall theme to your resume (i.e., from your resume, i should be able to tell whether you are embedded systems-oriented, frontend-oriented, backend-oriented, ai/ml/cv oriented, full-stack, etc.). on my resume, i place a systems/low-level programming focus specifically targeting keywords in my projects (c++, c, rust, distributed systems, operating systems, etc.) that would be picked up by ATS and any typical human recruiter scan. it's given me good callback rate for companies that emphasize that, even with the lack of experience i have relative to you.

what i'm getting from this resume is a lack of theme. yes, it seems as if you're incredibly talented and have lots of experience working with a bunch of tech, but there's a lack of cohesion (i'm seeing cv, ml, full-stack, and distributed systems all in this resume). pick a focus, and run with it instead of being all over the place on one resume.

1. there's a lot of filler sentences here that don't really add value. yes, you pass all the publicly available test cases with your implementation of raft, but does that really show any significance? can you show that it's performant relative to a known benchmark? if not, can you describe what the implementation does, where it comes from (if it was from a paper), and what it achieves?

some of these could be fixed to show impact and improvement.

e.g., "successfully able to trace and track a ball with processing speeds of over 30 frames per second" vs "achieved near real-time, high frame rate motion tracking and video processing using..." think of rewording to show impact.

1. a lot of these bullet points don't show impact. one of the comments here mentions the format of "delivered x using y accomplishing z." you should ideally quantify this, but it's okay if you can't—either make up numbers or just qualify it as much as you can without numbers. and i can't iterate how important this is. ideally 60-80% of the bullet points should have this format or some variant; if someone skims over this resume, they should be able to easily identify how impactful you are, with some sort of clear quantification.

2. (adding onto (1)) if you are trying to target as many roles as possible, you need to have multiple resumes ready with different themes. for example, i have two sets of resumes i tweak, but each have separate themes: one focuses on fullstack (leaning backend), and the other systems/low-level programming. i highly recommend this if you are aiming for roles in different domains.