With the exception of c++, socket(mkt data), py(devops), c#, MSVS … looks like majority of ventures out of my tech sweet spot java/SQL/scripting… presents esteem-hazards (like health hazards) but dismal prospect in terms of self-esteem boost.
high-risk, low-return ventures, in terms of self-esteem?
Looking deeper, the esteem-hazard is really nothing but one mgr’s assessment. For my recent painful jobs, I continue to dismiss/ignore the possible boost to self-esteem —
- I conquered some of my biggest technology fears — MSVS; c++ crash management; c++ large code navigation.. Other people may not agree, but my own experience proves that these challenges are harder than high-level dev (like web/scripting..). My fears about these c++ challenges were more deep-rooted .
- OC — I built real mileage in c#. I even proved myself stronger than some c# veterans when I created a simple web server to dump log files for everyday troubleshooting.
- Macq — I invented elegant solutions for splunk even though boss wasn’t impressed
- .. many more
- see more pointers in https://bintanvictor.wordpress.com/wp-admin/post.php?post=27139&action=edit
All three jobs were java-lite , with some quantDev exposure. Through these jobs, I gained the crucial clarity about the bleak reality of the quantDev career direction. The clarity enabled me to take the bold decision to stop the brave but costly TSN attempts to secure a foothold. Foothold is simply too tough and futile.
Traditional QuantDev in derivative pricing is a shrinking job pool. Poor portability of skills without any standard set of interview topics.
at same pay, now I would prefer eq than drv pricing domain, due to mkt depth and job pool.
QuantDev offers no contract roles !
Instead, I successfully established some c#/py/c++ trec. The c++ accu, though incomplete, was especially difficult and precious.
Without these progresses, I would be lacking the confidence in py/c#/c++ professional dev that enabled me to work towards and achieve multiple job offers. I would still be stuck in the quantDev direction.
See also past vindicative specializations
- I would still do my MSFM
- I would still fail to get into algo trading or quant dev — too few jobs and extremely high bar
- I would likely fail to get into leadership roles. I was considered for leadership roles at 1 to 3 companies
- I could possibly have focused on a specialization such as risk system + some analytics
- would probably have joined citi, barc, baml, UBS, SC or .. in sg
- probably java or swing or connectivity
- would Not have achieved the c#/py/c++ ZBS growth
- would Not have the skills to get this ICE raw mkt data job or the other c++ job offers.
- no guarantee to become a
manager or app owner. There could be many old timers in the team.
- possibly less stress and pain. Lower chance of performance stress (#1 biggest stressor), because my GTD/KPI would be higher due to my java/SQL zbs.
In the US I can slowly steer my tech specialist career into my chosen strategic domains of specialization like
– financial analytics
– big data
– statistical analysis
– risk analytics
In many of these domains, most of my peers struggle while I am comfortable…. more confidence, more leisure, more free time, less stress ..
In Singapore, I don’t have the luxury because there are Simply too few jobs at my salary level. Those specialized jobs there are, are simply too selective too demanding
— OC: wanted to go deep into drv pricing..
–stirt: wanted to go into curve building and real time risk but ..
–Mac: wanted to go into quant dev …
Update — In ##what actually determined%%past job satisfaction I concluded that respect(zbs) was the #1 determinant of my job satisfaction. In these 3 Singapore jobs, my efficiency and zbs were insufficient compared to whatever their benchmark is. Even in java, theoretical, complex domains, without distractions … my colleagues could be superfast. Even if I get a lot done, I can still be seen as under-performing — low respect low bonus. Consider GS.
Update — my RTS GTD/effi was lower than Singapore, much lower than Stirt and Macquarie.
It’s kinda hard to measure 2 developers’ output. Given my background within my past teams, I now feel I did reasonably well on GTD, not super productive or super slow. Some periods in OC and Stirt were highly productive. My productivity was not excellent in Citi, Verizon, even 95Green,
not higher than in Stirt. Conclusion — my GTD productivity self-assessment is swayed by my income and boss’s assessment.
- In OC, I took care of Guardian, Quest, Excel interface, Bloomberg and other part of GMDS. I wrote the web-based log viewer in WCF…. I think my OC 1st-year GTD productivity was reasonable, probably higher than Citi, and not lower than barcap.
- The donut bonus was at least 50% due to manager relationship.
- In contrast, at 95Green and Barcap my GTD was not much higher, but the value of my output was higher than team peers. I spent my spare time on c++, swing, c#, quant…
- In Stirt and Macquarie, manager felt I was good enough to be transferred to other teams — sign of respect
- Stirt — I had lower value-add than the veterans, but probably higher value-add than most new joiners. Technically I was rated competent by everyone, otherwise they wouldn’t set up the transfer. My Stirt GTD effi was clearly higher than at citi and not lower than Barcap or 95G. Perhaps only lower than GS.
- One /speed bump/ was the perfectionist team lead who approves everyone’s commit
- Another speed bump was lack of online resources for hacking (i.e. self-study).
- Macqarie role has very high requirements in terms of communication, leadership, but in terms of technical expertise I was clearly appreciated, otherwise they wouldn’t hint the internal transfer, and they wouldn’t pay me a $10k bonus.
Common reason: no IV to give feedback on any “muscle growth”
Common reason: Most if not ALL of the growth areas have since become non-strategic, due to the limited job market
- c# — Actually my c# had tremendous and fast growth, no slower than my 2010-2012 peak period, but there was no IV to verify it
- py — was growing fast in Mac, but no full time python jobs
- quant — I went through a hell of growth in quant-dev, but gave up
- c++ tool knowledge — was growing in Mac but not a QQ topic at all.
- c++ optimization for HFT — I read quite a bit but can’t pass the interviews 😦 so I gave up