Java SDK Engineers within the Manta team will be a primary part of the core Manta Client SDK group and own the development of Manta’s Java SDK. The primary mission of an SDK Engineer is the ongoing development and maintenance of the SDKs and associated tools. Collaborating with management, customers, and other engineering teams, the SDK Engineer is a lynchpin ensuring the platform and services delivered are reliable and easy to use. Candidates local to San Francisco or willing to relocate are preferred, although individuals with proven experience working remotely will also be considered.

Qualifications

• Proficient in modern Java development practices (1.8+) and tools

• Comfortable writing both unit and integration tests and understand their tradeoffs

• Experience with the principles of concurrency and multi-threading both generally and in Java

• Deep understanding of HTTP and client-server architectures

• Thorough understanding of the principles and failure modes of distributed systems

• Obsessed with writing clean, understandable code, avoiding unnecessarily clever solutions whenever possible (even if they’re fun to implement)

• Capable of working both within a team and independently

• Strong attention to detail and a passion for delivering valuable solutions to customers

• Familiarity with Maven configuration and workflows

• Willing to travel up to 15%

0Thread HN

Elevator.js 11 years ago

I don't know why there's so much empty space at the bottom but I did notice my phone allowed me to continue playing the song if I dragged up from the bottom. It's four full minutes of sweet, relaxing elevator music.

0Thread HN

Was Y Combinator Worth It? 12 years ago

The result is not totally surprising but it's nice to see some numbers to quantify it. The only negative thing I see is the fact that the only comments so far are complaining about identifying investors.

0Thread HN

Mastering Modern Payments: Using Stripe with Rails 13 years ago

This page feels awfully meta.

0Thread HN

Tell W3C: We don't want the Hollyweb 13 years ago

I'm having trouble understanding what you mean by people paying for the creation of goods by the people that want the content. The division between paying for DRM-free content and the creation of that content seems contrived unless you're saying that consumers would pay the content creators directly so that more content can be produced, but that would make it problematic for up and coming artists to break into the market.

Don't take this as an argument, I'm just asking for clarification.

0Thread HN