Trabajo de Front End Developer en Placeit Envato, Jalisco - México

Front End Developer

Hi - we, at Placeit have a need to hire Front-end Engineers.

 

We run a tool called Placeit used by hundreds of thousands of clients around the world. We serve over 2 million users worldwide and we process a transaction every 2 minutes. We also run several other products used by some 8 million people around the world, but we'll cover that later.

 

We've just begun our expansion plans and would like you to be a part of it. We currently have 190 people in our offices in Guadalajara, but our engineering team is small (22 people).

 

We started as an agency, called Fresh out in 2008. We developed new products for companies such Yahoo, Telefonica, eBay. When we realized we couldn't control the products we built through our clients, we started to invest in our own products. We bootstrapped our way to a product company in late 2014.

 

What kind of work do front-end engineers typically do at your company?

 

Typically, the product manager just works directly with the front-end engineer to determine the UX a particular feature. For smaller items, our “mockups” are done on developer tools directly in order to follow the existing style conventions.

 

For larger items, they are crudely drawn in short-hand wireframes (on paper) and then prototyped to give room to the engineer to make what they see as the best decision. Those decisions are also externalized to the rest of the team. We rarely design in Photoshop or Sketch.

 

We believe that aesthetics has very little to do with the success of our products, so we primarily focus our attention on the "functional" UX with specific constraints that we put on our products.

 

That's also why our front-end engineers propose and control much of the UX of the product. Most of the flows and interactions are done directly and iterated on the prototype level.

We've seen that it's better to spend more time to align the front-end engineer with the product goals and let them propose the execution options rather than having a designer propose them. Those options proposed by the engineer are usually discussed, iterated and executed by the same engineer.

 

We work this way because we've seen the best ideas for user experience come from those building the product as long as they care, understand the product goals and are given autonomy.

 

This also means that you will spend very little time “slicing” up images and spending most of your time in actual front-end engineering. We tend to follow the style guides and UX guidelines that we develop once and follow through.


What would I work on specifically?

You would be working on the front-end of Placeit. So, you'd be entirely responsible for the front-end aspect of any new features for Placeit. The most immediate new item we're working on next is a video mockup feature that we've been prototyping for a while. If you want to see some examples, visit the Placeit website.


What general skills do I need to perform well in this position?

  • You need to know how to:

  • Be clever about how to approach problems

  • Be technically curious (learning on your own)

  • Have a serious interest in understanding the goal behind your work

  • Push for doing things the right way the first time around

  • Have empathy for our users


What technical skills do I need to perform well in this position?

 

  • You need to be familiar with the following:

  • HTML (different version) and their compatibilities.

  • CSS (different versions and techniques to apply effects and cross browser support), one or two CSS frameworks (LESS or SASS).

  • Component frameworks such as Bootstrap or Foundation.

  • JS: programming model in JavaScript / inheritance model, scoping, differences between the three major version of JS.

  • HTTP: how the protocol generally works and how browsers generally deal with it.

  • Web sockets and web workers.

  • Experience with AJAX libraries (jQuery is required and one of these three: Backbone, Angular or React).


What is the required baseline technical skills for all levels of engineers there?

 

  • Here is a list of what we consider baseline fundamentals that you need to be familiar with no matter what area of ​​the platform you work on:

  • Unix: bash, piping, SSH, tools (CAT, AWK, SED), basics of standard input / output

  • Basic principles of database design

  • Basic experience with ORM

  • Software Design Patterns (https://en.wikipedia.org/wiki/Software_design_pattern)

  • Functional Programming Principles (https://en.wikipedia.org/wiki/Software_design_pattern)

  • Event Oriented (including asynchronous) Programming (https://en.wikipedia.org/wiki/Event-driven_programming)

  • Object Oriented Programming (https://en.wikipedia.org/wiki/Object-oriented_programming)

  • Prototype Based Programming (https://en.wikipedia.org/wiki/Prototype-based_programming)

  • Coding Best Practice

  • Refactoring Best Practices

  • Test Driven Development (https://en.wikipedia.org/wiki/Test-driven_development)

 

What does the flow look from the beginning to deploy for a particular feature?


You get a feature request from product manager

  • You make sure you understand the goals clearly and collect basic information

  • Assuming it's time to work on it, you'd start with the specifications (detailed in X Workflow document).

  • The document generally starts with describing the problem, a bit of background and your hypothesis for the approach you're going to take.

  • Then you would work on the high-level solution proposal

  • And lastly would be your Blackbox (if needed), Theory of operations and functional specs.

  • Once those are approved, you can start coding!

  • Once your code is ready, you would deploy to staging to test your work.

  • If ready, you would then send your code for final review.

  • If ready, then it would be deployed to production after OK from CTO.

  • Lastly, you would go back to update your specification with any future work that you believe this feature needs.

 

How's the work / life balance there?


Most engineers are here between 10am to 6pm although some come earlier and leave a bit earlier. Some days they stay later and some days they leave earlier.

We generally keep an "adult policy" over these things. The idea is that you're responsible and we're not going to babysit you. We don't really focus on the hours you spend the office. Our focus is mostly on how efficient you are. We're flexible for people that want to start work earlier and leave earlier as well.


I like the position but what if I'm wrapping up a freelance project currently?


That's ok. We can work on a part time basis (has to be at least half time) for the first month or two. This approach works out well so you can see if this is a good fit for you before committing 100%.

Do you guys help with my paperwork if I'm not a Mexican citizen?

And it is! Will also pay for it.

 

Benefits

  • Private Medical Insurance

  • Saving funds

  • Full Law Benefits

  • Profit sharing (5% of company profits)

  • Pay for roundtrip tickets to anywhere in Mexico 2x a year

  • Inflation adjustment of salary

  • Paid for educational courses

  • Unlimited ebooks / books

  • Top line equipment

  • Central location (Lopez Cotilla 1599)

  • Paid for Friday Mondays, fruit, coffee, snacks subsidized

  • Impact on lots of users (over 8m users) / fast growing

 

Salary range

The salary range for this position would be between $ 60,000.00 and $ 80,000.00 MXN Gross.