Developer/App Server Admin?

[Robert Chisholm]

I don't think such a thing exists.

Some client wants to hire me as a "Systems Administrator" that does Application Server administration... and some small development projects on the side.

I am a developer (that happens to know a fair bit about App Servers... but what developer doesn't?)

Has anyone heard of such a thing?

[Mark Herschberg]

Yes, I see positions like that all the time. It's a small firm. They need an admin. It's not a full time role but it is the primary responsibility, so they have you do coding on the side. Also, many sys admins don't know how to manage web servers but many developers do. Before talking the job ask yourself is this is where you want to grow your career.

--Mark

[Robert Chisholm]

That is exactly the case... although it's not really a "small" shop, they do not spend much money on IT. They have very few developers, and no Sys Admin at all.

I'm not keen to get "Sys Amin" on my resume. Have you heard of any other "titles" for such a thing? Maybe I can convince the company to change the job title.

[Tim Holloway]

I've no problems claiming SysAdmin experience. I feel that I'm never going to produce software that runs effectively/efficiently unless I periodically get a chance to see how the hardware's being abused.

I've seen a few "app admin" positions advertised in this state. Usually meaning they want 6 years WebLogic admin experience.

And BTW, also Solaris admin experience, extensive J2EE coding experience, plus 5 years RUP.

Starting salary $35K. Ending salary also $35K.

I'm not joking, alas.

[Mark Herschberg]

Originally posted by Robert Chisholm:
I'm not keen to get "Sys Amin" on my resume. Have you heard of any other "titles" for such a thing? Maybe I can convince the company to change the job title.

I haven't but perhaps you can make your own title. Granted, when I'm skimming resumes, I look at the title and glance at one or two descriptions--some bad titles can hurt you. But once in the interview, I drill down into what the tasks were and how much time was spent on each. Ask youself, at an interview 2-3 years from now, how comfortable you would be describing the role to a potential employer, as it was described to you? Do you think it would help your career, both for your next step and/or long term?

--Mark