blog post about DE cv

docs/website/blog/2023-09-20-data-engineering-cv.md

@@ -0,0 +1,102 @@
+---
+slug: data-engineering-cv
+title: "How to write a data engineering CV for Europe and America - A hiring manager’s perspective"
+image: /img/dall-e-de-cv.jpg
+authors:
+  name: Adrian Brudaru
+  title: Open source data engineer
+  url: https://github.com/adrianbr
+  image_url: https://avatars.githubusercontent.com/u/5762770?v=4
+tags: [data engineer, cv]
+---
+
+I recently reviewed someone’s anonymized CV on Reddit as they complained they applied to dozens of jobs but never heard back. Shortly after, my inbox blew up with review requests.
+
+My experience comes from 10+ years in the industry, and having reviewed thousands of CVs myself, having hired for multiple companies. I also asked the opinion of other hiring managers who have hired data engineers.
+
+Why Europe and America? Because, in my experience, other parts of the world work more in enterprises with different tool sets. They often do “outsourcing” work, often on technologies used 5-20 years ago and less modern techs. Even when the tech used is new, the role is usually very limited in an enterprise and generally lacks the end-to-end capabilities requirement. For example, it might mean doing drag and drop tools + sql stored procedures, or it might mean doing only data loading without architecture and generally without an orchestrator, etc.
+
+So, let’s cut to the chase - what is a hiring manager looking for in an application?
+
+### Cover letter
+
+Let’s start with the shortest bit - cover letter - definitely write one. If you apply by email, put it in the email body. If not, attach it to the application.
+
+What should it contain? A couple of paragraphs about
+
+- Why this company you are applying for is interesting to you
+- Your motivation for applying and what you hope to achieve here
+- Why you would be a good fit for the role.
+
+Keep it honest. Write about the role and your intent, do not make it about you.
+
+A definite **don’t** is a generic letter that talks about you, but doesn’t mention the role or company - this shows a lack of investment in the application and gives wrong signals, so if you cannot review the company and say why you like it, then the reviewer might feel the same way about you.
+
+### The CV
+
+Rules of thumb
+
+- Space is your friend. It drives focus to what matters. Don’t fill it with junk.
+- “Soft skills” - show the human behind the role, and have a bio section that should contain info about you.
+- Focus shows consideration to the reviewer. Tell me what’s relevant.
+- If you are junior, demonstrate potential: list your initiatives, learning, etc.
+- If you are senior, demonstrate results: focus less on techs and more on outcomes.
+- Use a two-pager if you can. First page - everything else. Second page: your experience. If you do not have experience, stick to a one-pager. If you are in the US, you might be required to use a one-pager in which case make your job descriptions shorter and more focused, dropping the non-relevant.
+
+### The parts
+
+1. Bio: Name, where you come from, your values.
+    - Image. You are a human talking to a human, don’t make it less - it doesn’t help. Be confident, friendly, smile.
+    - “Values” Your [values](https://en.wikipedia.org/wiki/Values_(Western_philosophy)) are a significant predictor of your “direction” - behavior and interactions. List the top 3, not more. No BS.
+    - “Motivation”  indicates what is the fuel to your fire so the company knows if they can do that for you. One sentence.
+    - “Mission” or what you are looking to do, indicates if your goals may align with role goals. One or two sentences max.
+
+1. Skills:  The easiest thing to filter on, so list the relevant skills for the role you are applying. Do not list the entire list of something you have ever used or tried - this only creates noise and the impression that you don’t have any practiced skills. Mention the skills that are relevant first, and consider skipping the rest. For example: “Python, SQL, orchestrator, GitHub, others.”  instead of “Java, Javascript, ruby, go, R, C++, SQL, python, tableau, excel, looker, big query, bash, basic, assembly, MsWord, google sheets, PowerBI, ” Make sure those skills are clearly displayed and optionally also mentioned in the listed jobs so people can judge how much you used them.
+
+    You can personalize the list based on the job you apply for. If skills are listed outside the job description, look at who else works or worked there, they might list the tools or skills on their LinkedIn.
+
+    If you are starting out and need to gain the skills, make them happen. Take a course, learn them, and list them.
+
+2. Job experience. Format:
+
+    <aside>
+    💡 Time-Time Company, Role.
+    At the company, I had a role that focused on delivering XYZ in a context. I worked with A, B, and C technologies.
+        - I achieved X
+        - I also built Y
+        - I am pleased about having done Z
+
+    </aside>
+
+    What are we presenting? The context (company, team), the achievements (X, Y, Z), the takeaways (A, B, C, X, Y, Z experience)
+
+    What are we **not** presenting? Things are irrelevant to the role we are applying for or our values. Less is more as it shifts focus to the important. Also, no vanity achievements or internal company awards, which are often offered in consultancies - these are just tools to motivate you, and nobody cares externally.
+
+3. Education: Studies, self-studies. Some groups care about the school. It is less important, as the school does not teach real-life data engineering, but it will help you understand where you come from.
+4. Projects, courses, volunteering. I care more about the demonstrated learning experience. I want to see that you keep learning - if not on the job, then I want to see courses or projects here. Volunteering also paints a picture of a “doer”.
+
+### The skills you need
+
+This depends on the role, but most DE roles building standard platforms need the following:
+
+- Python
+- orchestrator (Airflow usually)
+- dimensional modeling and other data architectures
+- SQL
+- software best practices - versioning, cicd, testing, etc.
+
+### And the magic sauce…
+
+… goes into the food, keep it out of the CV :) There’s no magic here, just clear communication.
+
+Your three levers are
+
+- Better communication
+- Better skills
+- More applications
+
+The rest is a matter of opportunities, depending on your location and the job market. If the opportunities are not available to you, consider entering the field via an adjacent role like an analytics engineer.
+
+Screening CVs is a rapid process, so you need to ensure you check off the requirements while removing (not adding) any doubts. Any hire is a risk, so the screener wants to minimize that - help them do it by showing a good understanding of your role and what is expected of you. Don’t add info that isn’t needed, as that might add doubts.
+
+I wish you good luck on your application process and encourane you to ask for feedback from the community if you get stuck.