What do you call this job ?
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Seems to me like it has an
abstractkeyword appended to it. You're not having any thing to do, but still you're the base for doing everything. Wow!Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem ~! Firewall !~
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
How about "The idiot who claims to know everything but is always busy for work."? :-D I want that as my title, FFS.
Overseer lord of IT?
New version: WinHeist Version 2.1.0 Beta Have you ever just looked at someone and knew the wheel was turning but the hamster was dead? Trying to understand the behavior of some people is like trying to smell the color 9. I'm not crazy, my reality is just different than yours! Not my circus not my monkey's!
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Systems Analyst is the job title as you are indeed analyzing new IT systems, both as part of their creation (review of specs etc) and implementation (testing). My guess is you'll find yourself doing most of things listed here (perhaps with the exception of ongoing support: http://hiring.monster.com/hr/hr-best-practices/recruiting-hiring-advice/job-descriptions/systems-analyst-job-description.aspx[^]
10 PRINT "Software is hard. - D. Knuth" 20 GOTO 10
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Everything sounds better with the word 'President' in it! But your colleagues will probably shoot down 'President (or Vice President) of Information Management Systems.' :(
My CodeProject Articles :: Our forgotten astronomic heritage :: My website.
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Amr Abdel Majeed wrote:
No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown: )
I work for a bank who did EXACTLY what yours is doing in the 90s, The absolutely WORST decision they have made in IT. Look for another employer, you will not be happy overseeing vendors unless you have a bent for it (management bleh). A bank, or any large organisation needs internal developers, they MUST retain the IP to the system they are reliant on, not necessarily the big, core systems but the small gluey ones that make them unique, reporting and analysis mostly. These must be handled internally.
Never underestimate the power of human stupidity RAH
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Program Manager?
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
You are missing Ace of Spades on your list :-) Anyway, I would go with something that has 'implementation' in its name. Most probably 'Implementation Officer' (or even Manager, depending on whether you have or have not the decision making power). 'System Analyst' does not sound that bad either. I saw some companies call similar people 'Product managers'...
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Job Title can affect pay; therefore check the market before picking the best sounding: http://www.totaljobs.com/salary-checker/salary-calculator[^] (Sadly The Man defaults to Therapy on the above site; you probably don't want to tell HR you're the rapy one)
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
IT Analyst
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Ive been given many titles in my 35+ yr it career on my business cards (when I was a wage slave), but when people ask 'what do you do' I always reply 'Computer programmer' (even though I do a lot more) coz most people have an idea what you mean, and it isn't as pretentions as some of the titles people give themselves. I had a self employed acquaintance who introduced himself as an 'IT director' for instance, or know salesmen who call themselves 'Business developers' when they mainly box-shift. (think of bin men calling themselves 'waste disposal technicians'). I think in your case 'IT Systems Analyst' has the right feeling and gets the message across. GL
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Amr Abdel Majeed wrote:
So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Sounds like a project manager to me.
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
Innovative Quality Usefulness (of) Information Technologist - IQUIT for short. We used a variation of that at my last job.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
DEREK. Tell everyone it's an acronym, and look at them as if they're stupid for not knowing it.
I wanna be a eunuchs developer! Pass me a bread knife!
