possibly - shoot an email to ian@
223 karma · joined January 26, 2015
* Kernel Engineer
* Virtualization Engineer
* Go Infrastructure Engineer
About: We're building out unikernel based infrastructure. If you haven't heard unikernels are super light-weight (ours weighs in around 200k + application) secure (single process - no popping a shell and wget'ng your way to freedom) virtual machines that are faster than containers and in some cases bare metal. We've been building out our own unikernel runtime lately and have other non-public projects we are working on. We're funded, have paying customers, and doing all sorts of interesting low level stuff.
If you miss hacking in assembly or haven't gotten a chance to do what you learned in school you know you belong here.
Location: We're only filling full-time on-site (SF, CA) roles at the moment.
Sponsor: We can sponsor or do transfers for the right people. Note: For H1 transfers we've had RFEs so ymmv. F1s are going to be hard too cause we prefer candidates with at least a few years under their belt.
Interview Process: 20-30min Phone Screen, 1-2hr onsite (comp. sci. fundamentals a must, *nix skills a must) - offer same day
Stack: Go, C, ASM
Also - I know this post is heavily geared towards engineers (it is HN) but if you happen to be a SDR/AE we're hiring those too!
Email us (ian@) or ping here.
* Kernel Engineer
* Virtualization Engineer
* Go Infrastructure Engineer
About: We're building out unikernel based infrastructure. We're funded, have paying customers, and doing all sorts of interesting low level stuff - a lot of it we don't publicly talk about yet.
If you miss hacking in assembly or haven't gotten a chance to do what you learned in school you know you belong here.
Location: We're only filling full-time on-site (SF, CA) roles at the moment.
Sponsor: We can sponsor or do transfers for the right people.
Interview Process: 20-30min Phone Screen, 1-2hr onsite (comp. sci. fundamentals a must) - offer same day
Stack: Go, C, ASM
Also - I know this post is heavily geared towards engineers (it is HN) but if you happen to be a SDR we're hiring those too!
Email us or ping here.
Ready to hack unikernel infrastructure? Unikernels are widely considered the cloud of the future and we have large paying customers utilizing them in production right now.
Politicians talk about re-building bridges and roads but no one discusses the mess of what software infrastructure is today or the fact that is largely built by systems designed over 40 years ago. It's time to fix that.
The software stack today is completely ludicrous - please help us fix it.
We need both Go Engineers && Kernel Engineers. Whether it's hacking DMA drivers or figuring out what needs to be tweak to scale more than 2000 VMs on a single server we got really nice meaty engineering problems for you to solve. We're currently a small team of highly technical engineers complemented by a highly effective sales team.
We have a large existing Go codebase along with a growing base of C/ASM. Other languages you might find in our codebase - rust/lua.
The opportunity to level up your game is extreme as we are going off the deep end on the technical front.
We are looking for really smart driven engineers - eg: ones that can take charge and code like the wind.
We have quite a few really interesting secret projects going on right now - would love to tell you more when we chat.
We are all on-site in our Townsend office in SF, CA. We currently aren't doing remote. We're customer driven by engineering led.
We run traditional interviews.
Please email ian / nanovms.com and secure your spot in the systems company you always wanted to work in.
Ready to hack unikernel infrastructure? Unikernels are widely considered the cloud of the future and we have large paying customers utilizing them in production right now.
Politicians talk about re-building bridges and roads but no one discusses the mess of what software infrastructure is today or the fact that is largely built by systems designed over 40 years ago. It's time to fix that.
The software stack today is completely ludicrous - please help us fix it.
We need both Go Engineers && Kernel Engineers. Whether it's hacking DMA drivers or figuring out what needs to be tweak to scale more than 2000 VMs on a single server we got really nice meaty engineering problems for you to solve. We're currently a small team of highly technical engineers complemented by a highly effective sales team.
We have a large existing Go codebase along with a growing base of C/ASM. Other languages you might find in our codebase - rust/lua.
The opportunity to level up your game is extreme as we are going off the deep end on the technical front.
We are looking for really smart driven engineers - eg: ones that can take charge and code like the wind.
We have quite a few really interesting secret projects going on right now - would love to tell you more when we chat.
We are all on-site in our Townsend office in SF, CA. We currently aren't doing remote. We're customer driven by engineering led.
We run traditional interviews.
Please email engineering @ deferpanic.com &&|| ian@ and secure your spot in the systems company you always wanted to work in.
1) What languages right now - Go, php, javascript, ruby through the rumpkernel project - rumpkernel.org.
2) We are implementing support to support user supplied images which will let you run mostly anything in the very near future. We plan to be completely agnostic.
While our main datastore is postgres we have 3 custom datastores that are starting to take a very active role. We have a lot of time-series data, very little relational, a bit of 'document' style and micro-service traces are living in their own.
Not sure if this answers your question but maybe that gets you going in the right direction.
They much rather hack on a webserver that they can use in 15 LOC from stdlib than some beefy JVM framework.
From the conversations I've had I strongly believe most webapps are going to be written in go in the coming years.
We are extremely open to suggestions/feedback.
One key point I'd like to point out though, is that OP specifically mentioned the go kit being targeted towards a company with "100–1000+ engineers". I think this is highly on point - if you have less engineers than this you probably don't have enough resources to maintain these sorts of systems yourselves and this is where we think we can help out.