Skip to main content

Picture Yourself Where You Want To Be

I recently received this marketing communication from LinkedIn, featuring a YouTube video. The video shows children talking about what they want to be when they grow up, and they are juxtaposed against images of successful professionals doing those things. The message is that you can follow your dreams and succeed. It's cute.

LinkedIn marketing communication promoting
http://imagine.linkedin.com

The website accompanying the campaign goes on to explain how some of the professionals featured in the video use LinkedIn to do their current jobs. For example, a chief merchandising officer uses it to discover vendors for unique items. And that's it: end of communication.

What I find interesting is that LinkedIn isn't set up very well for people trying to "follow their dreams". I've worked hard to grow my capabilities. I average two hours per day studying work-related topics to expand my reach. For my career, the signal-to-noise ratio on LinkedIn is mostly noise.

I get lots of contacts from tech recruiters based on my current and previous job titles. The pitch is often a form letter inviting me to take the same job title or an equivalent position. Some recruiters pitch positions where I would take a large pay cut, a more junior title and relocate at my own expense across the country to a more expensive area. I really like my current position, so my next one definitely won't be a lateral move!

"Technology recruiting is broken, and LinkedIn is positioned to fix it." 

Leveraging the enormous volume of career and skills data, LinkedIn could build a model that predicts how people progress in their careers. With such a model, the system can predict the most-likely career outcomes for each user. Based on feedback from the user, and on changes to the user's profile and network over time, the predictive model could be continuously adjusted.

For professionals using the site, this means the system can provide meaningful guidance about career options and how to build necessary skills for success. This could tie in with LinkedIn's recent focus on building informative content by pointing users to relevant articles, topics and groups. This capability would engage users between their job transitions, which is traditionally difficult for career sites:

"Users disengage when not actively looking for a job: most career sites are useless during stable employment."

On the recruiting side, a data-driven approach moves recruiters away from simplistic keyword-based searches that dominate current practices on LinkedIn. Some skills are easier to learn than others. For a strong software engineer, improving communication skills is hard but learning a new programming language is not. Recruiters often misjudge critical success factors for openings they represent.

LinkedIn can help recruiters understand which skill profiles can transition into the skill profiles the employer is looking for. This gives focus for recruiters and improves the resulting in-mail quality for the rest of us.

This marketing communication plays on the idea that LinkedIn enables its users to follow their dreams. By building the right data models, this vision could come closer to reality.
Labels:

Comments

Post a Comment

Popular posts from this blog

ReactJS, NPM and Maven

I'm just starting to get into working with ReactJS, Facebook's open source rendering framework. My project uses SpringBoot for annotation-driven dependency injection and MVC. I thought it would be great if I could use a bit of ReactJS to enhance the application. If you're looking for a basic conceptual intro, I recommend ReactJS for Stupid People and of course the official documentation  is quite good. In full disclosure, I still have no idea how to do "flux" yet. As an experienced Java backend developer, I'm pretty decent at hacking Maven builds - which is precisely what this blog post is going to be about. First, a word about how React likes to be built. Like many front-end tools, there is a toolkit for the node package manager (NPM). From the command prompt, one might run npm install -g react-tools  which installs the jsx command. The  jsx  command provides the ability to transform JSX syntax into ordinary JavaScript, which is precisely what I want...
21 comments
Read more

AWS S3 versus CloudFront Performance

Yesterday I took Amazon CloudFront for a spin. Creating the CloudFront distribution was pretty simple - the wizard process flowed nicely. I found myself relying on the help text in places, but the most surprising thing was how long it took for the distribution to become enabled. I didn't time it exactly, but I probably spent 45 minutes waiting for my new CloudFront distribution to change from "In Progress" to "Enabled" status. The performance is a bit confusing. Compared to the S3 bucket, I didn't see any improvement in performance in a few tries - in fact, the CloudFront CDN performance was worse than the S3 bucket on its own for my 217 KB image file. I decided to take a larger sample, loading the same image 30 times in Chrome and noting the timing data from the "network" tab in the developer tools. I'm located in Brooklyn, have CloudFront configured for the US/Europe with download mode configured. My S3 bucket is in the US Standard zone, w...
Post a Comment
Read more

IntelliJ Annotations and Maven

IntelliJ has a code inspection feature that is designed to prevent null pointer exceptions based on static code analysis - actually a kind of interesting idea, and the folks over at IntelliJ have recommended that the annotations be included in the Java SDK in the future. I noticed this feature when I was cleaning up some code today and found a cryptic error message in the IntelliJ code inspection tool: Not annotated method overrides method annotated with @NotNull The community documentation for IntelliJ has a nice explanation of this feature , and there is a Maven repository available. The dependency for version 12 of IntelliJ is the following: <!-- STATIC CODE INSPECTIONS -->  <dependency> <groupId>com.intellij</groupId> <artifactId>annotations</artifactId> <version>12.0</version> </dependency> Adding the @NotNull annotation to my overridden method and to a parameter seems to have cleared up the issue. I'm ...
Post a Comment
Read more