Early Engineer (LeftLane)

LeftLane · United States · posted today ago

engineering javascript remote jobs in united states

Listing supplied by Himalayas. 101 Careers did not originate this post and applications are handled by the employer.

About this role

LeftLane's mission to become the operating system for the 70k independent used car dealerships across the nation. We help independent dealerships manage the lifecycle of their inventory, secure financing for their customers, keep accounting records, comply with regulations, and learn more about their business.

This is an opportunity to get significant equity, significant responsibility, and ultimately, build a product that enables small businesses to serve ~40 million used car buyers every year. Here is some background context on the company.

Responsibilities

As an early engineer, you'll be wearing many hats across the stack and will interact directly with customers to gather feedback. You'll have a loud voice in driving early decisions. You'll need to:

drive and evangelize best practices across at least one area of the stack
own greenfield feature development end-to-end
own entire product verticals (inventory management, accounting, CRM, collections, etc.) and/or infrastructure horizontals (auth, CI, deployment, background jobs, etc.)
weigh the tradeoffs of decisions for technology and architecture adoption

This will be a good fit if you:

think an early-stage startup would be fun
are excited about the upside potential
are ambitious i.e. want to run your own team or be a founder yourself in the future
take ownership of problems i.e. will do what needs to be done
you like being rewarded directly for your high output

This will not be a good fit if:

you want to specialize strongly in one area or technology
you cannot iterate quickly
cannot take ownership and initiative

The Stack

We strongly believe that tight feedback loops and fast iteration drive great product. That is why we are obsessed with developer experience, pushing every commit to production, observability/alerting, feature flags/experiments, and test driven development.

Stack

RedwoodJS (node)
GraphQL
React + Apollo
Postgres
Render

Logistics

Full time only
Onsite/Remote: We prefer a flexible onsite model. Given how early we are we believe it will let us move the fastest and collaborate the smoothest.
Hours: At the end of the day what matters is the work and so you'll control your hours (if you need to WFH for X reason or swap a Monday for a Saturday or XYZ you can do that as long as expectations for work are being met), but we expect some minimumoverlap with the team to make collaboration flow, 4/5 days a week 10 - 4 in the office would be a reasonable base