Lessons from a brief career in open source

Lessons from a brief career in open source

Two hands holding a resume with computer, clock, and desk chair
Image by : 

Subscribe now

Get the highlights in your inbox every week.

I don't think many people answer the question "What do you want to be when you grow up?" with "I want to work in open source."

In my experience, working in the open source community is something that happens as a result of something else. I worked in open source for a short time—in fact, the mission statement of the company I worked for included the words "open source." But my path to that job was not direct and not as laser-focused as one might think.

Big decisions

I had worked my entire life in graphic design, then later in life, I began to think about my career options. Should I continue in graphics or try something else? I have a bachelor's degree in Communications, and getting a Master's degree in the same field seemed redundant, so after much thought, I decided on pursuing a Master's degree in Cybersecurity and Computer Forensics. I chose to earn my degree at Utica College.

At this point, I had no thoughts on open source and didn't even know what it was. I wasn't exposed to open source software and open source intelligence until we got into the "meat" of the program. I was intrigued by this open source thing. We had to create virtual machines with Linux to do our coursework and "compile" stuff and become a "superuser." I had purchased a cheap Asus laptop with Windows 7, thinking that would be enough. It was for some things, but I later wiped Windows out of existence and installed Linux. Much better.

One of the cool things about open source is that once you get into it you get hooked on it. You just want more of it, and you want to explore all that open source offers. This is quite unlike working with Windows or Macs, where you just curse at them. Open source creates a special bond between the software and the user.

The search begins

Once I earned my degree, I began looking for jobs. It was a bit frustrating. I did not have security clearance, and I was not a kid anymore. These seemed to be some big stumbling blocks.

I explored opportunities primarily on Indeed.com, and used other job sites, like CareerBuilder.com, Monster.com, HigherEdJobs.com, ZipRecruiter.com, and others. LinkedIn.com is also a good source for job postings, learning about a company's work in open source, and learning about a company's employees.

I wasn't making much headway in the cybersecurity field or in computer forensics. However, I did notice that many postings used words like "Linux" and "open source." I thought that might be a better path to take. So, I enrolled in several free, online courses to improve my skills and to build my credentials. You can find free courses at Cybrary.it, edX.org, and others. I have since been certified in Linux, Java, HTML, e-marketing, Google Analytics, and even FEMA emergency response.

All online and all free.

Does all that matter? Who knows? However, you can add these to a resume, and your work does show that you are making the effort to learn the craft before taking a job in it.

Local candidates only

I saw a job posting on Indeed.com for an entry-level Linux administrator. I read the job description and knew I was totally unqualified for it. In addition, the company specified it wanted local candidates only. I lived about 1,000 miles away. Of course, I applied.

Shortly after applying, I received a call from the company. I didn't have the skills and I didn't live anywhere near them. Neither of those were a problem for them as I could learn the skills and move closer. Since I had no applicable skills I would have to take a test. The test involved using certain open source programs, GitHub, Linux, and documentation. I had no idea what the guy was talking about, but I accepted the challenge and got down to the task.

I did some research, downloaded what I needed, created a GitHub account, and performed the required task. Apparently, I completed it correctly. I was offered the job. I was now working in the open source community and using some of the skills I learned in my Master's program.

Unfortunately, my job was eliminated four months later and outsourced overseas. Disappointing, of course. I have since returned to graphics, but I continue to be intrigued by open source and continue my research and writing on the subject.

Keeping it real

My advice to anyone seeking employment in open source is to embrace all that open source has to offer. Take advantage of all the free training and certifications available. Try different specialties in the open source world: graphics, business, databases, education, and so much more.

Look for positions that may seem only to touch on open source. Go ahead and apply to positions you know you'd be good at even though the job description may seem beyond you.

Keep your eyes open to the realities of the job market. Technology trends can change. Companies move or go out of business. Be flexible, be aware, and never stop learning.

I found that job descriptions and expectations change as employers and candidates get to know each other's strengths. This pretty much epitomizes what open source is all about: open, collaborative, and flexible.


About the author

Jeff Macharyas - Jeff Macharyas is the Director of Marketing at Corning Community College in New York. He is a writer, graphic designer and communications director who has worked in publishing, higher education and project management for many years. He has been the art director for Quick Printing, The American Spectator, the USO's OnPatrol, Today's Campus, and other publications as well as a telephone pole design engineer contractor. Jeff is certified in Google Analytics and Adobe Visual Design and holds...