First, Think
First…..
During your
academic finals, get Internships first, even at the small
firm will be OK. Request your employers for any kind of database related work,
or work as a SQL Developer. Don’t restrict yourself with any one kind of
database like MySQL, MSSQL, Oracle, MongoDB. Whatever you get, Just go for it.
Now impress
your bosses to convert your internships to full time job. Even if the company
wants you to be a Windows admin or Network admin first, just take the job.
Don’t ever neglect any opportunity. Now, You can slowly swivel to DBA career.
Conduct
Informational Interviews with people you know or your friends know. Join Communities on Facebook, Quora and OTN. Discover a WhatsApp group
for DBA’s and stay connected with the technology. You will meet new people.
These people could be working for companies that you may be interested in. You
may get opening/vacancies information. Find out what kind of databases they
use. Get specific. Find out the database versions and what their daily tasks
and challenges are. Try to add value to them. Just drop in every now and then
and present your findings.
It may be really small. But once people start seeing that you can add value, you will be hired. Think hard. You will definitely find some people you can talk to.
During learning, always spend more time understanding the fundamentals, Once you gets through the basics, the content or theory, later part would be a piece of cake for you now. So I suggest you to learn the basics and try to revise everything daily, example, Oracle Architecture.
Oracle
Architecture is very vast and even the core components still remain the same,
but the Oracle’s architecture has evolved on every version. When you become an
Oracle DBA, one of your main responsibilities will be monitoring production
databases.
During
Technical Interview, there is
99.99 % probability that Interview panel will ask you to Explain Oracle
Architecture. So, be well prepared for
this and explore every ‘nook and hook’ of Oracle Architecture and make a note
and write the architecture in your own words. Revise it daily.
Because once
you explain the architecture properly, there is 60 % chances you are selected,
because rest is depend on your technical answers.
Do not
explain architecture in rush. Never do this mistake. I saw many candidates,
they just finish explaining the architecture in 5-7 minutes. This is Bad.
You should
explain the Architecture for at least 25-30 minutes. So that the interviewer
get impressed.
Further part
of Interview preparation is written in my next article..
No comments:
Post a Comment