\nIntroduction to Demandbase: \n\nDemandbase is the Smarter GTM™ company for B2B brands. We help B2B companies hit their revenue goals using fewer resources. How? By aligning their sales and marketing teams around a combination of their data, our data, and artificial intelligence — what we call Account Intelligence — so they can identify, engage, and focus their time and money on the accounts most likely to buy. \n\nAs a company, we’re as committed to growing careers as we are to building world-class technology. We invest heavily in people, our culture, and the community around us. We have offices in the San Francisco Bay Area, Seattle, and India, as well as a team in the UK, and allow employees to work remotely. We have also been continuously recognized as one of the best places to work in the San Francisco Bay Area including, “Best Workplaces for Millennials” and “Best Workplaces for Parents”!\n\nWe're committed to attracting, developing, retaining, and promoting a diverse workforce. By ensuring that every Demandbase employee is able to bring a diversity of talents to work, we're increasingly capable of living out our mission to transform how B2B goes to market. We encourage people from historically underrepresented backgrounds and all walks of life to apply. Come grow with us at Demandbase!\nAbout the Role:\n\nWe’re looking for a Software Engineer to develop and maintain the backend that powers our ABX & Sales Intelligence Cloud.\n\nThe compensation range for this role is: $108,000 - $162,000\nWhat we’re looking for:\n\n\n* Minimum of 2 years of relevant work experience as either a full stack engineer, backend engineer or frontend engineer.\n\n* Experience building microservices in Java/Scala\n\n* Solid understanding of building APIs atop RDBMS\n\n* Attention to detail at a visual and technical level\n\n* Has a product-oriented mind and strong desire to solve problems for customers\n\n* Should help drive thoughtful and testable API design\n\n* Experience working closely with UX and Product\n\n* Experience working closely with cross-functional platform engineering teams \n\n\n\nWhat you’ll be doing:\n\n\n* Help develop and maintain the backend that powers our ABX & Sales Intelligence Cloud, primarily with Java/Scala microservices.\n\n* Help develop and own our single-page React (Typescript) application and set technical direction and standards across the product & engineering organization, participate in code reviews and help develop best practices. \n\n* Work on a cross-functional team (Product Managers, UX, and FE & BE engineers) to design, develop, test, and release rich and robust new functionality based around sophisticated ML-driven analytics and complex orchestration flows to drive sales and marketing automation\n\n* Work with Cloud Ops, QA, and Engineering to jointly own industry standard build, test, deploy pipelines, driving for best in class release processes. \n\n\n\nAdditional Experience Helpful for Success in this Role:\n\n\n* Has worked on large B2B and SaaS applications leveraging React, Redux, and Sagas.\n\n* Typescript experience or a strong desire to learn.\n\n* Experience using data visualization libraries like Highcharts or D3.\n\n* Strong Kubernetes and/or Istio experience \n\n* Experience with implementing and owning CI/CD pipelines (esp in Gitlab) \n\n* Experience with Postgres, ZIO, Clickhouse, Iceberg, Spark\n\n\n\n\nBenefits:\n\nOur benefits include options for up to 100% paid Medical and Vision premiums for employees, flexible PTO policy, no internal meeting Fridays, Modern Health mental wellness platform, and 11 paid holidays and 2 additional weeks where all Demandbase employees take off (the week of July 4th and the week of Thanksgiving). Plus 401(k), short-term/long-term disability, life insurance, and all those good things.\n\nOur Commitment to Diversity, Equity, and Inclusion at Demandbase\n\nAt Demandbase, we believe in creating a workplace culture that values and celebrates diversity in all its forms. We recognize that everyone brings unique experiences, perspectives, and identities to the table, and we are committed to building a community where everyone feels valued, respected, and supported. Discrimination of any kind is not tolerated, and we strive to ensure that every individual has an equal opportunity to succeed and grow, regardless of their gender identity, sexual orientation, disability, race, ethnicity, background, marital status, genetic information, education level, veteran status, national origin, or any other protected status. We do not automatically disqualify applicants with criminal records and will consider each applicant on a case-by-case basis.\n\nWe recognize that not all candidates will have every skill or qualification listed in this job description. If you feel you have the level of experience to be successful in the role, we encourage you to apply!\n\nWe acknowledge that true diversity and inclusion require ongoing effort, and we are committed to doing the work required to make our workplace a safe and equitable space for all. Join us in building a community where we can learn from each other, celebrate our differences, and work together.\n\n  \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to SaaS, React, Education, Cloud, API, Marketing, Sales, Engineer and Backend jobs that are similar:\n\n $70,000 — $110,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\nSan Francisco, California, United States

At 800.com, we’re building an intuitive & powerful cloud communications platform for SMB & Enterprises to communicate via Voice & SMS.\n\nOur backend tech stack currently consists of PHP web apps that serve a public API that our front-end JavaScript app consumes (React / React Native). Our data stores include MySQL, Elasticsearch, and Redis. The underlying infrastructure runs on AWS using a combination of managed services like RDS and non-managed services running on EC2 instances. All of our development runs through CI/CD pipelines that build Docker images.\n\n## About You\n\nWe’re looking for an experienced full-time Software Engineer to join our engineering team. Someone who has a solid understanding of web technologies and wants to help design, implement, launch, and scale major systems and user-facing features.\n\nYou should have senior-level experience (~7 years) building modern back-end systems, with at least 5 years of that experience using PHP, 3-years using Laravel, and 1+ year working with React.\n\nYou also have around five years of experience using MySQL, Redis, or similar data stores. You have significant experience designing, scaling, debugging, and optimizing systems to make them fast and reliable. You have experience participating in code reviews and providing overall code quality suggestions to help maintain the structure and quality of the codebase.\n\nYou’re comfortable working in a fast-paced environment with a small and talented team where you’re supported in your efforts to grow professionally. You are able to manage your time well, communicate effectively and collaborate in a fully distributed team.\n\nYou are based in the United States.\n\n## Required Skills & Experience\n\n* 5+ years experience with PHP development (Laravel, Symfony, WordPress)\n* You have 1-3 years of React knowledge and experience\n* Strong knowledge of SQL (writing and optimizing queries)\n* Experience with REST, XML, JSON, etc.\n* Version control using git on Bitbucket\n* Familiarity with Agile best practices\n* Able to solve problems in a simple, neat, and organized way\n* Experience working in an agile environment, scoping and road-mapping, and self-management\n* Knowledge of web performance and speed/memory optimization techniques\n\n**Bonus Required Skills & Experience:**\n\n* Understanding of test-driven development and testing in general\n* Experience in GraphQL and/or “Headless” CMS development\n* API design experience for frontend or server-to-server\n* Basic understanding of web servers, SSL, deployments, and continuous integration\n* Worked with a QA team before or familiarity with QA/release workflows\n\n## Come help us with projects like\n\n* Conceiving, designing, building, and launching new user-facing features\n* Improving our vanity phone number algorithm to secure the best matching phone numbers for customers\n* Innovating on business texting to include; auto-reply, scheduled messages, dynamic templates, keyword triggers, and reporting\n* Working with Twilio’s API, Bandwidth API, WebSockets, and WebRTC to improve our calling features\n* Building user-facing analytics features that provide actionable insights\n* Improving our internal messaging infrastructure using streaming technologies like Redis\n* Building new and enhancing existing integrations with other SaaS platforms like Google’s G Suite, Zapier, and Web Conferencing providers\n\n## Why 800.com?\n\n* 100% remote (we believe in trust and autonomy)\n* Competitive salary\n* Flexible vacation plan (includes company-wide winter holiday break)\n* $200/month co-working stipend\n* 401k matching at 4% (US residents)\n* Dependent care FSA (US residents)\n\n*800.com asks respectfully to only apply through the application form and do not email/apply directly to 800.com. Any applications sent directly to 800.com will not be considered. Recruiters and Agencies please do not contact 800.com directly.* \n\nPlease mention the word **TRUTHFUL** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMzc=). 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 — $250,000/year\n
\n\n#Benefits\n 🌎 Distributed team\n\n
\n\n#Location\nRemote in the United States

### About SchemeServe\nSchemeServe is UK based Insurance SaaS solution offering marketing support and consultancy to brokers, underwriting agencies and insurance companies. SchemeServe specializes in services for starting, managing and growing traditional and specialist insurance products. Started in 2000, SchemeServe gives the leading edge in super fast scheme deployment and has grown into the platform of choice for hundreds of insurance products worldwide.\n\nWe are a fully remote company although meet together once a quarter for some serious (and some not so serious) time together.\n\nAs we are remote there is, unfortunately, no unlimited kitchen or bean bags, but we offer the flexibility to those in the UK who want work to fit around their life!\n\nOur Tech Stack is currently .NET, Microsoft SQL, Azure hosting. We are in the process of transforming to an API first backend in .NET Core with a React front end.\n\n### Job Description\nWe are looking for a passionate UK based .net Developer specifically with experience in .net core/5.\n\nYou will need to coordinate with the rest of the team, working on different layers of the infrastructure. Therefore, a commitment to collaborative problem solving, sophisticated design, and a quality product are important. As this is a fully remote position the ideal candidate will need to be able to work well on their own and form a productive environment, as well as manage their own time effectively to ensure prompt delivery of work.\n\n### Responsibilities;\n* Develop software solutions by studying information needs; conferring with users, studying systems flow, data usage and work processes, investigating problem areas, following the software development lifecycle.\n* Working as part of a larger agile team\n* Writing tests on all development work written.\n* Update job knowledge by studying state-of-the-art development tools, programming techniques and computing equipment; participating in educational opportunities, reading professional publications, maintaining personal networks and participating in professional organisations.\n* Protect operations by keeping information confidential.\n* Work collaboratively with others to achieve goals.\n* Be a persistent, creative problem ­solver.\n* Remain cool and effective in a crisis.\n* Stay on the leading edge of development practices.\n* Be passionate about great technologies, especially open source.\n* Understand business needs and know how to create the tools to manage them.\n\n### Requirements;\n* 3+ years experience working with C# .net (preferably .net core/.net 5).\n* Restful API design experience.\n* A solid understanding of modern security practices.\n* Experience working with modern cloud providers (preferably Microsoft Azure).\n* Experience working within an agile development team using CI/CD practises.\n* Excellent communication skills both written and verbal in English\n\n### Nice to haves;\n* Experience within the Insurance or Finance professions would be useful to understand compliance requirements.\n* Experience with working on service-based architecture models.\n* Experience working with React JS.\n\n### Note for recruiters\nWe are not currently accepting any candidates from recruiters that we do not already have a working agreement with.\nYou are welcome to send an email if you really want, but it will be ignored :-) \n\nPlease mention the words **WINTER JUDGE SCENE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMzc=). 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 $40,000 — $50,000/year\n \n\n#Location\nuk

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