Frontend Software Developer
About LaterPay
We want to change the way people buy and sell digital content on the Internet. Why? Because we believe paying for digital content should be fast, convenient, and fair. And because we think you should be able to buy the exact piece of content you want.
We want to create a great software product that influences and changes the way people use paid content of any kind on the Internet. Consuming paid content should be as easy and convenient as going out to dinner: you are served first and you pay later. We want to build a user-centric product that makes users feel smart. It should represent the simplest, most secure way to buy digital goods. We want to change the way people regard paid content, turning it into a great experience. We want to enable businesses to offer “paid content as a service”, assuring users of their content’s value instead of forcing them to pay before actually getting the content.
What we have
English is our language, Slack is our “office” (though we also rent an office in Munich), GitHub’s where we keep our code, and AWS is where our stuff runs (plus some machines in a Munich DC, but we’re winding that down).
We’ve got a bunch of web UIs: newer ones built with React and Webpack and deployed to AWS S3, plus some older ones based around Django-templated HTML and jQuery. Behind them sit various services, mostly Python/Django providing REST-y APIs.
How we work
As a distributed team, we’re not too bothered by when and where you work. That said, most of us work Monday - Friday from 9ish UTC to 6ish UTC, and ideally you’d overlap heavily with that.
We try to be as asynchronous as possible, but still feel that we need some “synchronicity” to work well.
- Based in UTC+4 and want to work “normal hours”? Sure
- Based in UTC–8 and want to time-shift your days to overlap with “Team UTC”? If that works for you, sure
- Hobbies, family, pets etc. that require you to take time out of your day? Assuming you can maintain a reasonable amount of overlap with the rest of the team, sure
We care more about what you do and how you work with the rest of the team, than we do about your ability to be at a chair at a desk at 9am every day.
What we’re looking for
Good command of written English
This is probably the most important quality. Communication is vital, especially as a distributed team, where most tools we use don’t communicate tone or body language.
Anecdata suggests that your English is probably better than you think it is.
A desire to fix problems “properly” (not just paper over them) AND an understanding that you often can’t fix problems properly
We want you to want to build good-quality well-engineered solutions, but to know that sometimes you just need to “hack it in”. There are always tradeoffs to be made.
Experience and drive
You don’t need to be a Senior X or Chief Y, but you do need to be capable of taking a task and owning it.
That doesn’t mean you necessarily do all the work, but it does mean you take on responsibility for completion, and asking for help and advice as appropriate.
Specifics
Knowledge of HTML, CSS, JavaScript and the DOM is essential and you know what a browser is capable of and what’s available to you. Knowing how to build and debug complex applications is important, as well as ensuring they perform well. You understand how to test frontend applications, and how to choose and evaluate tools to help you better do your job. Oh, and having an eye for UX can be very valuable too.
Familiarity with React and its ecosystem is important - we need you to be able to hit the ground running with our existing React-based UIs. Knowledge of the Flux Application Architecture is also important. Familiarity with Redux is useful, though not mandatory.
A solid surface/contextual-level understanding of “the full web stack” is massively useful - we don’t expect you to know the mechanics of a DNS SOA record or the inner workings of Postgres’s HStore, but knowing the right sort of tool to use for a given task is important, as is knowing enough words to start asking helpful questions / googling the right things
Experience with Python would definitely be useful to be able to poke the underlying services
Closing date
We will be taking applications until 10 January 2017. All screens and interviews will be arranged after the closing date.
APPLY
If this sounds interesting, but you're not sure you're quite the right fit, *apply*, and let us know what you bring to the table. We're not just looking for "Computer Science degree and X years of experience with language Y".
Salary
36k-65kEUR / year
Desired Skills
Contact Info
- Company Website: https://www.laterpay.net/
