Nuvocargo is reinventing the $2 trillion freight forwarding industry. We are a digital-first freight forwarder using a mix of technology and exceptional service to help companies seamlessly move products across the Americas, starting with the biggest trade lane in the world: Mexico USA cross-border trucking.\n\n**The opportunity for you**\n\nAs a Nuvocargo software engineer, you will work with senior members of the engineering and product organization. You will help architect and implement solutions up and down the stack from our front end apps, to our backend API, to our databases and external services.\n\nYou will also be part of the landing team that will kickstart our engineering presence in Mexico City. As part of that team you'll help set a high quality bar for engineering and help us bring software best-practices from Silicon Valley to Mexico, making a meaningful impact to the startup ecosystem in Latin America.\n\nTogether with rest of the engineering, product, design organization, you will help shape the future of Nuvocargo's tech stack and engineering culture.\n\nOur current stack includes a combination of modern tooling and philosophies:\n\n- The front end interfaces include React (including Context and Hooks), Next.js and interactive interfaces via the WhatsApp Business API interfaces and emails.\n- Our React/Jamstack apps are continuously deployed on Netlify and the internal team workflows and interfaces use a mix of low-code and no-code solutions (think: Airtable, Retool and Zapier) for fast iteration combined with custom front ends for usability, precision and control on certain workflows.\n- The design and styling processes for our frontend interfaces include Zeplin.io and a component library hosted in React Styleguidist.\n- We use Rails API, a Postgres database and API integrations with multiple external services for back end development.\n- We have a strong culture of building quickly and iteratively, deploying features and releases to staging and production multiple times a day.\n\nThe products you build will be used by hundreds of Nuvocargo's customers, carriers and users across Nuvocargo's internal teams.\n\n**Who you are**\n\n- You love deploying features. One of your favorite feelings is shipping code and releasing new features to users. You know when to accrue technical debt in order to get a feature live. You strive for simple, readable code and you are averse to over-engineering the task at hand (YAGNI).\n- You have a track record of building great software in fast-growing companies. You have battle scars and wisdom from many years of building software in ever-changing environments. That wisdom comes both from projects that were incredibly successful and from projects that were abject failures.\n- You are passionate about making an impact in the Latin American startup ecosystem. You want to have a direct impact in establishing Nuvocargo's engineering org as one that bridges the gaps between Silicon Valley startups and the Latin American startup ecosystem.\n- 1 + 1 = 3. You strongly believe that collaboration, pairing, mentoring and raising the bar for everyone on the team makes the team greater than the sum of its parts.\n- You are a software craftsperson who believes in the journey to mastery. You believe in creating well crafted software, steadily adding value to stakeholders (as well as the engineering team and your future self) and collaborating with others with an open mind and flexible opinions. You believe that the journey of mastering the craft of software never ends, but you love being along for the ride.\n- You thrive in a low-friction, light-process environment. We are not a meeting-heavy org. You are self-motivated to write great software, release great products, pair with team members all without spending hours deliberating whether something is "3 points" or "5 points".\n- You are intellectually curious. You are probably a polyglot when it comes to programming languages (and natural languages), even if you don't have mastery over those other languages. You are always curious to dabble in a new library or framework or language and you analyze their high level pros and cons without even realizing it.\n- You are both a great communicator and listener. You are great at synthesizing inputs from different sources; you speak and write clearly, concisely, and with a structure that gets everyone on the same page when things feel messy.\n\n**Must haves**\n\nFluent in English.\nAt least three years of professional experience of developing and deploying production software.\nProfessional experience in at least one dynamically typed language (JavaScript, Ruby, Python etc).\nPersonally growth minded.\n\n**Nice to haves**\n\nProfessional experience at a software startup.\nExpertise in JavaScript and Ruby (React + Rails, even better!).\nExperience mentoring people technically.\nExperience building APIs.\n\n**What we offer**\n\n-A unique & fun culture at the intersection of the freight and technology industries as well as between the USA and Latin American work cultures.\n-Above market salary, benefits, and a robust employee stock ownership program to make you an owner and partner of the business.\n-Remote-first location strategy and allows you to work from wherever. Hybrid office / work from home model that allows for flexibility and collaboration time in our -Polanco / New York City office. Beautiful modern Polanco office space that is perfect for collaboration.\n-A chance to join the ground floor of a well-funded, fast-growing startup that is modernizing a trillion dollar industry critical to the global economy.\n\n**More about Nuvocargo**\n\nInternational logistics is the multi-trillion dollar connective tissue of the world economy, but it's been slow to leverage the power of technology; it's finally going digital, and Nuvocargo is playing a big role in driving this historic shift.\n\nWe believe that true expertise in logistics cannot be automated and is incredibly valuable; however, we think software and technology can give logistics professionals superpowers to help provide shippers with the best service, and make everyone's lives easier.\n\nWe're growing quickly, and are backed by some of the world's best investors from both Silicon Valley and Latin America such as Tiger Global Management, The Flexport Fund, QED (founders of $60B+ Capital One), NFX (Silicon Valley fund with $10bn in exits), the founders of Nubank ($30B+), Loft ($3B+), Ramp ($2B+), and Rappi ($5B+), Y Combinator (~1% acceptance rate, created $300bn worth of startups), and angels who have built, exited, or currently sit on the board of companies worth over $100 billion.\n\nOur DNA is comprised of four very distinct worlds and cultures: Silicon Valley, Logistics, Latin America, and USA. We are at the intersection of these worlds and laying the foundations for hyper-growth at one of the most tech-forward 3PL's in both the US and Mexico.\n\nRead more about us here: www.nuvocargo.com/about and feel free to reach out with any questions.\n\nWe look forward to working with you! \n\nPlease mention the word **RECONCILE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $70,000 — $120,000/year\n \n\n#Location\nUnited States and Mexico

# We're building the Data Platform of the Future\nJoin us if you want to rethink the way organizations interact with data. We are a **developer-first company**, committed to building around open protocols and delivering the best experience possible for data consumers and publishers.\n\nSplitgraph is a **seed-stage, venture-funded startup hiring its initial team**. The two co-founders are looking to grow the team to five or six people. This is an opportunity to make a big impact on an agile team while working closely with the\nfounders.\n\nSplitgraph is a **remote-first organization**. The founders are based in the UK, and the company is incorporated in both USA and UK. Candidates are welcome to apply from any geography. We want to work with the most talented, thoughtful and productive engineers in the world.\n# Open Positions\n**Data Engineers welcome!** The job titles have "Software Engineer" in them, but at Splitgraph there's a lot of overlap \nbetween data and software engineering. We welcome candidates from all engineering backgrounds.\n\n[Senior Software Engineer - Backend (mainly Python)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Backend-2a2f9e278ba347069bf2566950857250)\n\n[Senior Software Engineer - Frontend (mainly TypeScript)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Frontend-6342cd76b0df483a9fd2ab6818070456)\n\n→ [**Apply to Job**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp) ← (same form for both positions)\n\n# What is Splitgraph?\n## **Open Source Toolkit**\n\n[Our open-source product, sgr,](https://www.github.com/splitgraph/splitgraph) is a tool for building, versioning and querying reproducible datasets. It's inspired by Docker and Git, so it feels familiar. And it's powered by PostgreSQL, so it works seamlessly with existing tools in the Postgres ecosystem. Use Splitgraph to package your data into self-contained\ndata images that you can share with other Splitgraph instances.\n\n## **Splitgraph Cloud**\n\nSplitgraph Cloud is a platform for data cataloging, integration and governance. The user can upload data, connect live databases, or "push" versioned snapshots to it. We give them a unified SQL interface to query that data, a catalog to discover and share it, and tools to build/push/pull it.\n\n# Learn More About Us\n\n- Listen to our interview on the [Software Engineering Daily podcast](https://softwareengineeringdaily.com/2020/11/06/splitgraph-data-catalog-and-proxy-with-miles-richardson/)\n\n- Watch our co-founder Artjoms present [Splitgraph at the Bay Area ClickHouse meetup](https://www.youtube.com/watch?v=44CDs7hJTho)\n\n- Read our HN/Reddit posts ([one](https://news.ycombinator.com/item?id=24233948) [two](https://news.ycombinator.com/item?id=23769420) [three](https://news.ycombinator.com/item?id=23627066) [four](https://old.reddit.com/r/datasets/comments/icty0r/we_made_40k_open_government_datasets_queryable/))\n\n- [Read our blog](https://www.splitgraph.com/blog)\n\n- Read the slides from our early (2018) presentations: ["Docker for Data"](https://www.slideshare.net/splitgraph/splitgraph-docker-for-data-119112722), [AHL Meetup](https://www.slideshare.net/splitgraph/splitgraph-ahl-talk)\n\n- [Follow us on Twitter](https://ww.twitter.com/splitgraph)\n\n- [Find us on GitHub](https://www.github.com/splitgraph)\n\n- [Chat with us in our community Discord](https://discord.gg/eFEFRKm)\n\n- Explore the [public data catalog](https://www.splitgraph.com/explore) where we index 40k+ datasets\n\n# How We Work: What's our stack look like?\n\nWe prioritize developer experience and productivity. We resent repetition and inefficiency, and we never hesitate to automate the things that cause us friction. Here's a sampling of the languages and tools we work with:\n\n- **[Python](https://www.python.org/) for the backend.** Our [core open source](https://www.github.com/splitgraph/splitgraph) tech is written in Python (with [a bit of C](https://github.com/splitgraph/Multicorn) to make it more interesting), as well as most of our backend code. The Python code powers everything from authentication routines to database migrations. We use the latest version and tools like [pytest](https://docs.pytest.org/en/stable/), [mypy](https://github.com/python/mypy) and [Poetry](https://python-poetry.org/) to help us write quality software.\n\n- **[TypeScript](https://www.typescriptlang.org/) for the web stack.** We use TypeScript throughout our web stack. On the frontend we use [React](https://reactjs.org/) with [next.js](https://nextjs.org/). For data fetching we use [apollo-client](https://www.apollographql.com/docs/react/) with fully-typed GraphQL queries auto-generated by [graphql-codegen](https://graphql-code-generator.com/) based on the schema that [Postgraphile](https://www.graphile.org/postgraphile) creates by introspecting the database.\n\n- [**PostgreSQL](https://www.postgresql.org/) for the database, because of course.** Splitgraph is a company built around Postgres, so of course we are going to use it for our own database. In fact, we actually have three databases. We have `auth-db` for storing sensitive data, `registry-db` which acts as a [Splitgraph peer](https://www.splitgraph.com/docs/publishing-data/push-data) so users can push Splitgraph images to it using [sgr](https://www.github.com/splitgraph/splitgraph), and `cloud-db` where we store the schemata that Postgraphile uses to autogenerate the GraphQL server.\n\n- [**PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) and [PL/Python](https://www.postgresql.org/docs/current/plpython.html) for stored procedures.** We define a lot of core business logic directly in the database as stored procedures, which are ultimately [exposed by Postgraphile as GraphQL endpoints](https://www.graphile.org/postgraphile/functions/). We find this to be a surprisingly productive way of developing, as it eliminates the need for manually maintaining an API layer between data and code. It presents challenges for testing and maintainability, but we've built tools to help with database migrations and rollbacks, and an end-to-end testing framework that exercises the database routines.\n\n- [**PostgREST](https://postgrest.org/en/v7.0.0/) for auto-generating a REST API for every repository.** We use this excellent library (written in [Haskell](https://www.haskell.org/)) to expose an [OpenAPI](https://github.com/OAI/OpenAPI-Specification)-compatible REST API for every repository on Splitgraph ([example](http://splitgraph.com/mildbyte/complex_dataset/latest/-/api-schema)).\n\n- **Lua ([luajit](https://luajit.org/luajit.html) 5.x), C, and [embedded Python](https://docs.python.org/3/extending/embedding.html) for scripting [PgBouncer](https://www.pgbouncer.org/).** Our main product, the "data delivery network", is a single SQL endpoint where users can query any data on Splitgraph. Really it's a layer of PgBouncer instances orchestrating temporary Postgres databases and proxying queries to them, where we load and cache the data necessary to respond to a query. We've added scripting capabilities to enable things like query rewriting, column masking, authentication, ACL, orchestration, firewalling, etc.\n\n- **[Docker](https://www.docker.com/) for packaging services.** Our CI pipeline builds every commit into about a dozen different Docker images, one for each of our services. A production instance of Splitgraph can be running over 60 different containers (including replicas).\n\n- **[Makefile](https://www.gnu.org/software/make/manual/make.html) and** [docker-compose](https://docs.docker.com/compose/) **for development.** We use [a highly optimized Makefile](https://www.splitgraph.com/blog/makefile) and `docker-compose` so that developers can easily spin-up a stack that mimics production in every way, while keeping it easy to hot reload, run tests, or add new services or configuration.\n\n- **[Nomad](https://www.nomadproject.io/) for deployment and [Terraform](https://www.terraform.io/) for provisioning.** We use Nomad to manage deployments and background tasks. Along with Terraform, we're able to spin up a Splitgraph cluster on AWS, GCP, Scaleway or Azure in just a few minutes.\n\n- **[Airflow](https://airflow.apache.org/) for job orchestration.** We use it to run and monitor jobs that maintain our catalog of [40,000 public datasets](https://www.splitgraph.com/blog/40k-sql-datasets), or ingest other public data into Splitgraph.\n\n- **[Grafana](https://grafana.com/), [Prometheus](https://prometheus.io/), [ElasticSearch](https://www.elastic.co/), and [Kibana](https://www.elastic.co/kibana) for monitoring and metrics.** We believe it's important to self-host fundamental infrastructure like our monitoring stack. We use this to keep tabs on important metrics and the health of all Splitgraph deployments.\n\n- **[Mattermost](https://mattermost.com/) for company chat.** We think it's absolutely bonkers to pay a company like Slack to hold your company communication hostage. That's why we self-host an instance of Mattermost for our internal chat. And of course, we can deploy it and update it with Terraform.\n\n- **[Matomo](https://matomo.org/) for web analytics.** We take privacy seriously, and we try to avoid including any third party scripts on our web pages (currently we include zero). We self-host our analytics because we don't want to share our user data with third parties.\n\n- **[Metabase](https://www.metabase.com/) and [Splitgraph](https://www.splitgraph.com) for BI and [dogfooding](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)**. We use Metabase as a frontend to a Splitgraph instance that connects to Postgres (our internal databases), MySQL (Matomo's database), and ElasticSearch (where we store logs and DDN analytics). We use this as a chance to dogfood our software and produce fancy charts.\n\n- **The occasional best-of-breed SaaS services** **for organization.** As a privacy-conscious, independent-minded company, we try to avoid SaaS services as much as we can. But we still find ourselves unable to resist some of the better products out there. For organization we use tools like [Zoom](https://www.zoom.us) for video calls, [Miro](https://miro.com/) for brainstorming, [Notion](https://www.notion.so) for documentation (you're on it!), [Airtable for workflow management](https://airtable.com/), [PivotalTracker](https://www.pivotaltracker.com/) for ticketing, and [GitLab for dev-ops and CI](https://about.gitlab.com/).\n\n- **Other fun technologies** including [HAProxy](http://www.haproxy.org/), [OpenResty](https://openresty.org/en/), [Varnish](https://varnish-cache.org/), and bash. We don't touch them much because they do their job well and rarely break.\n\n# Life at Splitgraph\n**We are a young company building the initial team.** As an early contributor, you'll have a chance to shape our initial mission, growth and company values.\n\n**We think that remote work is the future**, and that's why we're building a remote-first organization. We chat on [Mattermost](https://mattermost.com/) and have video calls on Zoom. We brainstorm with [Miro](https://miro.com/) and organize with [Notion](https://www.notion.so).\n\n**We try not to take ourselves too seriously**, but we are goal-oriented with an ambitious mission.\n\n**We believe that as a small company, we can out-compete incumbents** by thinking from first principles about how organizations interact with data. We are very competitive.\n\n# Benefits\n- Fully remote\n\n- Flexible working hours\n\n- Generous compensation and equity package\n\n- Opportunity to make high-impact contributions to an agile team\n\n# How to Apply? Questions?\n[**Complete the job application**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp)\n\nIf you have any questions or concerns, feel free to email us at [[email protected]](mailto:[email protected]) \n\nPlease mention the words **DESERT SPELL GOWN** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Location\nWorldwide

*If there’s one thing that’s important to know about Culture it’s that we have a good culture.*\n\nFor example:\n- We value kindness and empathy over intellect and strong opinions.\n- We don’t use the word “resource” to refer to people.\n- Imagine a typical bro-y startup… now imagine the opposite… that’s us\n\n**The Company**\n\nCulture Biosciences grows organisms for biotech companies. We've built the first cloud bioreactor facility. Here’s how it works:\n\n* Our customers, biotechnology companies, design organisms (bacteria, yeast, mammalian cells) to produce products (materials, therapeutics, food).\n* We grow their cells in our bioreactors to optimize the yield of their products. Ultimately, we help our customers get their products to market faster.\n* Our customers receive their experimental results live on our website.\n* Our cloud bioreactor facility is made possible by custom software and automation technology that our team develops. The automated infrastructure is also more efficient to operate than traditional equipment. Our software also provides quick and simple data analysis, enabling customers to analyze reams of data quickly. \n\n**The Role**\n\nWe are looking for a frontend software engineer who wants to build the software platform that will transform biomanufacturing. You will collaborate with electrical, mechanical, biological, and chemical engineers to build our core technology. Your work will quickly impact cutting edge biotechnology companies by helping them get their products to market faster and more efficiently. \n \nWe have new and interesting software challenges. Our problems are more than scaling a web service: we model biological processes and operate mission-critical software within bioreactors that sometimes get wet. \n \nYou will work with our small, but growing, customer software team to design and build all aspects of our software for customers; from tools that allow our customers to turn around their experiments faster, to features that ensure the quality and safety of their experiments. \n\nWhat you'll do:\n* Help define our software engineering culture\n* Proactively solve the problems most important to the business\n* Write high quality software for the frontend\n* Write high quality software for the backend as well when needed\n* Do code reviews\n* Learn about fermentation, bio-manufacturing, and biotechnology\n\n\nIn return, we will support you by:\n* Placing a high degree of trust in your ideas and execution\n* Bringing you up to speed in the domain of fermentation\n* Providing a low-stress work environment\n* Making ourselves available for collaboration\n* Caring about you as a whole person, not a “resource”\n\nProjects on our horizon\n* Building the communication platform for bio-process planning and execution\n* Developing new data visualization and analysis tools for our customers\n* Expose complex bio-process protocol data in a simple understandable way\n* Provide live process controls (dangerous!) in a safe and intuitive way\n* And much, much more\n\n\nAbout You:\n* You have at least six years of experience in frontend software development\n* You know your way around modern JS, React, and css\n* You’re proactive and enjoy thinking about the big picture\n* You’re kind, curious and enjoy learning new things\n* You’re product focused - you think about the perspectives of end users even when it might not be expected of you\n* You value communication and connection with a multidisciplinary team\n* You care that you’re building something that solves a problem and helps end users\n\n\nBenefits include:\n* Competitive salary and equity compensation \n* Medical (PPO), Dental, Vision, and Life insurance\n* 401(k) plan with company match\n* 3 weeks of paid time off and 10 days of company holidays\n* 12 weeks of parental leave at full salary\n* Access to on-site child care facility, subject to availability\n* Free onsite breakfast, lunch, snacks, coffee, and gym (varies based on COVID-19 restrictions)\n* Support for relevant educational opportunities\n\nCulture Biosciences provides equal employment opportunities to all employees and applicants. We seek to build a company that promotes inclusion and expands the diversity of our industry as a whole. We encourage people with identities underrepresented in biotech and technology to apply. \n\nPlease mention the words **DIVERT CIVIL FLAVOR** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $150,000 — $175,000/year\n
\n\n#Benefits\n 💰 Equity compensation\n\n
\n\n#Location\nUnited States

\nAt Dataquest, we teach data science to a community of hundreds of thousands of students worldwide. We help students deeply learn concepts, build projects, work together, and gain the confidence they need to start new careers. Read more about our philosophy here, and read what students think here.\n\nWe want to eventually help tens of millions of students worldwide change their lives through data science education, and you’ll play a key role in helping us get there. We're looking for a Senior Frontend Engineer to help support and evolve our learning platform.\n\nWho Should Apply?\n\nWe’re seeking a senior frontend engineer who enjoys working on various frontend applications, building new features, and maintaining and enhancing our existing code. You’ll be responsible for driving progress and quality in our frontend codebase, so vision and strategy are key.\n\nYou must be passionate about learning, and enjoy developing new features without regressions and in a rapid iteration cycle. We’re seeking someone with senior level experience who enjoys mentoring other engineers. You’ll have a lot of autonomy in how you work and will be responsible for setting frontend development guidelines and best practices organization-wide.\n\nHow You’ll Contribute:\n\n\n* Lead the development and improvement of frontend features.\n\n* Help create an improved frontend architecture.\n\n* Set frontend development guidelines and code quality standards.\n\n* Mentor junior engineers.\n\n* Collaborate with the engineering team to develop a resilient and scalable frontend platform.\n\n* Decide when to incur and when to pay down technical debt.\n\n* Identify and fix frontend bugs.\n\n\n\n\n\nRequirements\n\nMust Have:\n\n\n* 5 + years of web development experience.\n\n* Strong verbal and written communications skills -- with an emphasis on clarity, empathy, and kindness.\n\n* Agile experience.\n\n* Experience measuring the effectiveness of the features you work on.\n\n* Experience leading architectural discussions and creating milestones.\n\n* Experience mentoring other engineers.\n\n* Experience maintaining a frontend build process.\n\n\n\n\n\nNice To Have:\n\n\n* Passion for education and/or education technology.\n\n* Passion for or interest in data science.\n\n* 2 + years of Python and Django experience.\n\n* You’re interested in and seek new technology that can improve your work.\n\n* Experience working remotely.\n\n\n\n\n\nOur Stack\n\nThese are some of the technologies you'll be working with at Dataquest, though you may end up introducing new ones:\n\n\n* Our frontend is a React using Redux, GraphQL, and WebSockets.\n\n* The backend is Django on Python 3.\n\n* We use Docker extensively, both for student code execution and for deployment of our services.\n\n* We use Kubernetes on Google Cloud to orchestrate our containers in production.\n\n* Our data is largely stored in Postgres, with some caching in Redis.\n\n* We use Git for source control, CircleCI testing, and deployment, and Prometheus with Grafana for monitoring and alerting.\n\n\n\n\n\nWhy You Should Work at Dataquest:\n\n\n* Flexible Paid Time Off.\n\n* Medical, Dental, and Vision Insurance and 401K (available to US team members).\n\n* The opportunity to see your impact on the lives of our students every day.\n\n* The chance to work with an engaged and mission-driven team.\n\n* The chance to contribute to product direction and decisions.\n\n* The ability to work remotely.\n\n* A supportive environment where you can get help when you run into blockers.\n\n\n \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Senior, Engineer, Front End, React, Education, Cloud, Git, Python, Junior and Backend jobs that are similar:\n\n $70,000 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n

\nHi there!\n\nWe're looking for a Frontend Engineer to join the engineering team at Zapier. Want to create a simple product that allows anyone to do complex, incredible things with the world's APIs? Then keep reading!\n\nWe know applying for and taking on a new job at any company requires a leap of faith. We want you to feel comfortable and excited to apply at Zapier. To help share a bit more about life at Zapier, here are a few resources in addition to the job description that can give you an inside look at what life is like at Zapier. We hope you'll take the leap of faith and apply.\n\n\n* Our Commitment to Applicants\n\n* Culture and Values at Zapier\n\n* Zapier Guide to Remote Work\n\n* Zapier Code of Conduct\n\n* Diversity and Inclusivity at Zapier\n\n\n\n\nZapier is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce.\n\nAbout You\n\nYou love code. You love to take raw ideas and build great products with JavaScript, HTML, and CSS. You know JavaScript is imperfect, but you embrace its functional side and genuinely enjoy coding with it. You might like to talk about obscure computer science topics, but really, you just want to write simple code and ship new products and features to customers (or improve existing ones).\n\nYou love great UX. You spend most of your time coding, but you also have an eye for great design and a feel for great UX. Maybe you were once a designer (or still are) or maybe your creative outlet has always been the code. Either way, you care about more than just the code.\n\nYou love learning new things. You love playing with new tech. Your focus is on frontend JavaScript code, but you can dig in wherever needed. Python, CSS, build tools, you name it. If you don't already know it, you're ready to learn it.\n\nYou can balance lots of concerns. Frontend apps have to take into account performance (using networks and devices that we can't control), customer demands, A/B tests, UX research, code quality, a rapidly changing ecosystem of languages and modules, and the list goes on. And we actually want to ship things too! You can balance those demands without getting overwhelmed and keep the needle moving forward.\n\nYou love helping others. You love sharing knowledge with the rest of your team, giving back to the open-source community, and directly helping customers.\n\n\n\nThings You Might Do\n\nZapier is a small, fast-growing, and remote-first company, so you'll likely get experience on many different projects across the organization. That said, here are some things you'll probably do:\n\n\n* Research, guide, and execute frontend architecture changes, including but by no means limited to GraphQL, server-side React rendering, and Flow typing.\n\n* Build reusable React components with modular CSS, manage data on the client with Redux and GraphQL, and test everything with Jest.\n\n* Refactor or improve existing code. We've migrated most of our frontend to React, but we still have some Backbone code to clean up. And we constantly find ways to improve all of our JavaScript code.\n\n* Work closely with our product, design, and UX teams to create amazing and intuitive experiences that make it effortless to connect different apps together.\n\n* Help put tools, processes, and documentation in place to improve our code quality.\n\n* Review code written by other team members or other teams.\n\n* Ship to hundreds of thousands of users every day while having lots of autonomy in terms of code and feature ownership.\n\n* Work with complex and varied data structures (APIs can be a little, uh, eccentric).\n\n* Help out with our Python backend or Node-based developer platform.\n\n* Share what you know and learn either one-on-one or with lightning talks to the group.\n\n* Give back to the community via open source and blog posts.\n\n* Experiment: this is a startup so everything can change as we experiment with doing more custom partnership work\n\n\n\n\n\n* As a part of Zapier's all-hands philosophy, help customers via support to ensure they have the best experience possible.\n\n\n\n\nYou’ll also have the opportunity to specialize in a variety of areas of the Zapier codebase, including core product or platform development. Focusing on a specialization will not limit your area for growth at Zapier as each engineer brings a unique perspective and can contribute differently in all areas. We encourage participation and will frequently have engineers contribute across teams to assist in projects. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Engineer, Front End, React, JavaScript, Python and Backend jobs that are similar:\n\n $62,500 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n