*Role                    :         Data Analyst(SQL) with strong SQL,
Oracle (PL/SQL) and Teradata experience*

*Location             :         Woonsocket, RI*

*Duration            :         7 months contract *

*Interview           :          Phone and f2f/Skype (always prefer locals)*



It is really a Database Analyst role with strong SQL, Oracle (PL/SQL) and
Teradata experience.

the important part is *some Teradata with either PL/SQL  (Oracle) and SQL*



·         *Prior knowledge of the inner workings of the data warehouse:*

·         Batch environment

·         Local SMEs



*SQL: *

·         Oracle: ability to query script data from individual MONTHXX
tables as needed as well as the three consolidation views.

·         Oracle: ability to logically segment a large request into
multiple steps to both produce the final result faster and to minimize the
load on the database.

·         Oracle: reading and understanding explain plan

·         Oracle: knowing when to use a table join vs. Exists or Not Exists
(requires knowledge of explain plan)

·         Oracle: knowing how to tune queries using partitions, indexes,
etc.

·         Oracle: being able to analyze data to determine correct data
source—number of nulls, nullable vs. not nullable columns, frequency of
data updates, type 2 tables, etc.

·         Oracle: knowing Oracle-only SQL quirks and functionality (ex.
PIVOT analytical function)

·         Oracle: optimizer hints

·         Oracle: data dictionary knowledge

·         Oracle: know how to collect stats on a table

·         Oracle: ability to read and understand PL/SQL



*Teradata:*

·         Teradata: knowing the architecture differences between Oracle and
Teradata

·         Teradata: knowing the differences in SQL syntax between Oracle
and Teradata

·         Teradata: knowing Teradata-only SQL quirks and functionality (ex.
Qualify statement and cast())

·         Teradata: reading and understanding explain plan

·         Teradata: data dictionary knowledge



*Analysis:*

·         Be able to analyze requirements and data to produce an efficient
solution.

·         Apply analysis to SQL code (outer vs. inner joins, null handling,
etc.)



*Communication:*

·         Excellent verbal and written skills

·         Be comfortable communicating with different groups: IT, business,
analysts

·         Be comfortable communicating with anyone up to the level of vice
president

·         Be able to effectively communicate issues and risks while at the
same time giving recommendations that make sense for BOTH the technical
environment and the business needs.

·         Engage with the team in a manner that allows them to view you as
a contributor beyond just the technical.

·         Organization, time management, and documentation:

·         Be able to juggle multiple projects concurrently.

·         Build stakeholder confidence by consistently producing A-quality
results. Everyone makes mistakes, but the result of your efforts impact
direct communications with customers and patients, so due diligence and
validation are key.

·         Be able to keep track of all the emails, IMs, verbal requests,
and etc. related to a project.

·         Be able to learn from the past and prevent the same mistake
twice. In a related note, apply lessons to future requests even when not
distinctly asked for. Example: The business asks you for script data for
the last 30 days by store, but you know from experience you might need to
filter the data on things like picked-up only, no minors, no cancelled
fills, etc. Be able to speak up and clarify.

·         Document everything well and keep track of different code
versions for a project. You will almost certainly be asked to refresh
something you did before.

·         Keep management aware by documenting significant activity in
Teamtrack.



*Training:*

·         Be able to provide hands-on technical support for your
co-workers. While this is not necessarily a requirement of the job, you
will get asked for things, because you are in IT. It goes a long way if you
can answer a question about SQL or how to connect to a database, etc.
without just saying, “Call the help desk.” But, you also need to know when
calling the help desk is the right thing to do even when you know the
answer.







*Regards , *

*Akshita  | ** KPG99,INC <http://www.kpg99.com/>*


*3240 E State, St Ext |  Hamilton, NJ 08619  609-681-2602  ||
aksh...@kpgtech.com <aksh...@kpgtech.com>*

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/CAMpa04fozc6UU7dZU%2BxSXVJRRjVta8oCg5Vkf95PQTNxzG1Jbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to