At Fluxx, our mission is to be the leading collaborative grantmaking platform that amplifies impact in our global communities. We’re a mission-driven business making an impact in philanthropy, and our cloud platform enables the end-to-end grantmaking process for funders and doers. We volunteer, serve our community, and we’re committed to building a team of outstanding individuals with diverse backgrounds and perspectives. We are looking for the best talent to continue to drive our mission forward.\n\nIn the role of Senior Software Engineer, you’ll play a critical role in building high-quality, innovative, and performant software that aligns with industry standards and best practices.\n\nThis is a full-time exempt and remote position. Candidates must be located in the United States.\n\nWhat you'll be doing:\nProvide technical leadership, bringing best engineering practices to all phases of large-scale engineering initiatives\nWork cross-functionally with engineers, designers, QA, and product managers\nDesign and execute new user-facing features and applications\nBuilding test automation to ensure quality release after release\nLead initiatives to refactor, re-engineer, and reimagine our platform\nProduce high-quality software that is well designed, fully unit tested and passes peer code review\nDeliver projects with high quality and at a rapid cadence\n\n\nWhat you bring to the team:\nExperience as a full-stack engineer (frontend + backend development).\nAt least 4 years of experience building, fixing, and scaling web apps\nDesire to learn and mentor\nStrong communication and collaboration skills\nProficiency with SQL and Unix\nA deep foundation in computer science with a strong understanding of data structures, and algorithms\nDedication to writing maintainable, fast, beautiful code including documentation\nAn ability to learn and adapt quickly\n\n\nYou’ll have a better chance of success given experience with:\nLarge refactoring/re-engineering projects\nWorking in at least some of our stack:\nRuby, Rails\nMySQL\nElasticsearch\njQuery, React\nRedis, Resque\nJava\nPlay\nDevops and AWS\nRESTful APIs\n\n\nAbout Fluxx:\nAt Fluxx, we're looking for people with grit and passion about Fluxx’s vision to become THE company that changes Philanthropy forever. We encourage you to apply - even if your experience doesn't exactly match the job description. Your skills and passion will stand out especially if your career path is unique. \n\nPlease mention the word **FAST** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMTQ=). 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 $160,000 — $170,000/year\n \n\n#Location\nUnited States

At Jungle Scout, we are on a mission to empower entrepreneurs and brands to grow successful e-commerce businesses, and we provide the industry-leading data, powerful tools, and resources they need.\n\nThe role:\n* Do you get excited working with talented engineers, leading them to ship product features and enhancements, and helping them thrive in their career?\n* Do you define a great day as getting sh*t done and having fun working with your team?\n* Do you have a thirst for breaking down complex initiatives into achievable project plans?\n* Do you thrive when you're contributing to a high-performing, humble team?\n\nAmazing, then you’re the type of person we’re looking for!\n\nWe’re growing and we are looking to add a Senior Backend Engineer to the Engineering team focused on building Jungle Scout’s enterprise SaaS product. \n\nWhere would this person be located? Great question! We’re a remote-first company and hope to hire this Senior Software Engineer Team **anywhere between the EST - PST timezone**\n\nInterested in learning more? Let’s get into the details: \n\n**What you will be doing:**\n\nArchitect and build: \n* Highly scalable, fault-tolerant, elastic, and secure services\n* Large scale distributed systems\n* Applications that are a composition of independent services (microservices)\n\nMake recommendations around:\n* Technologies to be used for new services and applications \n* Improvements on existing services and applications\n\nScale, maintain and improve:\n* Existing codebases and system infrastructures\n* Independent services using CI/CD and multiple environments stages (e.g., staging vs. production) to ensure rapid delivery while maintaining high quality and availability\n\nParticipate and contribute in:\n* Leading the technical architecture and delivery of complex projects, interfacing with product, design, and multiple engineering teams\n* Helping product managers with project planning and facilitating the Scrum process\n* Ongoing improvement of engineering practices and procedures\n\n**Who you are:**\n\n* You’ve done this before. \n* You’re an expert with one or more modern programming languages (Ruby, Javascript, Python, Java), technologies, coding, testing, debugging, and automation techniques\n* Have built enterprise-level services with popular backend frameworks (e.g., Ruby on Rails, NodeJS, Spring, Django, Flask, etc)\n* You have experience building data-driven systems that have high availability, optimize for performance, and are highly scalable\n* You’re experienced with modern SQL and NoSQL databases, know when to use each, and can build performant systems on top of each\n* You’re an AWS Cloud Wizard.\n* You’re an AWS cloud ninja and you have experience building cloud-native services at scale\n* Experience working with core AWS services like EC2, RDS, DynamoDB, Elasticsearch, ElasticBeanstalk, Lambda, Cloudwatch, SQS, Kinesis and SNS.\n* You’re a master communicator & passionate mentor. \n* Fluent in both written & verbal English to easily chat with our North American teams. \n* Able to communicate effectively, clearly, and concisely on both technical and non-technical subjects. \n* Take any chance you can get to share knowledge with your team. \n* Contribute to the team’s documentation and mentor teammates in an open, respectful, flexible, empathetic manner. \n* Do not shy away from taking and giving feedback.\n* You’re autonomous. \n* Successfully execute large multi-person projects and well-defined initiatives from definition through to the end.\n\n**Working at Jungle Scout\n**\n[Check us out!](https://www.junglescout.com/jobs/)\n* The BEST team. \n* Remote-first culture.\n* International Retreats.\n* Access to Jungle Scout tools & experts.\n* Performance Bonus. \n* Flexible Vacation. \n* Comprehensive Health Benefits & Retirement Program. \n\n**We prioritize Diversity, Equity, and Inclusion \n**\nAt Jungle Scout, we hire great people from a wide variety of backgrounds, not just because it’s the right thing to do, but because it makes our company stronger. \n\nJungle Scout is committed to creating a diverse environment and is proud to be an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, or veteran status.\n\n*All offers of employment at Jungle Scout are contingent upon clear results of a comprehensive background check. Background checks will be conducted on all final candidates prior to start date.* \n\nPlease mention the words **MISERY ALARM PARTY** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMTQ=). 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 $10,000 — $200,000/year\n \n\n#Location\nNorth America and South America

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

\nWe're looking for a talented software developer to work on the server-side of our music delivery service: music ingestion and delivery, analytics collection and reporting, and web services used by our clients and curation team. Your goal will be to help us power sound everywhere. \n\nYou will need to form a full understanding of our data model, how we map our music providers’ schemas to it, and how we expose it to our clients. You will be working with our primary data stores: MySQL, ElasticSearch and Google BigTable. You will work on all our backend services, written primarily in Node.js, along with PHP and Bash scripts.\n\nYou will work hand-in-hand with our current engineering team, music curators, customer support, and product team to define and develop whatever is needed to advance our business. You will work with and develop our tools and services that:\n\n\n* Ingest files and metadata from our music providers\n\n* Analyze and extract metadata from our music collection\n\n* Deliver music to applications using our client SDKs\n\n* Track music playback and generate reports for our music providers and licensors\n\n* Generate analytics and reporting from playback and client data\n\n* Power our customer and client portals\n\n\n\n\nYou are, at heart, a problem solver, and eager to collaborate with others to deploy working solutions to advance our business. You are eager to understand how the tasks you are working on fit into the bigger picture and you proactively engage with others to clarify and refine what you are working on.\n\nWe manage our infrastructure with Chef and Terraform, and use Jenkins and Git for deployment. We strive for reliability and simplicity, and look to outside SaaS providers when the price is right. You will take part in managing and supporting our staging and production environments.\n\nAt Feed.fm, we believe the best candidates are excellent communicators, learn quickly, are compassionate, collaborate well with others, and have a strong desire to see their work in action. We are flexible with working hours and maintain a healthy balance between work and personal lives.\n\nRequirements\n\n\n* Outstanding communication skills and an eagerness to collaborate with others\n\n* Experience building and maintaining production web services\n\n* Strong Node.js development experience\n\n* Strong SQL experience, particularly MySQL\n\n* Familiarity with server side languages such as Go, Java, PHP.\n\n* Strong operational experience with Linux and cloud computing providers (AWS, Digital Ocean, Google Cloud, or others)\n\n* Experience with cloud provisioning and infrastructure management tools such as Terraform and Chef.\n\n* Experience with test driven development\n\n* Strong desire to ship, receive feedback, and improve\n\n* Ready to take responsibility for production systems\n\n\n\n\nBonus:\n\n\n* Experience with storing and processing event streams\n\n* Experience with generating reporting and analytics\n\n* Terraform, GraphQL, Kinesis, ElasticSearch experience\n\n* Past experience with server or client side audio processing\n\n* Past experience implementing or working with music-related applications\n\n* Contributions to open-source projects\n\n* Familiarity with frontend web development: Javascript (and popular frameworks, like React, jQuery, and others), HTML, CSS.\n\n\n\n\n Benefits:\n\n\n* Competitive salary\n\n* Equity\n\n* Comprehensive health, dental, vision and disability insurance along with a 401k matching plan.\n\n* Working with a talented team and having a huge impact!\n\n\n\n\nWhy Feed.fm?\n\nWe're providing music for companies you know and love: FitBit, Nautilus, Tonal, Mirror, American Eagle Outfitters, Bose, Life Fitness, and others\n\n\n* We're building a real company that generates value and pays artists\n\n* You will have a hand in all aspects of a growing platform\n\n* Experienced, down-to-earth coworkers and investors\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, Developer, Digital Nomad, JavaScript, Music, Elasticsearch, Cloud, PHP, Git, SaaS, Linux and Backend jobs that are similar:\n\n $65,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