
If you’re looking for an Oracle resource, there is a huge possible range of knowledge.

In your interview, you should distinguish between the two. Every project should have at least one good developer. A developer should be able to handle requirements gathering through implementation. A developer should be part analyst and part coder. What, exactly, will this person be doing in their day-to-day job? It’s easy to say having a good job description makes it easier but in many cases, employers have a generic template when looking for someone.įirst off, is there a difference between a developer and a programmer? I think there is. To me, probably the hardest thing is pinpointing exactly what you want this person to do.

Interviewing technical resources is very difficult.

In this entry, I share my method for interviewing Oracle resources and provide some sample interview questions and answers for developers. I’m seeing many of my friends find new jobs and I’m doing a lot of interviewing at work. It looks like the job market for Oracle is opening up.
