\n\nBased in Washington, D.C., United States, Quorum is the leading provider of workflow software for government affairs professionals across Fortune 100 corporations, non-profits, associations, and governmental end-markets. Quorum’s innovative AI-powered integrated cloud platform allows users to manage stakeholder engagement, launch grassroots advocacy campaigns, manage PACs (Political Action Committees), and track legislative activity at all levels of government, including federal, state, local, EU, and internationally.  \n\nHelp us build the future of PAC management software! As the Engineering Manager of the Quorum PAC Expansion software team, you will coach, manage, and support a squad of full-stack engineers focused on building new PAC features to support our growing list of customers. As Engineering Manager, you will be hands-on and own the technical roadmap planning and execution in collaboration with the PAC Product Manager, peer engineering managers, Product Design, and QA. In managing the individual contributors, hands-on coding and technical guidance are expected at about 50% in any given week, though delegating technical tasks is usually expected. As the Engineering Manager, you will deliver high-quality results and work through risks, challenges, and obstacles, all while setting and managing expectations with various stakeholders. \n\nWhat You'll Do\n\n\n* First Week: You will work closely with an onboarding mentor to complete the standard engineering onboarding process and learn to ship new code to production to understand the end-to-end tech stack and software development lifecycle.\n\n* First Month: You will be up and running with your standard managerial practices and processes, learn the ins and outs of Quorum’s PAC product, technical strategy, roadmap, and challenges, and get to know the members of your team, product managers and other leaders on the technology team.\n\n* First Three Months: You will fully own the planning and execution of the PAC Expansion team, including technical roadmap and milestones. You will mentor and coach existing team members to improve their skills & team productivity and help bring new team members into the organization as needed. \n\n* First Six Months: Your team will have successfully shipped many new features, improved team operations and effectiveness, and facilitated the onboarding of new customers.\n\n\n\n\nAbout You\n\n\n* 5+ years of relevant experience, including 1+ years as an Engineering Manager and/or Tech Lead with proven technical and leadership abilities.\n\n* Data expertise: data modeling in relational & non-relational databases, data quality, data integration, search, data visualization, and performance tuning. \n\n* Expertise in software development and Quorum’s front-end and back-end technologies, including must-have Python and React (or similar Javascript framework), PostgreSQL, AWS, and Linux. Nice to have: Django. \n\n* Experience with cloud-native architectures, AWS preferred.\n\n* Experience with Docker and containerized build and deploy pipelines. \n\n* Excellent communication skills, including good English\n\n* Strong, agile project management skills as demonstrated by a strong track record of completing complex technical projects that this individual directly owned\n\n* Strong coaching and management skills as indicated by a strong track record of supporting the growth and development of other engineers\n\n* Experience with US-based companies as part of a remote or hybrid team is preferred.\n\n* This position requires approximately 50% hands-on development time. \n\n\n\n\nAbout the Software Development Team\n\n\n* We're a fast-growing team dedicated to improving our people, processes, and platform. The team is primarily structured into product-oriented squads.\n\n* We support many different products but internally think of them as one system with a single unified codebase supporting the Quorum platform. We aim to build centralized systems that handle complex problems for multiple features and products.\n\n* We’re focused on doing the important things the right way -- we write solid documentation, test our code well, design for scale, and follow defined software development processes.\n\n* We follow best-in-class security practices to safeguard our data and application against bad actors. We regularly test and update processes and technology to fight complacency because we know good security is a continuous effort.\n\n* We curate high-quality datasets essential for effective mapping and tracking of the government and public affairs spaces. Our datasets underpin our promise to give users the information necessary to make intelligent decisions influencing policy.\n\n* We set rigorous quality standards and monitor them with a mix of programmatic and manual verifications to ensure users maintain high trust in our systems.\n\n* We’re very close as a team and invest not only in each others’ skills and careers but also in building genuine relationships with one another: product development is a team sport where open communication and collaboration lead to amazing outcomes for our customers. We believe it’s better (and more fun) to work on a team of people you know well and care about.\n\n\n\n\nOur Work Environment\n\n\n* We are a remote-first team with flexible work options: work remotely, or you may choose to come into our office in Belo Horizonte.\n\n\n\n\nDo you want to learn what it's like to have a real impact at a fast-growing company that is changing the way the advocacy process works? If so, drop us a line. We'd love to talk to you!\n\n\n* This is a full-time CLT position.\n\n\n\n\nBenefits\n\n\n* Standard Brazil Holidays\n\n* Monthly Work from Home Stipend\n\n* Mental and Dental Care by SulAmérica\n\n* Monthly Professional Development/Mental Health stipend\n\n* Alelo Food Voucher\n\n* Incompany English classes with a native speaker teacher\n\n* Free Subscription to the Calm app\n\n* Invest in Yourself Days - one Friday per quarter is dedicated to your professional development!\n\n* Flexible Paid Time Off\n\n* Virtual and in-person team events\n\n* Inclusion & Diversity Affinity Groups to support belonging\n\n* 12 weeks of paid parental leave\n\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 Design, React, Python, Docker, JavaScript and Cloud jobs that are similar:\n\n $57,500 — $105,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
\n\n#Location\nBelo Horizonte, Minas Gerais, Brazil

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

### NYC (Or Remote)\nCroscon plans, builds, and grows digital products and services that help companies become leaders in their industry. Our clients range from startups looking to get to market with an MVP or large companies like Google, Soundcloud, NASA, SEIU, among many others.\nWe present a unique opportunity for a seasoned engineer to work on a variety of projects in a variety of industries. Our team is small, driven and pull off projects that others simply can’t. You’ll work directly with principal engineers and product leads to plan and execute digital products for our clients. Additionally, Croscon is incubating it’s own companies for which we retain full ownership and control.\nSuccess in this role will lead to engineering and/or product managerial roles.\nTo learn more, please visit: http://www.croscon.com/\n\n\n**Requirements:**\n- 3-4+ years of professional enterprise web development experience\n- Experience with modern backend web frameworks and libraries: Flask & Django\n- Expert in various database and modeling paradigms (MongoDB/NoSQL, MySQL, Postgres).\n- Experience with modern client web programming languages and standards: JavaScript, CSS3, HTML5, etc.\n- Deep understanding of web architecture including the HTTP protocol, caching proxies, REST services, etc.\n- Strong understanding of designing secure systems.\n- Experience with distributed architectures and measuring system performance metrics.\n- Expert in common software engineering practices, such as version control with Git, unit tests, continuous integration, and automated deployment.\n- Strong Experience with public cloud systems (Amazon Web Services, Google Cloud Platform).\n- ORM Experience -- SQLAlchemy / peewee\n- Queuing: Celery, RabbitMQ\n- Redis\n- Docker\n\n\n**Nice to have:**\n- Elasticsearch/Solr\n-Kubernetes\n- Serious DevOps or SysAdmin experience\n- Supervisor experience (or any other long running process manager experience, e.g., pm2)\n- Salt / Ansible experience\n- React / ES6 experience\n- Jenkins \n\nPlease mention the words **VAGUE WHISPER GESTURE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xNDY=). 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 No salary data published by company so we estimated salary based on similar jobs related to Python, Docker, Web Developer, Developer, Digital Nomad, React, DevOps, Cloud, Engineer and Backend jobs that are similar:\n\n $67,500 — $120,000/year\n