ZipRecruiter - https://ziprecruiter.com - Santa Monica (LA area) - REMOTE OK for some positions.
Our goal is to create the best online services for filling and finding jobs.
We're growing rapidly and have a large customer base (primarily small and medium sized businesses). We have interesting problems to solve in the areas of search, yield management, analytics, scalability and new product development. If you'd like to learn more, please visit:
https://www.ziprecruiter.com/hiring/technology or email us at techjobs@ziprecruiter.com
We do try to respond to all responses to this thread that come through that email address. It is humans replying, not a bot, so it is always possible to miss an email. I encourage you to email again and apologize for not responding the first time.
Specifying raw or cooked rice gets you the right answer. Given that it gives you the info to correct instantly, this isn't too bad. NLP is hard.
We had a similar idea, but for automatic handling of whole recipes that you can adjust to your dietary needs (http://www.tweakeats.com). I have to say I prefer the feedback for individual ingredients that spelt has though, given the ambiguity of a lot of ingredients (raw vs cooked, chopped ingredients measured before or after chopping, red peppers, etc.). Seeing quickly how is was interpreted is helpful.
A lot of companies will ask for existing code examples, in this way I can just point them to my example-code github repo and I've had companies use that instead of asking me to do a specific challenge for them.
At the teams I have managed at larger companies (Stamps.com, TrueCar) the technical track had official equivalents to management roles (Sr. Engineer -> Manager, Architect -> Director, Sr. Architect -> VP) for determining compensation, equity and any other role defined "perks."
Each of those roles also came with leadership expectations: Architects were responsible for the overall technical health of the systems they were responsible for, with Sr. Architects being responsible for multiple. They were empowered to reject system changes and were expected to review code and designs on a regular basis. Really good engineers that weren't system thinkers or didn't want responsibility for other people's code, could increase in compensation but weren't considered part of the leadership team.
I know I am late to this thread, but building development tools for closed source products (.NET, etc.) is an easy way to make a living. Developers are easy to reach, don't demand glossy marketing and have a good sense of the time they can save with your tool. Two of my early startups were both development tools companies and they were both quickly profitable.
We have a number of open positions:
We're growing rapidly and have a large customer base (primarily small and medium sized businesses). We have interesting problems to solve in the areas of search, yield management, analytics, scalability and new product development. If you'd like to learn more, please visit: https://www.ziprecruiter.com/hiring/technology or email us at techjobs@ziprecruiter.com