Oracle is looking for a software development manager to work with their OnDemand CRM team:
We are looking for an experienced, energetic manager to lead our applications team (approximately 12 developers). This person should share our passion about creating industry changing applications that are focused on our end users. This position will entail responsibility for end to end application development and delivery including development, QA, PSR, & Operations. This role will also require close coordination with many other groups in Oracle including Product Management, Customer Care, Legal, etc.
From the sounds of things, it’s a senior role in a good-sized team of people working on relatively modern technology to deliver large-scale products that people are interested in, that the large company that owns this team supports, using agile methods.
There’s a lot to be impressed by, in that list.
First of all, there’s not a ton of detail. What’s the team like, what are the projects, are people really interested in them, and does Oracle really support them. What’s it like to work at this location, is it really a small-company feel with big-company resources, or a big-company feel with small-company resources? What’s the compensation?
And to the specifics — there’s a reference about multiple time zones. If you’ve got a team of twelve and you’re managing them in an agile fashion, why are time-zones a requirement? Is this agile team of twelve spread about the globe?
First and foremost, the location is steeles and the 404, which is well outside of Toronto, and depending where you live, either convenient, or ludicrous. For me, it’d be the latter.
Well, although your immediate connection is with the local team, the overall company is Oracle. For some people, that might sound just-about-perfect: the resources of the big company when you need it, and a small place to hang your hat and make a mark. To others, that might sound like the sort of place where your office is too small to offer daycare and free meals, but there’s thirty-sheets of paperwork to fill out any time you want to shift one developer from one project to another. One of you is likely more right than the other, but I can’t tell you which one.
Finally, Flex: it’s an interesting technology, and I expect we’re all going to see more of it, but it’s a bit of a bear to work with in automated testing, which could be a problem for an agile team.
This looks tailor-made for someone who’s uptown already (or at least mid-town) when they start their day, and is willing to work for a company that sounds like Oracle.