When hiring Oracle DBAs and developers, a lot of questions are asked about Oracle view. Although view is only one of Oracle objects and it is not that significant in my opinion, for some reason managers and business users love views, therefore in interview they usually like to ask more questions on Oracle views. The following are some of questions and answers for you to prepare: (more…)
The other day, I received this question on our Expert forum.
“I am in a situation where I have studied communication, got a distinction for my final year … its been 3 yrs and I have landed in so many unrelated jobs that I beginning to think that I will never work in communications … how can I get there and not be paid a beginners salary??”
This was my answer: (more…)
In today’s IT environment, you’ll need the ability to get along with all kinds of people, coworkers, managers, subordinates, and especially customers. To do your job, you must get long with all of them.
Are there difficult people? If you think they are difficult, you imply that you may not be able to get along with them well. So, the answer this question, first deny there are any difficult people to you.
Sample Answer:
“To me people are different but not difficult. I honestly don’t think there’s any type of people that I don’t get along with. Of course, some people are more pleasant to be around than others, but I’ve worked with all kinds of personalities and never had any problems with anyone. I understand this consulting position requires interaction with a lot of client, I am very good at this.”
In general it is not the time to deal with the salary question until the offer is made. If they ask you this question during interview, ask back for the salary range of this position first. You can mention you are flexible about salary, which means it’s negotiable. Don’t give a specific amount and don’t make a commitment. You’ll have the fun time for real negotiation after they offer you the job.
But before interview you’d better do the salary research. Check the web and ask around. There are many online resources for IT job salary info.
Sample Answers:
“I’d rather not commit to a specific salary until the interview process is over and you make a formal offer. What is most important to me is the opportunity to work for your company. I am confident that your offer will be competitive.”
“I would expect a salary which reflects my skills and experience. What’s the salary range for this position?”
“I’m sure you will be fair. My focus is on finding the right opportunity, and I’ll be open to discussing salary when the offer is made.”
“I am ready to consider your very best offer. What did you have in mind?”
“I’ve got extensive experience on Oracle and believe my DBA skills are a perfect match for this position. I would expect my salary to be at the upper end of your range.”
Are you making these software development blunders? Here’s the top 10 list compiled by Borland.
1. building Infrequently
The solution to painful dentist visits isn’t going less often, it’s going more often! The same is true of painful software integration events. Building frequently – preferably continuously – allows you to discover problems early on and nip them in the bud before they grow into big expensive disasters. Plus, building software is a critical validation step – you don’t know if something’s broken until you try putting it together. Build frequently gives you greater confidence that you know what the state of your software development project really is. (more…)
Money… that’s what this is all about. Unfortunately, business owners don’t hire you simply to give you their money. The surest way to not get a job is to ring up and ask how much it is paying.
The second best way to miss out on the job is to ask how much you will be paid in the first interview. Either wait for the final interview or until you have received a job offer. Besides, your research of the industry should already give you an indication of how much to expect. (more…)
Be careful about this question. What the interviewers want to know it your knowledge and experience on OLAP DSS, but many candidates missed this point, they explained their DBA experience in general, but failed to answer what is asked. To answer this question correctly, you should provide your knowledge about the characters of OLAP and DSS systems, and how you configure the database to meet the requirements. (more…)
After-interview fallow-up play an important role to help you stand out and get hired, that’s simply because majority of candidates don’t do it. It is such a great way to distinguish you from the rest of the pool. Why most people (maybe include you) don’t follow up? Because they are afraid of rejection, and rejection hurts.
Let’s face it. Rejection is an unfortunate part of the job-hunting journey everyone gets, so don’t take it personally. You don’t lose anything by follow-up but you have a lot to gain even if you get rejection in return. If the answer is no, forget it and move on. By all means, you used this opportunity to practice you communication skills, which would benefit you in the long run.
How to follow up, then? (more…)
CASE Tools
Computer-Aided Software Engineering (CASE) tools are used by system analysts, designers, and developers to capture information about business requirements, create a design for the data structures to fulfill those requirements, and generate front-end and server program code. CASE tools can automate much of the manual, repetitive, and error-prone work needed for system development, and can greatly increase the productivity, accuracy of the design, and robustness of the implementation. (more…)
First, let’s admit the fact, many job seekers lie in interview, and they get good jobs with no problem. Sounds like a good deal? It might be, but the risk is not tiny. After all, lying is not a good practice. Thus my suggestion is, do not lie. Instead, hide facts. Facts are the truth, but you don’t have to tell the truth if the facts don’t make any good to you. Last but not least, don’t lie on obvious things, that means, don’t call black white. (more…)