Language Selection

English French German Italian Portuguese Spanish

Reminder about Linux and resumes

Filed under
Linux

There’s a lot of uncomfortable truth to the tired old joke about the guy with ten years of Solaris experience who got turned down for a job interview because he lacked experience with Unix. What’s behind that is a simple fact: recruiters and human resources staff tend to be salespeople, not techies. Most simply don’t know that Linux is Unix or that experience with Tru64 can make learning Solaris seem trivial.

Bear in mind that most recruiters and many in-house HR departments now use automated search tools and you can see the problem. Put "Red Hat" on your resume, and you’ll be invisible to a recruiter looking for "Linux" using any of the more simple minded, and thus common, search tools.

So what can you do? Tailor your resume to text search engines that rely on simple word matches - mention every Unix variant you can reasonably claim at least once, but be prepared to justify your inclusions to a sceptical recruiter.

One resume I saw recently aced this. She had an introductory section summarizing her expertise in which she explicitly claimed hands on experience with Red Hat Linux, HP-UX, and SCO OpenServer -and pointed out that much of what she learned would apply to future work with other Unix products including Debian, Solaris, and NetBSD. Then she had supporting sections listing the employers and roles where she gained her experience and mentioned the lookalikes in each case -mentioning, for example, skill portability to Debian where she talked about the work she’d done using Red Hat.

Do a "quick Search" for a someone with Debian experience in a package like Staffsoft’s and boom - she shows up twice even though she’s never used Debian and didn’t lie on her resume either.

There are some things you should remember about this strategy. First, don’t waste time doing this in your covering letter, most agencies and HR departments throw those away before storing your resume.doc or scanning it in. More importantly, however, don’t exaggerate: remember, your goal isn’t just to get the recruiter to notice you, it’s to get the recruiter to notice you positively. Most recruiters who don’t know if technology A maps to technology B will ask a colleague or phone the employer to check acceptability. Win on that and you’re golden, lose and you won’t get a job there job no matter how often your resume pops up.

Source.

More in Tux Machines

today's leftovers

Debian and Ubuntu Leftovers

  • Listing and loading of Debian repositories: now live on Software Heritage
    Software Heritage is the project for which I’ve been working during the past two and a half years now. The grand vision of the project is to build the universal software archive, which will collect, preserve and share the Software Commons. Today, we’ve announced that Software Heritage is archiving the contents of Debian daily. I’m reposting this article on my blog as it will probably be of interest to readers of Planet Debian. TL;DR: Software Heritage now archives all source packages of Debian as well as its security archive daily. Everything is ready for archival of other Debian derivatives as well. Keep on reading to get details of the work that made this possible.
  • Canonical announces Ubuntu Core across Rigado’s IoT gateways
  • Collecting user data while protecting user privacy
    Lots of companies want to collect data about their users. This is a good thing, generally; being data-driven is important, and it’s jolly hard to know where best to focus your efforts if you don’t know what your people are like. However, this sort of data collection also gives people a sense of disquiet; what are you going to do with that data about me? How do I get you to stop using it? What conclusions are you drawing from it? I’ve spoken about this sense of disquiet in the past, and you can watch (or read) that talk for a lot more detail about how and why people don’t like it. So, what can we do about it? As I said, being data-driven is a good thing, and you can’t be data-driven if you haven’t got any data to be driven by. How do we enable people to collect data about you without compromising your privacy? Well, there are some ways. Before I dive into them, though, a couple of brief asides: there are some people who believe that you shouldn’t be allowed to collect any data on your users whatsoever; that the mere act of wanting to do so is in itself a compromise of privacy. This is not addressed to those people. What I want is a way that both sides can get what they want: companies and projects can be data-driven, and users don’t get their privacy compromised. If what you want is that companies are banned from collecting anything… this is not for you. Most people are basically OK with the idea of data collection, they just don’t want to be victimised by it, now or in the future, and it’s that property that we want to protect. Similarly, if you’re a company who wants to know everything about each individual one of your users so you can sell that data for money, or exploit it on a user-by-user basis, this isn’t for you either. Stop doing that.

OSS Leftovers

  • QMO: Firefox 59 Beta 10 Testday Results
    As you may already know, last Friday – February 16nd – we held a new Testday event, for Firefox 59 Beta 10. Thank you Mohammed Adam, Abhishek Haridass,  Fahima Zulfath A. and  Surentharan.R.A. from  India QA Community team for helping us make Mozilla a better place.
  • Bugzilla Triage Helper
    There are an awful lot of bugs filed against Firefox and all it's components in the course of a release. Keeping on top of that is hard and some teams have adopted some policies to help with that (for example see: design-decision-needed). Having a consistent approach to bugs across the organisation makes it a little easier for everyone to get a feel for what's going.
  • Alfresco Founder: Commercial Open Source is more than Old Stuff for Free
    February sees Open Source turn 20 years old. Or the OSI definition at least. According to the OSI, the term was coined in Palo Alto by nanotechnologist Christine Peterson during a meeting on February 3rd, 1998 shortly after the announcement of the release of Netscape’s source code.
  • EOH and LSD Information Technology partner to lead open source in Africa
    By identifying global trends and local needs, EOH is able to proactively source and secure capabilities that will assist with the adoption of the digital revolution. LSD’s offerings across Linux, automation, devops and containers is a great technology fit for EOH to lead open source in the market.
  • Choosing a tool to track and mitigate open source security vulnerabilities
    Continuously tracking your application’s dependencies for vulnerabilities and efficiently addressing them is no simple feat. In addition, this is a problem shared by all, and is not an area most companies would consider their core competency. Therefore, it is a great opportunity for the right set of tools to help tackle this concern.
  • Open source software: to be celebrated or cursed?
    The use of Open Source Software (OSS) has become widespread. The latest statistics show that 78% of companies run OSS, and a number of mainstream software and hardware products are based on the OSS model – for example Android, Skype [sic], Firefox, Amazon Kindle, Tivo and BT Home Hub.
  • Marshall Students Use Open Source Data to Help Stop Sex Trafficking Cases
    The work involved sex trafficking cases in Latin America, the Caribbean and Southeast Asia. Select students in Marshall’s Open Source Intelligence Exchange program worked to provide open source intelligence collection and analysis for law enforcement and other clients. Open source refers to data collection from publicly available sources.
  • Stanford scholar celebrates Western culture’s open-access tradition
    The move toward “open access” to research and scholarship, far from being a modern digital-age creation, has roots in the West that date back to medieval times, writes a Stanford education scholar. John Willinsky’s new book explains how learning has long benefited from efforts to increase its circulation.

Events: OpenStack Summit Vancouver, IBM Index, Eclipse CheConf 2018

  • OpenStack Summit Vancouver '18: Vote for Speakers
    The next OpenStack Summit takes place again in Vancouver (BC, Canada), May 21-25, 2018. The "Vote for Presentations" period started. All proposals are up for community votes. The deadline for your vote is will end February 25 at 11:59pm PST (February 26th at 8:59am CET)
  • IBM Index: A Community Event for Open Source Developers
    The first-ever INDEX community event, happening now in San Francisco, is an open developer conference featuring sessions on topics including artificial intelligence, machine learning, analytics, cloud native, containers, APIs, languages, and more.
  • Eclipse CheConf 2018 – Join the live stream February 21st at 10 am EST
    2017 was a fantastic year for the Che project, with more contributors, more commits, and more usage – this solidified Che’s position as the leading developer workspace server and browser IDE. Eclipse Che users logged over 7 million hours of public Che usage (plus more in private installs). We’ll discuss the growing cloud development market, Che’s position in it, and the exciting changes we’re planning for 2018.