Looking for developers

I'm currently looking for a developer to join my team.  We've been doing some dramatic things over the last couple of years.  We're currently driving for completion on our Vista work, and we're beginning work on our next wave of developments.  To help make that happen, I'm looking for a bright, ambitious developer who wants to be in a position to drive some extremely cool features.

To quote the ad:

Do you want to work on a small team that is working to change the way people write reliable code? Does coming up with really innovative designs and seeing them ship with Windows, CLR and WCF (a.k.a. Indigo) releases sound like your idea of a good time? If so, then you should take a look at the Transactions team in the XML Enterprise Services group. We are currently finishing our current set of deliverables and beginning the planning phase of our next wave (circa ’08) of releases.

For the last two years our mission has been to make the usage of transactions simple and ubiquitous. We have made transactions easier to use (look at the System.Transactions namespace in Whidbey) and have made dramatic improvements in performance (for in-memory transactions our performance exceeds 1 million TPS!). We have extended the reach of transactions all the way from Web Services (we authored the WS-AtomicTransactions standard and implemented it in Indigo) to the kernel (in Vista we have integrated our transactions stack with the transacted file system and registry).

But all of this is just the beginning. In our upcoming releases we will continue extend our reach, from ultra-lightweight transactions in one direction to long-running activities with compensation in the other. We will make the usage of transactions pervasive throughout the managed space (from implementing transacted collections to working with MSR on cutting edge technologies). Most importantly, we will continue to ship regularly to get our work into the hands of customers!

Applicants should be experienced in designing, developing and shipping products and have full understanding of the development cycle. Must have a passion for quality, be creative and be able to write robust, secure and maintainable code. Must be able to work effectively with a team of highly skilled and motivated developers. Must be able to own several features concurrently, make decisions independently, and have strong communication and development skills. Proven and demonstrable skill in C++, C#, or Java is required. An MS degree in computer science, a related degree, or equivalent experience is required. Knowledge of transaction concepts or industry experience with a transaction processing or a reliable messaging technology would be a definite plus.

If you're excited by these sorts of challenges, see.


Posted Oct 31 2005, 02:30 PM by jim-johnson

Comments

Security Briefs wrote Tx work at MS
on 11-04-2005 12:03 AM
Shawn Wildermuth wrote re: Looking for developers
on 11-08-2005 1:06 AM
I love the concept, but I assume that relocation is required?
Jim Johnson wrote re: Looking for developers
on 11-08-2005 7:08 AM
Yes, it's a Redmond only position.

I can tell you, though, that I relocated to here a few years ago from the UK, and it has been a great experience.

Jim.
ex-Surf wrote re: Looking for developers
on 11-15-2005 6:08 PM
"in-memory txn" seems like an oxymoron...
Alan Potter wrote re: Looking for developers
on 11-28-2005 10:40 PM
>"in-memory txn" seems like an oxymoron...

Not if you've got an in-memory database accessed by multiple threads...
Matt wrote re: Looking for developers
on 12-02-2005 2:15 AM
Yeh, shame relocation is required :(
Jim Johnson wrote re: Looking for developers
on 12-02-2005 8:21 AM
Yeah, it's required. Fwiw, I made a pretty big relo (from Scotland) to come here, and have had a great time with work and really like the area.

And, fwiw, Alan is pretty much dead on -- but ask just how simple that in memory database could be. There's a lot bubbling in the research area, and it looks be a pretty cool time for transaction technologies.

Jim.
Alan Potter wrote re: Looking for developers
on 12-07-2005 12:56 AM
>but ask just how simple that in memory database could be

Any object... and if you're talking of user-mode, .Net managed code, that means anything... You sure do want to make that lightweight...

Shame about the relo.

/alan

ex-Surf wrote re: Looking for developers
on 12-30-2005 5:07 PM
>"Not if you've got an in-memory database accessed by multiple threads..."

how do you ensure txn durability/recovery during system failure when it's in (volatile) memory?

Jim Johnson wrote re: Looking for developers
on 12-30-2005 7:12 PM
Let me jump in on that -- I have a prior entry in this blog (http://pluralsight.com/blogs/jimjohn/archive/2005/02/10/5727.aspx) that talks about volatile resources.

Note that since these resources don't exist across system failures, there is nothing to recover.

Now, if there are any non-volatile resources, or any failure modes where the resource can outlive the transaction manager, then the transaction outcome must be recorded persistently.

Jim.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?