*Role: SQL Developer with Oracle EBS experience * *Location: 18 months*
*Client: HCL / Google* *Location: Sunnyvale, CA * ***Make sure they have not been previously submitted to Google!*** Solid experience in the approach to developing structured queries, extract, transform and load. They want people who are NOT tied to any specific tool. Their queries will be against a backend Oracle EBS system. Oracle EBS is preferred but not required. Minimum is 5 years but they are really focusing on 7-8 years MAXIMUM.. Do not send people with 10 years or more..they not a fit.. they are too far away from the heads down coding needed. *Job Roles & Responsibilities*:- 1. Candidate will be writing SQL queries to extract the data from EBS. 2. Candidate will be working on inhouse ETL tools (similar to Pentaho) but not tool specifc. 3. Candidate should be writing shell scripts (Python/Perl) 4. Candidate would be working on in house tools to provide the dashboards. 5. Candidate has to help business to Design and develop data warehouse solutions 6. Strong SQL development. (we are not talking about SSIS/SSRS.. but basic and advanced Structured Query Language) 7. Unix Shell Scripting 8. Oracle on the backend with strong preference for Oracle e-business Suite (Oracle Assets, GL, Payable, Receivables, Cash Mgt, Tabs: CRM, Supply Chain, ERP). The Oracle database is not the same as EBS!! *What we need in order to submit:* 3) Fill out the HCL Chart at the BOTTOM of this e-mail 1) Self Rating 2) Justification of Self Rating (make sure you write 1-2 sentences in the “Remarks Section” next to each skill) 4) Provide interview times for today, Monday-Friday next week PST or EST time zones only. 5) Updated resume showing Structured Query Language (SQL) examples under each project and what they have done with it (see comments below.. READ everything from top of this email to the bottom and write sentences under each project..do NOT copy word for word anything!) **Review the “Typical SQL ROLE” duties below and update resume. make sure you show where Oracle or Oracle EBS is used as a backend database. Unix Shell Scripting, Prefer: Pentaho or ODI (Oracle Data Integrator), any DBA work. In order to qualify, sentences under each project showing what they did must be there. If it is just listed at the top or the Environment section, it does NOT count. They will be asked technical questions during the interview and they have to back it up. If they are just exposed or familiar with it, DO NOT add to resume. 6) Once they get an interview directly from the T-Mobile team, they need to follow the Google Hangouts instructions attached. Only candidates that the client feels are qualified based on resume will get interviewed . 7) These are 1-2 year assignments in Sunnyvale CA for Google Corporation. Google Hangouts Interviews only. No phone. Typical SQL role : 1. *Security.* This should always be first. Understand SQL injection and parameterized queries. 2. *Restoring a database.* Notice how I did not say, "making a backup." That will obviously be a necessary step, but it's far more important to know how to *restore*, because otherwise your backups are for naught. 3. *Query load monitoring.* How do you identify which queries account for the greatest share of your database load? 4. *Query optimization.* Once you find the bad queries, improve them. a. Creating indexes b. Rewriting query logic c. Partitioning or sharding d. Denormalization e. Using caches or message queues in your application 5. *DBMS tuning.* Most databases have many options to tune resource use. For example, allocating as much RAM as possible to cache data and indexes. 6. *SQL types.* Understand the characteristics of different SQL types as they pertain to logic, performance, and storage. I'll include *SQL NULLs* as part of this entry, although that could be a separate item itself. 7. *Transactions.* Understand the importance of grouping changes and committing them as an atomic unit of work. Understand isolation levels. 8. *Set-based data operations.* Many developers think of a database as a collection of individual rows, and fail to use powerful features of SQL to update sets of data in one query. Developers who use object-relational mapping (ORM) tools are especially guilty of this. 9. *High availability.* What happens if/when your database server shuts down, or needs to be upgraded? Does your application handle this gracefully? Can you queue data changes temporarily until the database is back online? Do you have a spare database instance for failover? How do you get the spare back in sync with the primary? If there's one item from Justin's list I'm tempted to reiterate, it would *SQL JOINs*. As far as SQL language features, that is very frequently misunderstood by developers. Will also get *UNIX Shell Scripting questions.* Do your best here. Best Regards, *Fredric Miller | Sr. Recruiter*Pull Skill Technologies, Inc. Office: +1 201 497 1010 Ext: 104 | Fax: +1 201 641 0110 fred...@pullskill.com *------------------------------* Note: We respect your on-line privacy. This is not an unsolicited mail. Under Bill 1618 Title III passed by the 105th US Congress this mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. If you are not interested in receiving our emails then please reply with a *"REMOVE"* in the subject line. We truly apologize for the inconvenience caused. -- You received this message because you are subscribed to the Google Groups "SAP ABAP" group. To unsubscribe from this group and stop receiving emails from it, send an email to sap-abap+unsubscr...@googlegroups.com. To post to this group, send email to sap-abap@googlegroups.com. Visit this group at https://groups.google.com/group/sap-abap. For more options, visit https://groups.google.com/d/optout.
