You've been working on this project for several years; is there a monetization system in place yet? If not, your first step should be to build one. I've found that when you can build something that generates a cash flow, it becomes a lot easier to do all those other important things. Like 10x easier.
Investors are probably going to shy away from something that's been around for several years with no money.
Yes there is, it hasn't launched yet so I have no cash flow.
It's a big cloud project and just getting it launched and running is going to take at the very least some DevOps people.
It doesn't initially make sense to me that investors would shy away from something with so much existing value.
"I've done the heavy lifting, and that's a bad thing?" But I think you're right, I can see how fast-paced technology investors would be more interested in snapping up a large stake of a project with a greedy, determined leader.
I need more of a bank-loan sort of investment, which unfortunately I can't get because I trashed my credit.
Interesting idea. We'll make a blog post soon about the progress we've made.
Also, if you invite 25 friends you will have access to premium features like analytics which shows you how many companies have visited your page and what search terms the companies are using to reach you.
We built Primsly after realizing a couple of problems with the way hiring works in the tech industry:
- It's difficult to find a job when you already work 9-5 (you don't have time to interview)
- The best talent doesn't get paid proportionally to how much work they output
- There are sly tactics that companies use to force you to make an uninformed decision => resulting in an unhappy workforce.
Primsly's a solution to these problems and more. Anyhow, check it out and feel free to comment on this thread or email me directly at nima at primsly dot com. Thanks!
Working as a software engineer at a non-tech company would be a refreshing change of pace for a lot of people in tech. Could you elaborate a bit more on what exactly an engineer would do on a daily basis and what the size of the team currently is?
We are a tech company. We just don't look like one :) Tom (tptacek) always accuses me of not selling enough, so I'll give it a try.
Your question is actually very open-ended. We have roughly 4,000 R&D employees, so you can imagine the work is very diverse across the company. Teams are roughly 4-8 people at the lowest level and group up into larger organizations organized by product type (equities, fixed income, etc.).
I happen to work on infrastructure for the Professional service (aka Terminal). Our team has very little interaction with anything finance related and most of our work is related to evolving the entire platform forward and making forward-looking changes. Back in 2005, we converted all of our higher-level "app" development to server-side JS (custom, Spidermonkey based) and now run probably the largest server-side JS stack in the world (~20MM LOC). We migrated a lot of our GUI toolkit to be scripted as well (LUA this time) to allow us to more easily evolve it. And now we're evolving it, embedding WebKit and pushing bugfixes and feature enhancements to do what we need (our fork is on GH). We're helping define and implement CSS3 Grid spec and help implement ES6 generators among other things. We built and run a third-party app store within the Terminal. Over the past decade we've rebuilt the C++ foundation of the company from the ground up, starting with our own STL implementation using the Lakos allocator model (Lakos and a few other C++ committee members work here). We have a huge wealth of awesome C++ libraries that we started open-sourcing and will continue to add more layers as time goes by.
All of what I mentioned is stuff done by the infrastructure team, and we're a tiny percentage of the overall R&D population. Other teams get to do fun stuff as well. The mortgage team ported long-running ABS OAS calculations from Linux farms to GPU clusters and wrote a Python based cash flow engine from the ground up, potentially helping define the SEC's Python-files-must-be-included rules.
We run a worldwide network with somewhere around 35,000 circuits in 180+ countries. We ingest anywhere from 45-60 billion "ticks" daily aggregate from feeds in all of these countries. We normalize, scrub, and then re-distribute all this data to customers in all of those countries in an efficient manner. The Terminal provides analytic and visualization tools to work with market data, as well as the same tools to work with news and alerts. On the news side, we ingest over 80,000 news feeds (e.g. WSJ would be one "feed") from around the world and do the same kind of processing, applying ML for sentiment and topic classification, etc. We also design our own hardware in-house -- everything from keyboards and monitors, to custom ASICs for authentication/subscription tokens and PCIe hardware security modules for our certificate infrastructure. The web side (bloomberg.com, businessweek.com, BGOV, BLAW, Black, etc) uses mostly Rails stacks and everything you would expect to find in a web shop.
Oh, and we have a TV station, radio station, etc. They innovate too. Bloomberg TV is the first non-OTA channel to be distributed via Aereo, for instance :)
