Sometimes it is a just a matter of "title" and management speak. If they have 5 perl programmers, one must be "senior" and the rest "junior." In some places, this means the "seniors" are actual team leaders and have pseudo-management jobs regarding the other programmers. In other places, the job is the same, but the "senior" ones get paid a bit more. For others, a set amount of experience equates to one level or the other. I have found that years of experience does not equate so easily to the actual ability to excel at a project and write good, clean, efficient code. At least not as much as other careers. In general, as stated above, avoid "junior" designations like the plague. Push for senior, even if you don't feel worthy of the title yet.
When it all comes down to it, it's just a title. There are programmers out there straight out of college who have passion about a language (e.g. perl) and who can code circles around "experienced" programmers who are comfortably competent.
In reply to Re: What is a Junior Perl Programmer?
by turnstep
in thread What is a Junior Perl Programmer?
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |