\n(Toronto area candidates preferred or remote in GMT-4, GMT-5, GMT-6, GMT-7, and GMT-8 timezones. All candidates should have eligibility to work in Canada. We are not offering working visa sponsorship at this time so please apply only if you are eligible to work in Canada)\n\nCrowdlinker is an end-to-end digital product studio based in Toronto and Barcelona with a relentless focus on our customers. We connect people through technology by being the strongest link between companies, their ideas, and their clients. We do so by excelling at digital strategy, creative design, full-stack development of websites & web/mobile apps, and digital marketing (SEO, SEM, PPC, Marketing Automation). Our clients include large startups like Freshbooks, TopHat, League, and Second Closet, as well as enterprises like Unilever, Nestlé and NBC Universal. We create cutting-edge applications using the latest technologies and design them with an exceptional user experience.\n\nAs a Full-Stack Developer, you will be responsible for ensuring that user stories and features of projects are executed using sound development practices and the most up-to-date and reliable tools. You will collaborate with product managers and designers to ensure that the problem is being solved in the correct manner. Every team member at Crowdlinker is equally responsible for the success of the project as a whole and so you will bring a strong level of organization, communication and accountability to the work that you do.\n\nWe are looking for someone to be a Full-Stack Ninja, and so your ability to code the front-end is critical and a strong understanding of the back-end is needed. We are looking for developers with an obsession for clean, well-structured coding practices who think about the sustainability of the products they build.\n\nWe are growing quickly, which means there are always new and exciting challenges at Crowdlinker. We are looking for someone who is comfortable taking risks and solve burning problems. We embrace change, see challenges as opportunities and focus on solutions. We do offer great pay and benefits. We hope you can join us to push the boundaries of what’s possible.\n\nRequirements\n\nMust Haves:\n\n\n* 2-3+ years of web / mobile development experience.\n\n* Proficient knowledge of at least one backend programming language like Node.js / Python / PHP\n\n* Excellent understanding at least one backend framework like Express, NestJS, Laravel or Django etc\n\n* Experience working with SQL databases (PostgreSQL/MySQL) OR NoSQL databases (MongoDB, DynamoDB, Redis, etc.)\n\n* Experience working with REST APIs\n\n* Proficient in using front-end frameworks such as React.js, React Native or Vue.js\n\n* Proficient with TypeScript, ES5/ES6, state management libraries like Redux / Context API, React Hooks, JSX and CSS-in-JS\n\n* Experience designing application architectures and concepts like unit testing, TDD, and continuous integration.\n\n* Impeccable written and verbal communication skills as you will be working closely with designers, product managers and sometimes clients.\n\n* A sound understanding of design concepts and best practices required to build systems with considerations for scalability, performance, maintainability, testability, and extensibility\n\n* Strong understanding of project management tools in the Atlassian Suite (Jira, Bitbucket, Confluence etc.)\n\n* Experience working with Agile principles.\n\n* Experience with Git for version control\n\n* Proficient in writing maintainable CSS / SCSS with a strong understanding of Flexbox & experience working with responsive web design frameworks, such as Bootstrap / Zurb Foundation.\n\n* Have excellent communication, collaboration skills and comfortable communicating via email, Slack or on video calls.\n\n\n\n\nNice to Haves:\n\n\n* Experience with GraphQL\n\n* Experience with testing libraries like Jest, Cypress, etc.\n\n* Experience with Docker\n\n* An overall understanding of popular frontend and backend languages, their associated frameworks and their upsides/downsides. \n\n* Can mentor and coach other developers to skill up in their craft. \n\n* Familiarity with cloud providers, such as AWS, Google Cloud Platform and Digital Ocean.\n\n* An impressive portfolio / Github handle to demonstrate skillsets.\n\n\n\n\nResponsibilities\n\n\n* Participate in technical design and planning discussions\n\n* Work closely with our designers on implementing designs into code.\n\n* Work closely with our product managers to ensure projects are delivered in a timely fashion.\n\n* Provide timely and accurate estimates for project deliverables.\n\n* Hands-on troubleshooting, debugging and fixing of issues during development and post-release.\n\n* Participate in and contribute to client meetings and proposals.\n\n* Lead, mentor and coach our developers to level them up in their craft\n\nWe don't expect you to know all of the above! We're always constantly working with new technologies and learning is a part of the job!\n\n\n\n\nWhat’s in it for you?\n\n\n* Gain experience working with team of experienced developers.\n\n* Learn and implement the latest and greatest in new frameworks and technologies. (Receive up to $10k to take relevant courses.)\n\n* Learn faster by working on a variety of client projects throughout the year.\n\n* A ground-level opportunity to join a growing company early and accelerate your career.\n\n* Code with us the sensible way, using continuous integration, automated testing and deployment, proper testing/staging servers, Git repos with proper branching and all other DevOps practices that make developers’ lives easier overall.\n\n* A strong culture of excellence, mutual mentorship, and transparency.\n\n* The chance to work in fully operational, cross-functional product teams, giving you the opportunity to enhance your understanding of design, digital marketing and product management.\n\n\n\n\nPerks\n\n\n* Competitive compensation.\n\n* Potential for stock in the company.\n\n* 5 weeks paid vacation.\n\n* Comprehensive medical and dental plan, which includes $800 per practitioner (e.g. massage therapy, physiotherapy, orthotics, acupuncture, etc...)\n\n* Cool office in trendy Entertainment district at 119 Spadina Avenue.\n\n* Flexible hours with an option to work from home.\n\n* Optional computer hardware.\n\n* Optional company mobile hardware and phone plan.\n\n\n\n\nDuration of the role\n\nThis is a full-time, permanent role, not a contractor position. \n\nHow to apply\n\nIn your application, please include:\n\n\n* A link to your GitHub profile if you have one.\n\n* A link to your LinkedIn profile if you have one.\n\n* A link to your portfolio of work if you have one.\n\n* A summary of how you would be able to make a difference in our team.\n\n\n\n\nYou may include a traditional resume and cover letter as well, although it is not required. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Full Stack, Developer, Digital Nomad, React, DevOps, Video, Laravel, Cloud, CSS, NoSQL, Git, Python, Mobile, Marketing, Medical 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

# 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 (#RMjE2LjczLjIxNi4xMg==). 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