Zalando is Europe's leading online fashion platform. We deliver to customers in 20 countries. In our fashion store, they can find a wide assortment from more than 4,000 brands.
We are looking for 2 Senior Backend Engineers to join the teams that select the delivery promises (how fast customers can get their orders, and for what fee) shown on the product detail and checkout pages. The team owns its services completely, so we look for candidates with DevOps experience in addition to excellent software development skills.
Our stack is mostly Kotlin microservices running on Kubernetes, with a few services in Java as well. You will get to work on critical services at a large scale, and with strict availability and latency SLOs. You will be part of a small-to-medium size team, will work closely with stakeholders and Product Managers, and will help mentor other engineers on your team.
Unfortunately, some publications use a double-blind review process, where checking whether the authors have published similar content before becomes more difficult: you'd have to figure out who the authors are first, which kind of goes against the idea of a double-blind review process.
But of course, when the double-blind review process is not used, then it makes perfect sense for a reviewer to check the authors' other published work. In journals that require a certain percentage of original work, I don't see any other way.
If all papers were indexed by a full-text search engine, you could simply pick a few sentences that sound unique and search for them across all publications. It's not like self-plagiarism is more important to detect than regular plagiarism :)
Or journals could just submit all papers to the plagiarism-detectors used for undergraduate work, like Turnitin.
Yes, we use it in Nakadi (https://zalando.github.io/nakadi/). It's an event broker platform based on Kafka, and we use json-schema for event validation.
About me: Currently a postdoctoral researcher in SWE, looking to transition to industry or applied research. I am working on bidirectional programming and self-adaptive systems, with a keen interest in functional programming and security (especially authorization).
Location: Tokyo, Japan (but I'm a Belgian citizen)
Remote: possibly, but I'd prefer on site
Willing to relocate: Yes! US, Canada, or Europe (incl. Switzerland). I am authorized to work in the EU and Switzerland.
Technologies:
- Java, Haskell, some Spring, Python, and Scala, OCL
- git, AWS, Linux, some server administration
- authorization (access control), modeling, verification, and repair.
Oh, what a fantastic idea. Just take an old smartphone that the manufacturer stopped shipping security updates for ages ago (if they ever did it at all), and get it to record what goes on inside your home. What could possibly go wrong?
You might want to look at http://androidvulnerabilities.org/ to see the sorry state of security on Android phones. The older they get, of course, the worse it is.
All I see are tons of local privilege escalation, which is concerning if you like to download and run random not-very-trustworthy apps, but it's actually not of much significance if all you're using the phone for is as a network camera. IMHO these are the good exploits, since they let you get root and have full control over the device so you can repurpose it more easily for other things... like network cameras.
Remote exploits that require no user action are the only thing to worry about here, and Stagefright is AFAIK the only one I've heard about so far (simple solution: take the SIM card out - what do you need it for in this application anyway?)
Correct me if I'm wrong, but it seems that the author's point can be summarised as:
Obscurity will (at least in the case of an SSH deamon) not make an attack any less likely to /succeed/, but it will make it less likely to /happen/.
Note that what he observed were automated, scan-everything-you-can, undirected attacks. I would presume that changing the SSH port will do very little against a targeted attack.
Zalando is Europe's leading online fashion platform. We deliver to customers in 20 countries. In our fashion store, they can find a wide assortment from more than 4,000 brands.
We are looking for 2 Senior Backend Engineers to join the teams that select the delivery promises (how fast customers can get their orders, and for what fee) shown on the product detail and checkout pages. The team owns its services completely, so we look for candidates with DevOps experience in addition to excellent software development skills.
Our stack is mostly Kotlin microservices running on Kubernetes, with a few services in Java as well. You will get to work on critical services at a large scale, and with strict availability and latency SLOs. You will be part of a small-to-medium size team, will work closely with stakeholders and Product Managers, and will help mentor other engineers on your team.
Senior Software Engineer (Java/Cloud) - Fulfilment Offering https://grnh.se/25c5a86f1us
More positions here, including other locations: https://jobs.zalando.com/en/jobs/?filters%5Bcategories%5D%5B...