4 tech jobs for people who don't code | Opensource.com

4 tech jobs for people who don't code

There are many roles in tech for people who aren't engineers. Explore some of them in part 2 of this series.

Looking at a map
Image by : 

opensource.com

x

Subscribe now

Get the highlights in your inbox every week.

In the first article in this series, I explained how the tech industry divides people and roles into "technical" or "non-technical" categories and the problems associated with this. The tech industry makes it difficult for people interested in tech—but not coding—to figure out where they fit in and what they can do.

If you're interested in technology or open source but aren't interested in coding, there are roles available for you. Any of these positions at a tech company likely require somebody who is tech-savvy but does not necessarily write code. You do, however, need to know the terminology and understand the product.

I've recently noticed the addition of the word "technical" onto job titles such as technical account manager, technical product manager, technical community manager, etc. This mirrors the trend a few years ago where the word "engineer" was tacked onto titles to indicate the role's technical needs. After a while, everybody has the word "engineer" in their title, and the classification loses some of its allure.

As I sat down to write these articles, this tweet from Tim Banks appeared in my timeline:

This follows the advice in my first article: Tim does not simply ask about "non-technical roles"; he provides more significant context. On a medium like Twitter, where every character counts, those extra characters make a difference. These are technical roles. Calling them non-technical to save characters in a tweet would have changed the impact and meaning.

Here's a sampling of non-engineering roles in tech that require technical knowledge.

Technical writer

A technical writer's job is to transfer factual information between two or more parties. Traditionally, a technical writer provides instructions or documentation on how to use a technology product. Recently, I've seen the term "technical writer" refer to people who write other forms of content. Tech companies want a person to write blog posts for their developer audience, and this skill is different from copywriting or content marketing.

Technical skills required:

  • Writing
  • User knowledge or experience with a specific technology
  • The ability to quickly come up to speed on a new product or feature
  • Skill in various authoring environments

Good for people who:

  • Can plainly provide step-by-step instructions
  • Enjoy collaborating
  • Have a passion for the active voice and Oxford comma
  • Enjoy describing the what and how

Product manager

A product manager is responsible for leading a product's strategy. Responsibilities may include gathering and prioritizing customers' requirements, writing business cases, and training the sales force. Product managers work cross-functionally to successfully launch a product using a combination of creative and technical skills. Product managers require deep product expertise.

Technical skills required:

  • Hands-on product knowledge and the ability to configure or run a demo
  • Knowledge of the technological ecosystem related to the product
  • Analytical and research skills

Good for people who:

  • Enjoy strategizing and planning what comes next
  • Can see a common thread in different people's needs
  • Can articulate the business needs and requirements
  • Enjoy describing the why

Data analyst

Data analysts are responsible for collecting and interpreting data to help drive business decisions such as whether to enter a new market, what customers to target, or where to invest. The role requires knowing how to use all of the potential data available to make decisions. We tend to oversimplify things, and data analysis is often over-simplified. Getting the right information isn't as simple as writing a query to "select all limit 10" to get the top 10 rows. You need to know what tables to join. You need to know how to sort. You need to know whether the data needs to be cleaned up in some way before or after running the query.

Technical skills required:

  • Knowledge of SQL, Python, and R
  • Ability to see and extract patterns in data
  • Understanding how things function end to end
  • Critical thinking
  • Machine learning

Good for people who:

  • Enjoy problem-solving
  • Desire to learn and ask questions

Developer relations

Developer relations is a relatively new discipline in technology. It encompasses the roles of developer advocate, developer evangelist, and developer marketing, among others. These roles require you to communicate with developers, build relationships with them, and help them be more productive. You advocate for the developers' needs to the company and represent the company to the developer. Developer relations can include writing articles, creating tutorials, recording podcasts, speaking at conferences, and creating integrations and demos. Some say you need to have worked as a developer to move into developer relations. I did not take that path, and I know many others who haven't.

Technical skills required:

These will be highly dependent on the company and the role. You will need some (not all) depending on your focus.

  • Understanding technical concepts related to the product
  • Writing
  • Video and audio editing for tutorials and podcasts
  • Speaking

Good for people who:

  • Have empathy and want to teach and empower others
  • Can advocate for others
  • Are creative

Endless possibilities

This is not a comprehensive list of all the non-engineering roles available in tech, but a sampling of some of the roles available for people who don't enjoy writing code daily. If you're interested in a tech career, look at your skills and what roles would be a good fit. The possibilities are endless. To help you in your journey, in the final article in this series, I'll share some advice from people who are in these roles.

question mark in chalk

Dividing people into "technical" and "non-technical" labels harms people and organizations. Learn why in part 1 of this series.
Dandelion held out over water

There are lots of non-code ways to contribute to open source: Here are three alternatives.
Women talking

As organizations mature their DevOps practices, it's time to make the technical writer a bigger part of the team.
community team brainstorming ideas

Effective project management can mean the difference between a project thriving or lagging.
A football field.

A community manager is like a quarterback, ensuring things run smoothly and everyone on the team has the chance to grow.

Topics

About the author

Dawn Parzych - Dawn Parzych (@dparzych) is a Developer Advocate at LaunchDarkly where she uses her storytelling prowess to write and speak about the intersection of technology and psychology. She enjoys helping people be more successful at work and at life. She makes technical information accessible avoiding buzzwords and jargon whenever possible. Dawn has spoken at DevOpsDays, Velocity, Interop, and Monitorama. Her articles have appeared in numerous technical publications. In her freetime she serves as a...