Skip to main content

Looking for one more evangelist: Oracle Database for Open Source

The Oracle Database Evangelist team currently has two evangelists focused on SQL, one on PL/SQL, and another on Javascript/HTML5. 

 Overall, our mission is to show how powerful Oracle Database is as a foundation for application development. And with so much energy and application creation happening in open source communities, we are now looking to hire one more evangelist who has experience with Oracle Database, but is also active in two or more open source developer environments. 

 You will find below the description of this position and our ideal candidate, who would not only evangelize Oracle Database into open source communities, but advocate for the needs of those communities back to Oracle development. 

 You can apply for this position by following this link.
Oracle Database Evangelist for Open Source

This Oracle Database Evangelist position is first and foremost dedicated to helping open source developers succeed with Oracle.

Each Oracle Database Evangelist is responsible for the creation of high quality and highly entertaining resources for training and education; building a vibrant, engaged global user community; channeling user requirements back to Product Development to enable new generations of developers to fully utilize our technology.

You will be part of an evangelist team responsible for helping users fully utilize the Oracle Database and to promote the use of Oracle Database technologies, including SQL, PL/SQL, Application Express, Oracle REST Data Services, and more.

The ideal candidate:
  • Has a proven track record working with open source developer communities.
  • Has experience working with several of the following communities PHP, Python, Ruby, Node.js, JavaScript (or related libraries, frameworks, ORMs, CMSs etc for these technologies). 
  • Can explain things in ways people understand and by which they are    inspired
  • Enjoys performing in front of a crowd – and a camera.
  • Likes meeting new people and learning new technologies.
  • Is a user evangelist, representing user needs and issues to Oracle Development teams.
The successful candidate should expect to:
  • Stay current with trends and technologies in their respective communities.
  • Work with development to make sure that there are optimized technologies for using the Oracle Database.
  • Maintain an active online and physical presence within the developer communities.
  • Attend key PHP, Python, Ruby and other open source developer conferences, to present, listen and learn.
  • Act as a router / bridge, between the community and Oracle Product Management and Development.
Location and Travel

The team is distributed geographically; a driven individual could perform this job from home or out of the local Oracle office.  You should expect 25% travel, though the amount of travel will be largely up to you.

If you've been around the Oracle technology community for a while and are looking for a way to contribute more, to have a greater impact, then consider this position.  If you want to help ensure that people in open source development communities can make the most of their investment in Oracle technologies, if you like to help others do what you have learned to do, then apply for this position.

Comments

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more