(1) is very probably in the IT bonus pool, but your headhunter should have already told you whether it is FO or IT, since there is a serious difference in bonus.If they say things like "it depends" or "taken into account", or the frankly dishonest "on a par with", it's an IT bonus.You're right to pick up on the fact that you weren't interviewed by anyone other than IT. Inevitably you will learn more about trading which is of course good.Although by day I am a headhunter I also teach C++ on the CQF (long story), and I cover C++ addins for Excel, and it's on the syllabus because it is useful, and seems to be taught nowhere else.At it's core, it's an interface, an unusual one, but just an interface. The meat of your work will I assume be to code what happen after the call is made, which sounds as if it will be quite varied, and may be rather interesting.That's based upon my view that most Excel C++ addins in banks are analytical routines, so you won't be doing much of the dull work humping static data etc, which soak up much of the time of many quant developers.Also, modern versions of Excel (>= 2007) support multi threading which can add to the fun. But if you're going for JPM, my understanding that they regard any piece of software written in this century with a form of superstitious fear that medieval peasants might feel if a mobile phone appeared in their mud hut and started talking to them. Some of their developers use tools that are older than they are, yes really.You seem to have sensed that your programming skills will degrade, which I have to say is not my expectation of such a role, except....Being hyper-literal about how you describe the job: "smooth delivery of the quantitative models to the business."Can mean one of two things.a) You are writing stuff the traders want, working with quants with a focus on the code aspects, and the i/o of your code goes through Excel.That's a respectable C++ QD role. The fact that it's Excel is merely a detail that actually positively affects the quality of the job because the users of your work are FO.b) They've got some huge pile of non-XLL C++ which is not yet coded to work with Excel, perhaps as part of libs that currently integrate with other C++ code. Some may even be in VBA, Java, C# etcIt's possible to write some classes that hide Excel interfacing and some sed/awk scripts to change the code, but most people seem to end up manually editing code. Inevitably that will be some of your work, but that may vary anywhere from 2% to 98%, being work that is just skilled enough that a monkey can't do it, but not skilled enough that you can maitain, let alone improve your skills.(2) seems a bit vague. To judge it I'd like to know what sort of people interviewed you, how much they drilled into your business knowledge and how much they talked about things like databases.Is the work on strategies, risk, position keeping, exchange connectivity ?In my view, the best guarantee of "stability" is what is in your head in terms of skills and experience, which usually ourtanks the stability of the firm. A thing to know about large firms is that they are unlikely to die in (say) the next three years (though that's not impossible), but they could determine that they don't need you any more. So the net extra risk of joining the prop shop as big as it might seem, but is >0My standard method for evaluating a job includes looking at what the job after that might be.The big bank adds to your value by branding, and having FO C++ developer as a job title (make sure that'is the title, not just a description) is a pretty good place to be in terms of getting another decent job.The marginal value of the branding varies a bit depending on what you've done so far in your career. So you need to ask a bit more detail about the work.I suspect you will learn more at the prop shop, and probably ean more, but like many kinds of higher returns, risk goes up as well. I can't make that call for you.