EmployThis came to be because of a request to create software to help people looking to change jobs. Often misunderstood, it is not just the unemployed who are seeking a new job. In fact, unemployed may make up only between 10% to 30% of the entire job seeking market. Thus the software would mostly be used by educated, professional, computer literate people. Therefore the design considerations required it to be robust, yet easy to use and to be mobile ready.
About me: I create software for non programmers. People who want computers to do things – like EmployThis, come to me and describe their needs. I often act like a business systems consultant asking questions like, ‘does it need to be mobile’, or ‘what reports will you need?’ or ‘how are the reports used?’ Together we design the application, select the best platform and tools, assign developers and manage the construction. Something of a general contractor for software.
I don’t actually code programs. That is mostly because the system requirements of any given job may be better suited to one development platform or language than another. If programming were my thing I would be limited in service to my clients because that would limit my scope to expertise in only one language or platform. Rather I coordinate, more accurately I design it or manage the development. My role can be best described indirectly. Programmers and business people speak different languages, and I am their supreme translator because I understand both business system and design languages fluently. Thus it was a natural fit that the question passed my desk.
The problem with creating tools for job seekers comes from the open nature of job listings. Job openings may be posted on Craigslist, a company website, a recruiter’s website or a public website like Career Builder. In fact a single job may be posted on multiple locations concurrently. Jobs may be reposted on a website if they are not filled and may vary slightly between postings or locations.
Applying to jobs may also involve a host of sources for information such as: your resume may be on your desktop or different websites and be sent to places or websites other than the job posting site. To make things even more complex, the postings for job positions have a short life expectancy. In reality job opening notifications are most often removed from the web before the interview process. So a way to access job listings that have been de-published and yet find them when the interview is being scheduled complicates the software need.
Technically speaking and rendering the challenge down to simple terms: information may come from many different locations, none of which are on the users computer, and information is going to locations which, most often, are also not on the user’s computer. The challenge is to manage remote data in a many-to-many relationship.
When first approached with this challenge for job seekers a core problem of remote data management was already on my desk. It was working on a way users could manage a many-to-many remote-file relationship. So there was a near fit, but not a turn-key solution.
Even now, all contemporary file systems manage files in their own hardware structure. These can best be described as a many-to-one or one-to many environment.
In a job search this might be Monster.com manages monster files, the same is true for Career Builder or your own personal PC. These are both examples of one-to-many relationships. But EmployThis needed a way to manage files on multiple websites and data storage structures.
This is not a trivial problem or is there an easy solution.
As mentioned above, managing remote and local data storages as one comprehensive system in a many-to-many relationship was a problem I was working on. The solution I had was working but the specs I was working on didn’t call for a useful or even mobile interface because the implementation of the data management was to be done in a layer below the existing program’s user interface. In English – the user interface of an existing application would be used and my solution would be invisible to the user.
But EmployThis needed an elegant and simple user interface. That was the second problem.
Literally, after years of consideration, two things came together. One was the visual representation of data – this is called data visualization, not surprisingly. But the other, more importantly, was able to create and test a complex algorithm that would manage data by something other than file name and location. Considering it in this way, meant that files can be moved and renamed and their presence, or files’ identification, in a data storage system would be unaffected. it is like your keys don’t have to be on the same fob or the same place to start your car or open your home.
When applied to files which have a source on other systems and websites, those files could be integrated into an application like EmployThis without the user caring what they were named or where they were located. This is enormously powerful, because even if the files were moved their relationship for the job seeker would be unaffected. The job seeker could still find them.
Think of it this way – wouldn’t it be really great if you didn’t have to know where a file was located or what it was named and yet you could still find it in just two clicks?
We named the algorithm used to identify files digital-DNA or d-DNA.
EmployThis is an extremely robust and technically advanced design project incorporating our proprietary algorithm for d-DNA. Because d-DNA tracks files without regard of the file name and location and EmployThis needs to track information where the user may not have control over the sites that manage file names and locations, it was obvious: the only way to make EmployThis work reliably was to use the d-DNA proprietary algorithm.
EmployThis is the working amalgam of that long process of reinventing how file systems work and a visual user interface.
Though extensive in coding, d-DNA users can drag-and-drop files from their desktop, or from websites into a their own visual space in EmployThis without ever worrying where those files are stored or what they are named. That is what makes EmployThis so powerful. The files do not need to be on your PC, they can come from anywhere, even a job announcement site. The visual presentation of d-DNA is called the Job Map™.
The job map keeps track of where the files are automatically so users don’t have to remember where a file is or what it is named. When files are stored in the job map they can be moved and renamed without affecting the visual job map. The whole thing is pictorial so no training is necessary. It took us ten years to develop the technology including two years for the patent. You can’t imagine how happy we were to receive our patent! It cost – giving up dinners-out, movies and even vacations – but it was worth it because EmployThis works. Users can access the files they want instantly, often in just-two-clicks™.
Stated differently – in EmployThis the user’s files just don’t get misplaced!
We believe the years we invested in designing and testing our unique, remote, many-to-many data relationships and deployed into a simple user accessible system will help people find better jobs. That’s it.
We really are committed to this belief. And we know that once people use EmployThis they will convince themselves this is truly a great disruptive technology.
We hope you share our vision and excitement.