- (+44) not needed
- Profile and other headings a bit big. could reduce so total length of doc is smaller
- profile is very good, just maybe a bit long (nitpick)
- *constructing an/a ETL pipeline
- developed a full automated … -> ‘full’ could be removed
- iterating through -> iterating with
- with the bullet points it feels like you want to have one sentence but multiple line worth of stuff to say. this defeats the purpose of both and just makes it hard to read. do a paragraph or many small single line bullet points
- ’~ 10%’ ur already on a new line just say approximately
- would recommend you bold the tech used
- ik you dont have the most data engineering experience but if you can do make it sound more data engineer like. you seem like a multi talented guy which might be what theyre looking for so whatevers best
- relevant modules should be after the degree and maybe in italics or something to highlight it
- skills at the end - not a fan as they should be highlighted either in the experience first and if not in there then you can have them there - no redundancies i.e python sql
- you have skills in precision and recall - yh i have a phd in html
- gives the vibe of just listing technologies
- learning is a good field to have but ideally you would already be doing something in this i.e in a project. docker is an easy one to include - just say you plan to containerise your applications, host them on a server etc
- cant talk for the specific tech stuff as idek
rating 7/10 - thats like 4 std