Hi! We're Nylas and we're looking for help building the next generation email platform. We're building a missing piece of Internet infrastructure and are looking for frontend application engineers and designers and backend systems and infrastructure/operations engineers to join us.
Companies are building their core businesses around our email API right now, and that means we have to be reliable, up all the time, and fast. We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, this job might be for you. :)
Many people spend their entire days buried in mail clients which haven't significantly changed in years. Yet have you ever met anyone who really loves their email experience? We want to change that. We're building a frontend framework to power the next generation of mail apps. Sound exciting to you? Apply here.
== We're particularly looking for folks who ==
* Take personal pride in their work and value craftsmanship, autonomy and ownership.
* Want the chance to step up and lead a team.
* Put the work before ego. We've got each others' backs, and we want you to be with us on that.
== A bit more about us ==
* Our backend is built on tools like Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.
* Our frontend projects use Coffeescript, React, (Re)Flux, SQL for offline caching, Electron (Atom Shell), and no jQuery.
* We're 40% women on our team of 13 (12 engineers), including 1 of 2 cofounders. We want to make that number 50%.
* We have an open vacation policy and value personal responsibility and ownership. Benefits include full health, dental, vision, commuter, and lunch at the office every day. Some remote work / work-from-home is OK too.
Apply at https://nylas.com/jobs - you can also ping me directly (jennie at nylas dot com), I'm one of the platform engineers. We're a diverse team and encourage applications from those of all backgrounds.
EB2 'other' anecdote: I came to the US in 2009 on a H1B (job offer in October, granted in December) and filed for my green card almost immediately. I had my card within 18 months, most of which was PERM.
I realise I was very fortunate in three things: timing, nationality (British) and education (two Master's degrees, so EB2). During this time I was paid market rates, though I did go through a period of minor panic when I realised I basically couldn't leave Google while my green card application was pending and I had no idea how long it would actually take. But articles like this make me extremely sad that others can't be so fortunate, and I wonder what it is we (non-voting residents) can actually do about it...
It depends on the community. For this one, it's a bunch of folks learning to code and getting coding jobs; I can imagine many of those ending up working at tech companies who might be great Slack customers, and evangelising because they had such a great experience using it - so the investment of supporting a 'free' chat room could pay off over time.
> It's probably better to be rid of "customers" like this sooner rather than later.
Agreed. This is more or less an example of patio11's "pathological customer": they won't or lack the resources to pay, have an unreasonable use case and overinflated expectations, and proceed to throw a fit loudly and publicly when they don't get their way.
They are not customers they are users, and it's important to make sure your users are happy, lest you run out of them before you run out of money catering to their every whim.
This whole concept of a 'customer' sounds very interesting, I hear they appreciate the services companies provide so much that they are willing to hand over actual money, instead of using the service they got for free to bitch about the service they got for free.
You realize that this one example actually proves the rule, no? In order for the math to work out in this instance you need a large, tech-focused community that might one day turn into a workforce of engineers that might then bring their Slack preference into new companies. At which point assuming the company isn't already using Slack, which is a very big IFF, you then hope that the coder builds enough clout in the company to evangelize Slack and convince the company to move off of whatever they are currently using.
If I were Slack I would generate migration assistants to get organizations like this OFF of Slack and on to something like Gitter ASAP. Seems like the return on that investment (in purely good will) would be much more predictable and scalable.
I agree, but it looks like there will be more projects coming. I teach a class aimed at exactly this "Codecademy chasm" and tend to use small, practical apps e.g. parsing San Francisco street sweeping data or getting the weather forecast. I'm pretty sure most of my students have no idea what logs are.
It depends how your interviewer is ranking/scoring you. One interviewer might be impressed with your ability to talk through and solve the problem from first principles, where another might ding you for not instantly knowing the answer. The former type of interviewer would be happy to give you hints and prompts, the second is a stone wall. I try to be the first -- it helps assess how a candidate responds to coaching too! -- but there's a spectrum between "nudging" and "telling them the answer straight out".
I've definitely seen interviewers (both by reading other people's feedback, and in one rare case, being an interviewee) who expected a "correct" answer and wouldn't work with the candidate to get there if they didn't already know it.
See also: overused brainteasers. I remember being asked the 5 litre / 3 litre / get 4 litres problem for my Microsoft intern interview, and honestly told them that I already knew the answer, so I wouldn't be "solving" it, but here it is anyway...
I've seen the same thing, but I tried to account for it in the 10-15% of cases where I haven't had success.
Once I notice that it's not really going well, I try to politely as possible suggest that maybe we adjourn, so as to not waste each others' time. That hasn't really ever backfired, and actually turned one rejection into an offer, but I find it's polite to respect everyones' time.
> My grandparents and parents worked very hard to provide me with the environment to succeed. Success? Stopping another generation from going down the pit.
This feels like the generalised version of the story in the BBC article, in a way. Though with the pit closures, what happened to the generation whose parents didn't work hard to get them a chance to do something different?
Half my family is Welsh and I have coal-mining ancestors -- only my great-grandparents, I think, as my Taid ran a pub. I'm the first one in that side of the family to go to university, and I know they were always extremely proud to have put my mum through nursing school and let her find a different path. It really makes you stop and think, and in my case, feel deep gratitude for those who worked hard to set up a better life for relatives they barely even met.
Indeed - giving talks, supervising research students, etc.
Having said that, I worked with a professor who had effectively taken the same route; his work was relevant in the eighties and hardly used since. My job was to try and reimplement his algorithms (ALGOL 68) in Java, which involved talking to him a lot to understand the work -- it felt like he was genuinely happy to have someone to talk to about it, and various departmental shifts and changes over the years had gradually disconnected him from the world, rather than his own decision to start gathering dust.