avatarZach Quinn

Summary

The article emphasizes the importance of domain knowledge for data engineers, alongside technical skills, to enhance their value and career prospects within the booming data job market.

Abstract

The article "Why Data Engineers Must Have Domain Knowledge — And How To Gain It" argues that while technical skills are crucial for data engineers, possessing domain knowledge is equally important for career advancement. It highlights that understanding the business context and industry trends can lead to more significant contributions to an organization and better job opportunities. The data job market is currently thriving, with high demand for data professionals, and having domain expertise can set candidates apart from those who focus solely on technical aptitude. The article suggests that data engineers should actively seek to understand their industry and organization to provide more precise data solutions and to align their work with the company's goals, which can lead to promotions and better external offers.

Opinions

  • The author believes that technical skills alone are not sufficient for data engineers and that domain knowledge is crucial for providing context to the technical work.
  • It is suggested that data engineers with domain knowledge can offer more value by understanding the broader business problems and driving organizational growth.
  • The article posits that domain knowledge can be a key differentiator in the job market, making candidates more attractive to employers.
  • The author advises that data engineers should engage with industry trends, internal documentation, and financial reports to build their domain expertise.
  • Engaging with other departments and asking specific, relevant questions is recommended to gain a deeper understanding of the organization's operations and goals.
  • The author encourages leveraging past work experience or seeking out resources such as professional organizations, online communities, books, and industry data to develop domain knowledge.
  • The article implies that while certifications like Google Cloud Engineer are beneficial for career growth, domain knowledge provides a competitive edge and context for a data engineer's work.

Why Data Engineers Must Have Domain Knowledge — And How To Gain It

Why developing business knowledge is as important as developing technical skills.

Amassing the technical skills and confidence to apply for and thrive in data engineering roles can feel daunting, but such a heavy focus on up skilling neglects the importance of developing domain knowledge.

Photo by Gabriella Clare Marino on Unsplash

Be the Master of Your Domain… Knowledge

If you are an aspiring data professional reading this, good news: We’re in the middle of a data job market boom. Never before have there been so many companies seeking to acquire data analysts, data scientists and data engineers. Have a little patience, some skills and shop around your offers and it’s not unreasonable to receive a six figure offer with even just a few years’ experience. However, these offers are almost entirely focused on a candidate’s technical aptitude. Corporate recruiters and headhunters scour LinkedIn with key word searches for Google Cloud Engineer or Google Analytics Certification. Earning these certifications often translate to tangible career growth and progression.

So if you’re getting job opportunities, raises and interesting experiences based off your technical aptitude alone, why should you need to know about the domain you work in?

In my experience, not possessing domain knowledge means you’re missing the larger context of the business problem you’re tasked with solving, meaning that, in the end, you’re just the one coding. Without understanding how your work drives your organization’s growth, you’re missing a crucial opportunity to be an asset to your team and raise your profile to be eligible for promotions or better external offers.

Pardon the interruption: For more Python, SQL and cloud computing walkthroughs, follow Pipeline: Your Data Engineering Resource.

To receive my latest writing, you can follow me as well.

Defining the Term

According to job aggregation site, Indeed, domain knowledge is defined as the following.

“Domain knowledge is the collection of skills and expertise specific to a particular field or industry. Instead of expertise with a single specific program or tool, domain knowledge involves a broader perspective. Someone with domain expertise knows the current state of the industry and has an idea of where it’s headed. For management positions, domain knowledge is often a crucial business skill.” — Indeed

Often when someone asks about how to break into the field of data engineering, they’re wondering what technical skills they need. While it’s true you’ll need some combination of a programming language, SQL (or a NoSQL variant) and cloud computing experience, it’s helpful to work in a domain you either have firsthand experience with or would be interested in learning more about.

Photo by Markus Winkler on Unsplash

When it comes to IT career paths, the consensus is that it’s helpful but less necessary for software engineers to possess a broader knowledge of the industry they work in. However, when you consider data-oriented roles, which typically fall under the business intelligence umbrella at most organizations, it’s essential for these individuals to have at least a foundational understanding of the business, its capabilities and its annual goals. Domain knowledge is essential for data engineers because we are often serving internal clients who make specific business requests. Understanding their department’s role in the context of the larger organization hierarchy can help data engineers pull more precise data points for clients and stakeholders. Understanding the end goal of a data consumer can even help a data engineer make suggestions (when appropriate) for how to obtain, aggregate and leverage supplemental data, which adds tremendous value to one’s role.

How to Gain Industry Knowledge — Job Seeker

Once you’ve decided which industry or industries you’d like to do data work in, you’ll want to ensure you acquire at least a foundational knowledge of the larger trends and concepts of that sector. If you’re transitioning to data science, as I was, you can leverage your previous work experience to give you an edge on candidates that might present themselves as pure technical workers. If you’re entirely new to the industry you’re entering, I’d suggest seeking out some combination of the following resources:

  • Professional organizations/trade associations. If media/advertising is your thing, then you might want to check out the International Advertising Bureau (IAB).
  • Online communities. Reddit can be valuable for some niche topics, but as a journalist I’d advise you to avoid it for serious information, since there is little in the way of verification. I’d recommend Quora.
  • Books. Try to pick something with an engaging narrative; not a dry overview.
  • Data. If you want to work in data in a particular industry, I highly suggest you find some data to play with or even use as a foundation for a project. You never know, that could be the analysis/model/pipeline that gets you hired — and you learn something about that domain in the process.

Being a job seeker looking to enter a new industry puts you in an advantageous position to learn without bias and develop an organic curiosity.

How to Gain Organization Knowledge — New Hire

Just because you’re hired as a data analyst, data scientist or data engineer doesn’t mean you can stop caring about the domain you work in. In fact, learning about an industry in the context of your organization can yield insights that can improve your day-to-day performance. Here is how I developed (and continue to develop) my domain knowledge in the first few months:

  • Read any internal slide decks/reports/documentation. If you find yourself in limbo or with a lighter workload in your first few weeks on the job, this is the time you should dedicate to reading and learning (assuming you’re comfortable with the technical aspects of the role).
  • If your organization is public or planning to go public, read SEC filings and other financial documentation. Doing so can give you a better overview of your company’s revenue earnings and how it’s positioned within the industry.
  • Write down new concepts. Taking a relative’s advice, I started a notebook on my first day on the job. I continue to jot down concepts and terms specific to the media industry that I hadn’t encountered before.
  • Ask questions. Managers and executives have a broader perspective on business operation than us technical workers. They appreciate questions provided they are specific and relevant to the business.
  • Overview meetings with other department leads. If you truly want to gain a more in-depth understanding of your chosen domain as it pertains to your organization, ask your manager if it is possible to organize overview meetings with other department leads. This could consist of an informal Q & A or a more structured presentation that provides context for how your team’s work could help theirs.

Despite the hype surrounding certifications like the Microsoft Azure Cloud Engineer and the Google Cloud engineer credentials, diligently pursuing the acquisition of domain knowledge will better distinguish you from candidates and help provide better context for your work as a data engineer.

If you’d like to support Pipeline and my Medium writing, please feel free to become a Medium member using my referral link (I receive a small commission from each individual who joins).

Data Engineering
Job Hunting
Business Intelligence
Data Science
Programming Languages
Recommended from ReadMedium