Fully remote jobs for front end developers

Get remote jobs delivered to your inbox weekly.

Frontend Engineer at Parse.ly

Apply Now

We are seeking a senior developer who loves programming and shipping production software, but who also has keen design instincts and an ability to simplify, simplify, simplify — until the data speaks for itself.

Our frontend team owns the core experience of Parse.ly’s customer-facing SaaS products — most importantly, its real-time analytics dashboard.

Parse.ly is a fully distributed team, which means 100% of our engineers, designers, and product managers (including our founder & CTO) work out of home offices. Most of the frontend team is located in US/Eastern and US/Central timezones. We’ll also give preference to those timezones, because even though we operate on a distributed/async model, we like to have timezone overlap for f2f (video) collaboration and pairing. We prefer to hire US-based candidates, but we’ll consider Canada, Mexico, and Argentina for this role.

So, you might wonder, how do I get an interview with Parse.ly?

To prove design instincts to us, we ask that you point toward some work you have done in the past that showcases your frontend, UX, or data viz design tastes. For example:

  • A web portfolio of data visualization sketches, e.g. on bl.ocks.orgcodepen.io, or similar.
  • Github, or similar, code repos for JavaScript code, along with a README that describes or showcases how it looks when run.
  • Dribbble, or similar, screen crops of your designed interfaces.
  • Screenshots of past products you have worked on and how they looked in a shipped state, with some explanation of what parts you worked on, and how it was built. Using something like Dropbox is fine.

Or, if none of the above are available, feel free to get creative! Perhaps include a recorded live demo (you could try loom.com to record it); share a link to a recorded presentation at a conference or meetup; or, even share raw notes captured from your notebook. Indeed, photos of your design sketchbooks are very much welcome!

Your Perspective on JavaScript

JavaScript has gone through a lot of iteration in the last several years. Parse.ly has existed across three JavaScript maturity waves: (1) simple rich web apps built with Python/Django and a touch of jQuery & D3.js; (2) full AngularJS 1.x SPAs powered by a Django REST API, during the peak of Angular 1’s popularity; (3) componetized React applications powered by REST APIs & GraphQL, more recently. We even had a brief stint with Vue.

Given this evolution, Parse.ly frontend engineers develop a mastery over JavaScript and web technologies, pick the best tool for the job, and don’t fuss about the particular framework du jour. You’ll be working on a modern JavaScript codebase — parts of which might leverage AngularJS, D3.js, React, or other libraries. Since you’re a senior JavaScript engineer, a mix of frameworks doesn’t bother you in the slightest, as you realize it’s the nature of the beast for a set of successful and production web applications developed 2013-2019. And, since you’re a senior software engineer, cracking open the middle tier — which is written with established & stable technologies like Python 3, Django, and Postgres — doesn’t bother you either.

What You’ll Do:

  • Write JavaScript code using the best practices.
  • Come up with novel interface implementations and data visualizations.
  • Write code in Python that power our Django-based HTTP API.
  • Creatively sketch and design new product features.
  • Analyze customer usage data to improve shipped features.

An Ideal Applicant Will Have:

  • 5+ years experience in technology.
  • A preference for self-sufficient productivity.
  • A highly organized and disciplined approach to self-improvement.
  • Senior level of proficiency with modern JavaScript.
  • Comfort with git, the command line, and Python.

Looking for a new job?

Front end remote jobs is a curated job board featuring fully remote front end jobs for front end developers. New jobs are added every week.

View all remote front end jobs =>