Skip to main content

Hiring for a New Team: Oracle Database Evangelists

I have been given the honor of building a new team at Oracle: Oracle Database Evangelists.

The Oracle Database Evangelists team is responsible for helping users fully leverage their investment in Oracle Database and to promote the use of Oracle Database technologies, including SQL, PL/SQL, Application Express, Oracle REST Data Services, and more.

So what does it mean to be an evangelist? I very much like the following quote:

A developer evangelist is first and foremost a translator. Someone who can explain technology to different audiences to get their support for a certain product or technology. It needs to be someone who is technical but also capable to find the story in a technical message… A good developer evangelist can get techies excited about a product by pointing out the benefits for developers who use the product on an eye-to-eye level." 

Christian Heilmann, Principal Technical Evangelist at Mozilla

I like the focus on "translation", because our team will be first and foremost dedicated to helping our users succeed. And to do that, you often do need to "translate" the product features and the product documentation into how-tis and examples that are accessible and quickly applied. 

Oracle Database Evangelist Job Description

Each Oracle Database Evangelist (ODE) is responsible for the creation of high quality and highly entertaining resources for training and education; channeling user requirements back to Product Management and Product Development; building a vibrant, engaged global user community.

Detailed Description

The ideal ODE candidate:

Is an expert in at least one product area
Can explain things in ways people understand and by which they are inspired
Enjoys performing in front of a crowd – and a camera
Works on a development team (you have to use it or you lose it)
Is easy to get along with; her or his ego fits through the doorway
Is a user evangelist, representing user needs and issues to development teams

Each ODE will:

Hold monthly webinars in their technology focus area
Write and publish through the PL/SQL Challenge a weekly quiz on their technology
Publish daily tips through Twitter and other social media outlets
Attend key Oracle and Oracle User Group conferences, to present, listen and learn
Work closely with Product Management and Product Development to both deepen product understanding and more effectively communicate to users how to use those products.

Location and Travel

The ODE team is distributed geographically; you do not need to work out of Oracle Headquarters to do this job.

You should expect 25% travel, though the amount of travel will be largely up to you. The focus of our team is on building global communities, and this will be done mostly through the Internet, as opposed to via jet planes.

Interested? Excited? Get in touch!

I am! One of my key objectives in returning to Oracle after a 22 year absence is to help PL/SQL developers utilize that language more fully, and to make it easier for all the experts "out there" (outside of Oracle) to contribute their knowledge to the global community.

The ODE team is going to be precisely the vehicle to do that. And along the way, we will utilize the latest multimedia and education technologies to create engaging, entertaining resources that will change the way our core application development technologies for Oracle Database are perceived and used.

If you've been around the Oracle technology community for a while and are looking for a way to contribute more, to do more, to have a greater impact, then please consider the ODE position. If you want to help ensure that languages like SQL and PL/SQL flourish, are fully appreciated and used to their max, if you like to help others do what you have learned to do, then go to Taleo, find requisition number 14000L34 and apply!


Post a Comment

Popular posts from this blog

Get rid of mutating table trigger errors with the compound trigger

When something mutates, it is changing. Something that is changing is hard to analyze and to quantify. A mutating table error (ORA-04091) occurs when a row-level trigger tries to examine or change a table that is already undergoing change (via an INSERT, UPDATE, or DELETE statement). In particular, this error occurs when a row-level trigger attempts to read or write the table from which the trigger was fired. Fortunately, the same restriction does not apply in statement-level triggers. In this post, I demonstrate the kind of scenario that will result in an ORA-04091 errors. I then show the "traditional" solution, using a collection defined in a package. Then I demonstrate how to use the compound trigger, added in Oracle Database 11g Release1,  to solve the problem much more simply. All the code shown in this example may be found in this LiveSQL script . How to Get a Mutating Table Error I need to implement this rule on my employees table: Your new salary cannot be mo

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,

Working With JSON Arrays in PL/SQL

Oracle Database 12c Release 2 built upon the 12.1 SQL/JSON features by adding a number of builtin object types (similar to classes in object-oriented languages) for manipulating JSON data in PL/SQL blocks. In this post, I explore some of the array-oriented JSON features, all made available through the JSON_ARRAY_T type and its methods. Just like a class, an object type offers a pre-defined constructor function to instantiate new instances of that type, static methods and member methods. Here are the methods you are most likely to use: A couple of things to remember, generally, about working with JSON elements generally and JSON arrays specifically in PL/SQL: Error Handling Behavior By default, if an error occurs when you call a member method for your JSON array (or object), NULL is returned. In other words, an exception is not  raised back to your block. If you want errors to be propagated from the method as an exception, call the ON_ERROR method and pass a value greate