Scribd | Software Engineers | Amsterdam, Netherlands | Full time | ONSITE or REMOTE (NL)
Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, podcasts, and more. Our mission is to change how the world reads. In 2019 we hit 1M paying subscribers and have been growing since then. In 2020 we acquired SlideShare.
We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites. We have a very friendly, people-first, engineering-driven culture with competitive salary and great benefits. We are ambitious but at the same time value a good work life balance. To learn more, please check out https://tech.scribd.com.
The Service Foundations team is looking for:
- Ruby Software Engineer: help us define and evolve the next version of our Ruby/Rails foundations for services contributing to observability, logging, automated upgrades, RPC, event streaming and background processing solutions.
https://jobs.lever.co/scribd/6179374e-abb9-4cf5-9c3c-b2af754...
- SRE / Platform Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies within our global traffic routing layers (service mesh, CDN). https://jobs.lever.co/scribd/8e39d0ec-cfce-400c-a6a8-4612ef8...
The Content Delivery team is looking for:
- Site Reliability Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies of our content conversion pipelines. https://jobs.lever.co/scribd/7285115a-ed1c-40c0-95b2-ea0b1e8...
The SlideShare team is looking for:
- Senior Backend Software Engineer: after our acquisition, we have dramatically improved the product and plan to accelerate these initiatives in 2022. You will have broad ownership of technical direction. https://jobs.lever.co/scribd/17ccbd20-bbc1-4e59-a15c-a922923...
We have hired many people from these HN threads, including our VP of Infrastructure.
For more details reach out to me at nickyp at scribd.com.
Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of last year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC '06), operating one of the largest Ruby on Rails sites.
In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity. We're also looking for a site reliability engineer to help us out in the cloud.
Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.
We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...
Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of this year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC '06), operating one of the largest Ruby on Rails sites.
In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.
We're also looking for a site reliability engineer to help us out in the cloud.
Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.
We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...
Scribd | Software Engineers | Amsterdam | ONSITE | VISA
Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of last year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites.
In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.
We're also looking for a site reliability engineer to help us out in the cloud.
Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.
We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...
Scribd | Software Engineers | Amsterdam | ONSITE | VISA
Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of this year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites.
In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go).
We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.
Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.
We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...
It's not 'compliancy' as much as they're reinventing the wheel.
REST was born out of a philosophy that the HTTP protocol already solved much of what you wanted to do.
HTTP not only solved this, but solved this a long time ago and with 'great success' (aka The Interwebs ;-)
- Authentication mechanism
- Operations (CRUD) -> GET, PUT, POST, DELETE, ...
- Caching -> Use HTTP caching mechanisms...
- Resources -> URL's
- Formats -> mime-types + use a HTTP Accept: header
- ...
They reinvent the wheel on many of the bullet points above:
custom operations, custom format handling, custom authentication mechanisms, ...
That's why this really is one of the worst implementation of an 'RESTful' API
Would you care to point out where in the HTTP RFCs it requires the use of certain methods for certain operations? The reality is, you can do whatever you like as far as HTTP is concerned. In fact, only GET and HEAD are required to be implemented, all the other methods are optional.
HTTP does not have "verbs". That is REST. Just because they aren't using a REST API, doesn't mean they are not HTTP compliant.
I'm not sure that it actually violates the letter of the law of the spec, but I think it definitely violates the spirit, based on this section: http://tools.ietf.org/html/rfc2616#page-51.
I thought that GET (along with a few other methods) were supposed to be "safe" and not result in any action on the server except possibly logging and stuff like that? Is this required to be HTTP compliant or is this more of a recommendation?
Sven Van Caekenberghe (the author of cl-prevalence) and I used this approach to power the back-end/cms of a concert hall back in 2003. A write-up of our experiences can be found at http://homepage.mac.com/svc/RebelWithACause/index.html
The combination of a long-running Lisp image with a remote REPL and the flexibility of the object prevalence made it a very enjoyable software development cycle. It's possibly even more applicable with the current memory prices.
I especially liked the fact that your mind never needs to step out of your object space. No fancy mapping or relationship tables, just query the objects and their relations directly. I guess that's what SmallTalk developers also like about their programming environment.
we started with cl-prevalence and then of course (NIH-syndrome) implemented our own approach to this back in 2003, which you can find at http://bknr.net/ . We used it back then to run eboy.com, and it still is powering http://quickhoney.comhttp://www.createrainforest.org/ and http://ruinwesen.com/ amongst others. Those transaction logs + images are for some 6+ years old, and have gone through multiple code rewrites and compiler changes and OS changes and what not. It is good fun, has drawbacks, has advantages, definitely widens your horizon.
Ran a couple of Xserves a while ago to run web application stacks on it and most of the time I diverged from using the GUI to administer things I shot myself in the foot (Apache, firewalls, initscripts, networking etc.).
The nice hardware - those CPU load meters were gorgeous - unfortunately doesn't make up for those problems so I switched back to non Apple hardware + Linux and never looked back.
Don't fight the system is a nice mantra to follow when using Mac OS X Server and that's not hard when you use it to administer a collection of other Macs & the network they're on or when using the built-in services without wanting to tweak/upgrade the versions yourself (iCal server, Mail server etc.).
> most of the time I diverged from using the GUI to administer things I shot myself in the foot
This is something you hopefully learned early or were told by an more experienced Mac admin— configuring, let alone automating, Xserves from a CLI is an exercise in futility as so many components system have been rewritten to do things "the Apple Way."
Learned that soon enough, only 2 Xserves were used and the rest of the rack quickly went back to Linux ;-)
Although those puppies are still up-and-running of course (my Xserve adventure was in 2003)
We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites. We have a very friendly, people-first, engineering-driven culture with competitive salary and great benefits. We are ambitious but at the same time value a good work life balance. To learn more, please check out https://tech.scribd.com.
The Service Foundations team is looking for:
- Ruby Software Engineer: help us define and evolve the next version of our Ruby/Rails foundations for services contributing to observability, logging, automated upgrades, RPC, event streaming and background processing solutions. https://jobs.lever.co/scribd/6179374e-abb9-4cf5-9c3c-b2af754...
- Go Software Engineer: we are writing more and more of our services in Go. We have interesting challenges in scaling services and building foundations. https://jobs.lever.co/scribd/96dca15a-1a0f-456e-b206-ba11775...
- SRE / Platform Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies within our global traffic routing layers (service mesh, CDN). https://jobs.lever.co/scribd/8e39d0ec-cfce-400c-a6a8-4612ef8...
The Content Delivery team is looking for:
- Site Reliability Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies of our content conversion pipelines. https://jobs.lever.co/scribd/7285115a-ed1c-40c0-95b2-ea0b1e8...
The SlideShare team is looking for:
- Senior Backend Software Engineer: after our acquisition, we have dramatically improved the product and plan to accelerate these initiatives in 2022. You will have broad ownership of technical direction. https://jobs.lever.co/scribd/17ccbd20-bbc1-4e59-a15c-a922923...
We have hired many people from these HN threads, including our VP of Infrastructure.
For more details reach out to me at nickyp at scribd.com.