Perhaps hire one senior level and a two or three junior level developers to work closely together, and try and raise the productivity of the new devs.
If there are NO senior level programmers available, maybe they should get creative.
Perhaps hire one senior level and a two or three junior level developers to work closely together, and try and raise the productivity of the new devs.
If there are NO senior level programmers available, maybe they should get creative.
well and after all that investment the person leaves for better salary/etc... to somebody who is looking to hire senior people and not "willing to hire a junior dev or admin and contribute anything at all to his/her personal development, skill accumulation, and experience" There is a reason for the things even if we don't like the reason.
And again, the "hot" skills (any NoSQL/Hadoop) can be picked in a week and even junior with such skills would easy find a place. There is just no excuse for somebody unsuccessfully looking for work in this market to not sit down and master some of such skills.
They could offer them a raise based on their new value? If this company can't pay people well or offer a good work environment, how are they going to get senior developers?
> (any NoSQL/Hadoop) can be picked in a week
I can't believe there are companies looking for people with a "week" of experience in NoSQL who aren't mid-level developers already.
Companies have been hiring tons of inexperienced devs throughout the late '90s and early '00s, and they have been hurt badly by it. Incoherent teams full of junior devs that lacked practical skills and didn't know how to work in a team nearly killed many software based companies.
A CS degree teaches barely any professional skills, it's all on the job training, so training a junior is extremely costly.
So nowadays, smart companies build their team around seniors, and only then start hiring juniors one at a time. Which means 3 to 4 seniors for every junior dev.
It's not about "plugging the hole", it's about making sure the ship doesn't start leaking so badly it sinks.
The following team is vary senior heavy and would avoid the junior dev team syndrome without costing an arm an arm and a leg and is still reasonably stable over the long term as long as turnover is low.
1 person with 0-2 years exp, 1 person with 2-5, 1 with 5-7, 3 with 7+ and 1 with 15+.
To, keep priming the pump just look for one new grad every 2 years and keep a lookout for the occasional great senior dev out there to cover for attrition.
Hiring "junior devs" and "hiring inexperienced devs" can be a world apart.
Hiring someone for position X who turns out to be inexperienced is not the same as explicitly hiring a junior developer with the intent of training them up.
I've seen a lot of the former, but not much of the latter. The two ideas get conflated quite often, but in reality are different and the latter takes a bigger commitment of resources.
"So nowadays, smart companies build their team around seniors, and only then start hiring juniors one at a time."
5-10 years from now, the conventional wisdom will probably be different. Sr devs might be more willing to leave, and if there are fewer of them, a larger percentage of your company knowledge, culture and IP resources go with them.
Where are the companies hiring warlocks in training, people willing to learn but needing the chance to grow and be challenged.
I guess I wonder why, if I was indeed a sr level engineer, why I would work for anyone at all when I could command high rates as a freelancer, or build my own products.
On the other hand for people with 5+ years of experience there seems to be tons of high paying jobs.
Five years ago you could get a job around here as a security guard making 80k if you had a TS clearance.
For startups, it makes sense to desire a senior level developer. Midsize and large companies really should explore internal training programs. Everyone a generation older than me talk about a world where the "entered through the mail room" and worked their way up. Does this world even exist today? From my point of view, it seems like we only expect top talent everywhere.
Seriously, few things can sink the ship faster than taking on inexperienced people and hoping they'll learn. From that point of view, I can see why many startups, particularly those whose CTO/VP-E doesn't have management depth in addition to their technical depth.
I've been doing it for about 5 years now, almost exclusively remote - it's not difficult, it just requires that everyone communicate well, or be willing to learn, if they don't already.
Part of the problem I've encountered are founder/senior managment who are willing to learn these management skills themselves - they are conditioned that everything is on them, so that can be tough.
At this point, I'm of the opinion that in most cases, especially with startups, remote is far more humane than in the office. It's also far more cost effective.
I had one year of programming experience when I was hired at MyEdu. I was desperate for a job so I actually signed on as a member of the automated data collection team, which only involved writing lightweight scripts. After six months, though, I taught myself PHP and improved my JavaScript enough to move up to the web development team.
Other coworkers of mine at MyEdu had similar experiences with paths like manual data entry -> QA -> web developer / DBA (as junior roles), or automated data collection -> sysop + backend developer (junior role). I don't work there now, but I think it would still be fair to characterize the company as one willing to take a chance on someone who shows a burgeoning aptitude. [And there are direct hires into junior web dev roles also; promotion from within is highly valued but not the only route.]
Naturally, this is not how you make the biggest of bucks, but it's a decent salary (with stock options for some positions) + work on a meaningful product + an enjoyable work environment. It's an especially attractive situation for people who are attempting a career transition like I was.
In the interest of not derailing the discussion too much, email me if you want to know more about my experience there. I haven't worked there since August but I worked there for over two years.
> And do you know if the hire remote for a probation period?
Remote work is normally unavailable to junior positions -- it's more of a trust-earned situation.