At Jargon, our mission is to build the most useful content management and developer tools for voice platforms like Amazon Alexa and Google Assistant.
We recently completed the Amazon Alexa Accelerator (powered by Techstars), and have an ambitious roadmap to take full advantage of the burgeoning voice market.
We're looking to add several talented full-stack Software Engineers to work on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique Conversation Platform.
Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.
If you're interested in having significant impact, building a lot, working along experienced leaders, and shaping the voice industry, come join our Seattle-based team!
At Jargon we're building the tools developers of voice applications (e.g., Amazon Alexa skills or Google Assistant shortcuts) need to manage their content, reach global users, and build compelling, engaging experiences.
We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk), the backend of our voice conversation platform, and internal and customer facing websites.
We have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market and would love for you to join us on the journey.
Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.
Jargon enables voice applications (e.g., Amazon Alexa skills or Google Assistant shortcuts) to manage their content and reach global users.
We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique localization system.
We have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market and would love for you to join us on the journey.
Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.
Jargon | Sr. Software Engineer | Seattle, WA ONSITE
At Jargon we help voice publishers speak their customers' language.
We recently completed the Amazon Accelerator (powered by Techstars), and have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market.
We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique localization system.
Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.
$1m / year is actually a very common base salary, for tax reasons -- anything above that amount the company can't deduct as a compensation expense. The majority of CEO compensation is via bonuses and long-term equity incentives (grant, options, etc.).
It's the underwriters of the IPO that impose the lockout periods, not management. The lockouts apply to all pre-IPO shareholders (excluding shares explicitly included as part of the offering).
Lockouts may also include provisions that any early release granted to management or dominant shareholders must also be granted to all other parties on equal terms; that was true of the one lockout agreement I was subject to.
Amazon -- you can use Elastic Map Reduce [1] (the easiest way to run a transient Hadoop cluster) or spin up a bunch of EC2 nodes and deploy your own stack. Both methods can provide you access to very powerful hardware [2].
(Disclaimer: I work for Amazon, but not in AWS, and these are my own personal opinions.)
The misspelling in the title is quite intentional -- cek is Charlie Kindel, former GM of Windows Phone Developer Experience (see http://news.ycombinator.com/item?id=2860646).
It should also be said that he's a great guy that I've known for more than a decade. Anyone who's interested in taking part in an early stage Seattle startup should definitely send him a message.
Well, on LinkedIn or Twitter or Google+ I guess -- Charlie, please add contact info to your HN profile!
[Edit] Looks like the title spelling has been corrected...
Why do you think Hipmunk uses GWT (by which I assume you mean Google Web Toolkit)? The source for www.hipmunk.com pulls in jquery, but doesn't have the history iframe or <module>.nocache.js reference that one would expect to see for a GWT application.
One interesting thing we discovered about IPXs late one night in the lab is that they're FCC Class A devices -- that is, they didn't have the same level of RF shielding as consumer Class B gear. How did we exploit this? The memory bus timings happened to be in the FM radio range (~90-110 MHz), so by copying buffers in tight loops we were able to create a tone generator with a 10-20 foot transmit range.
I do hope the professors with nearby offices (and conveniently with radios on their desks) enjoyed our looping rendition of the Close Encounters of the Third Kind theme when they came in the next morning.
The article describes techniques for setting up RAID(0) against EC2 local ephemeral storage for performance gains. As there's no way to replace a failed drive RAID 10 wouldn't provide any benefit.
Absolutely, you should -- for everything already said here, and more. When you interview with a company do they ask you about the project? Have their developers looked at the code in enough detail to question the design decision you've made and see what you've learned since then?
"We established long-term relationships with many important strategic partners, including America
Online, Yahoo!, Excite, Netscape, GeoCities, AltaVista, @Home, and Prodigy"
Are those the topics you're interested in or the ones that you don't want to see? I'm not sure if your example uses command-line argument syntax or search engine query syntax...
I do like the idea, btw. The difficulty most likely is accurately categorizing articles. I know /. added tagging at some point but I'm not sure if that ended up actually being useful.
At Jargon, our mission is to build the most useful content management and developer tools for voice platforms like Amazon Alexa and Google Assistant.
We recently completed the Amazon Alexa Accelerator (powered by Techstars), and have an ambitious roadmap to take full advantage of the burgeoning voice market.
We're looking to add several talented full-stack Software Engineers to work on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique Conversation Platform.
Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.
If you're interested in having significant impact, building a lot, working along experienced leaders, and shaping the voice industry, come join our Seattle-based team!
https://angel.co/jargon-com/jobs