The Opportunity\n\nAI is rapidly changing the world. From processing job applications and credit decisions, to RAG-based chatbots, to making content recommendations and helping researchers analyze genetic markers at scale -- many aspects of our daily lives are touched by machine learned systems in some way. \n\nArize is the leading machine learning observability platform to help ML teams discover issues, diagnose problems, and improve the results of machine learning models. We are here to build world class software that helps make AI work better.\nThe Team\n\nOur Fullstack engineering team is responsible for building highly robust, yet seamless features, to Arize AI’s main product offering. These teams bring complex ML and LLM workflows to life by allowing a variety of clients / end users to interpret, visualize, and monitor the performance of their AI and ML models, pre and post production. Our Frontend and Fullstack Engineers are tasked with creating easy-to-use data visualization and observability experiences, in close collaboration with our Product, Design, and Platform Engineering teams.\n\nWhat You’ll Do\n\n\n* Write maintainable, scalable server-side Javascript for a real-time SaaS application\n\n* Design domain / object models and work with analytical data stores to create critical MLOps functionality.\n\n* Design and build out performant and reusable react components that will be used throughout the application.\n\n* Participate in or lead architectural decisions for new and existing features in collaboration with product, design and our backend teams. \n\n* Contribute to design & code reviews and technical documentation.\n\n\n\n\nWhat We’re Looking For\n\n\n* 5+ years of frontend experience working on external user-facing UI’s - preferably in React\n\n* Strong understanding and expertise building with client-side Javascript.\n\n* Experience building responsive web designs using CSS, HTML. \n\n* Previous experience debugging complex systems in a team environment.\n\n* Strong knowledge of optimizing for performance on large-scale, high-volume systems.\n\n* Strong sense of product ownership in order to push features over the line.\n\n* Passion for creating beautiful UX design with the end user in mind.\n\n* A good teammate, someone who sees supporting their team as a core part of the job.\n\n\n\n\nBonus Points, But Not Required\n\n\n* Experience working with GraphQl or a comparable API technology.\n\n* Experience working with ML, analytics, data science or data visualization products.\n\n* Previous experience working in a startup or pre-IPO environment.\n\n\n\n\nThe estimated annual salary for this role is between $125,000 - $225,000, plus a competitive equity package. Actual compensation is determined based upon a variety of job related factors that may include: transferable work experience, skill sets, and qualifications. Total compensation also includes a comprehensive benefit package, including: medical, dental, vision, 401(k) plan, unlimited paid time off, generous parental leave plan, and others for mental and wellness support.\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, SaaS, React, GraphQL, JavaScript, API, Senior, 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\nBerkeley, California, United States

**About the job**\n\nYou'll be one of the first engineers and a member of the founding team, joining a team of 5 engineers.\n\nYou will closely work with the CTO and product lead to create and implement the front-end for our products. You will be involved in UI implementation, UX, product development, and growth of the engineering team.\n\nAs a founding team member, you will get a chance to set the foundations of our engineering culture. You will help articulate our engineering principles and help set the long-term roadmap. \n\n[Read more about life at loc.tax](https://jobs.loc.tax/)\n\n\n\n**What is Loc.tax?**\n\nLoc.tax is the first-ever B2B SaaS tax management platform for multinational companies that empowers collaboration between internal and external stakeholders, and helps achieve higher levels of compliance, efficiency and corporate social responsibility.\n\n**Who we are**\n\nOur team comes from tax, legal, engineering and product design worlds. We are a fully remote yet highly collaborative and small team from 🇧🇪🇳🇱🇱🇹🇧🇾. Building software products is our passion and we love doing that in an environment that is welcoming and motivating. Good vibes only ✌️.\n\nWe are looking to add more folks with different backgrounds across European time zones. (+- 2 CET)\n\nWe're funded by well known early stage investors and are ready to kick some... 🙌\n\n**Our Stack**\n\n- React\n- Typescript\n- Recoil\n- Styled components\n- Storybook\n- Git\n- Node\n- GraphQL\n\n**Desired Skills & Experience**\n\n- You feel comfortable in a very fast-paced and rapidly changing environment.\n- You understand limitations in modern-day UI frameworks to ensure UX designs can be implemented efficiently.\n- You have a genuine interest in great UI/UX.\n- You are not afraid of complex engineering problems.\n- You have 3+ years of industry experience in front-end development.\n- You are an expert in CSS.\n- You have a good understanding of modern javascript development methodology, process, and tooling.\n- You have a pragmatic approach to engineering that balances seamless experiences, beautiful code, maintainability, and time to market.\n- You have an appreciation for a test-driven, code-review culture.\n- You're curious about new technologies and you're driven to find ways to implement them in your work.\n\n\n**Responsibilities**\n\n- Code, maintain, and coordinate the evolution of the current application using React.\n- Build re-usable components and implement design system.\n- Collaborate with the product team on the definition, evolution and maintenance of our front-end code.\n- Help to define strategic initiatives to improve the code, the guidelines, processes, tools, infrastructure, and workflows.\n- Optimize the rendering performance.\n- Review code through Pull Requests.\n\n\n**Benefits**\n\n- Payroll or contractor, you choose.\n- Remote-first\n- MacBook Pro and other necessary accessories (payroll) (payroll)\n- Budget for personal education & conferences\n- Flexible work time & vacation policy\n- Maternity & paternity leave (payroll)\n- Competitive salary and stock options \n\nPlease mention the words **ASSAULT CORAL BEST** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMjU=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $70,000 — $130,000/year\n \n\n#Location\n+-2 CET EUROPE

**We’re only able to consider applicants based in the United States at this time. (You can work remotely anywhere in the United States, or from our office in San Francisco.)**\n\nWe are looking for an experienced lead front-end engineer who knows their way around React to help us develop an online platform (we’d need your help with the web side of things). We’re a small growing engineering team distributed around the US & Europe, with an office in San Francisco. We iterate quickly, ship every day, build for the long term, and are looking for smart, independent engineers who want to ply their trade with like-minded people.\n\n**Responsibilities**\n\n* Architect, build, deploy and iterate on new features and capabilities of the Archipelago application stack.\n* Collaborate with other engineers, design, and product to build out new capabilities and designs.\n* Build fast but design for the feature through architecting efficient and reusable components.\n* Own the quality of your deliverable through good design, implementation and unit testing.\n* Ship code to production frequently.\n\n**Experience and Qualifications**\n\n* 7+ years of frontend SaaS application development experience\n* Experience building responsive and cross-browser compatible web applications with a strong UI focus\n* Production environment coding experience with React, Typescript, and Graphql.\n* Proven track record of delivering highly-performant and scalable software solutions, and commitments to demanding business customers.\n* Knowledge of best practices & patterns for large scale web applications.\n* Work independently as part of a distributed team.\n\n**Desired but not Required**\n\nExperience building applications for the insurance industry.\n\n**Benefits**\n\nYou’ll join at an early stage of the company, so you can take something from 0 to 1\nWe’re a supportive team who will give you as much assistance or independence as you like\n\nWe have an office in San Francisco, but most of your engineering teammates work remotely from around the world. Pre-existing remote work experience would be a big plus. **If you’d like to work remotely, please note that we’re only able to consider applicants based in the US at this time.**\n\n**About Archipelago**\n\nArchipelago is a start-up working to revolutionize how risk is insured. Our founders are tech & finance entrepreneurs with several IPOs and acquisitions under their belts. We are headquartered in San Francisco, have raised several millions in seed money to date, and currently employ over a hundred people across the US & Europe.\n\n#### View other openings in Archipelago: [https://archipelago.breezy.hr/](https://archipelago.breezy.hr/) \n\n \n\nPlease mention the words **MIMIC COMPANY AROUND** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMjU=). 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 $130,000 — $200,000/year\n
\n\n#Benefits\n 🌎 Distributed team\n\n
\n\n#Location\nUnited States

Shuttlerock is seeking a creative and forward-thinking Senior Frontend Developer. You will be joining a global company of wonderful, talented and ambitious people. Our HQ is based in Nelson on the stunning South Island of New Zealand, but we are a flexible bunch and open to you working remotely **within +/- 5h of the New Zealand timezone** (roughly between Japan and the west coast of the United States). You will be joining a growing interdisciplinary squad in a positive and agile organisation that is experiencing rapid growth.\nWe are looking for creative individuals that thrive in a constantly changing, uncertain environment. If you are a self-starter that needs limited oversight, a keen drive to mentor and share with other developers, designers and functions - you would be our perfect fit.\nIdeal candidates will have experience working with SaaS solutions and the latest and greatest frontend technologies, but also understand how the browser works and have a tendency for elegance and simplicity. Ideally you also have a keen interest or eye for screen and motion design.\nYou will have the chance to work in the most beautiful and friendly part of the world while working with the big names in innovation and technology as Shuttlerock is officially partnered with Facebook, Instagram, Google, Youtube, TikTok, Pinterest and Hulu - just to name a few.\n\n**Minimum qualifications**\n- Bachelor’s degree or equivalent practical experience.\n- 7 years of software development experience, or 5 years with an advanced degree.\n- Experience in Javascript, Typescript and a third strictly typed or object-oriented language\n- Experience in large-scale or high quality web application development using state of the art technologies such as Apollo GraphQL.\n- Ability to communicate and write in English fluently and idiomatically.\n\n**Preferred qualifications**\n- Master’s degree or further education or experience in engineering, computer science or other technical related field.\n- A keen eye and an appreciation and interest for art & design\n- Deep experience developing high-performance, accessible and fully i18n'ed web applications and websites using preferably React and one other major Javascript technology framework.\n- Experience with Ruby or an interest and ability to learn other coding languages and technology as needed.\n- Practical experience with cloud-native / serverless technology using Javascript or Typescript.\n- Experience with Javascript as scripting language in other runtimes and environments, such as After Effects.\n\n**Responsibilities**\n- Write highly testable code in Typescript and Javascript.\n- Use state-of-the-art technology such as Apollo GraphQL daily.\n- Work with an agile cross-functional team to deliver high quality software and features of any size at pace and at scale.\n- Collaborate with Designers and other Software Developers of all experience levels on a daily basis.\n- Work with your peers and technology management on improving and shepherding the Shuttlerock technology-base.\n- Collaborate with the team to make sure the Developer Experience (DX) is second to none.\n- Mentor junior developers on their journey and be a buddy for new hires\n- Write technical documentation and do lightning talks on new technologies\n- Help to maintain a positive, collaborative and friendly, yet honest and productive working environment and attitude.\nKeep an open and healthy mind. \n\nPlease mention the words **DAUGHTER SURVEY FLOAT** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMjU=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $70,000 — $100,000/year\n \n\n#Location\nPacific, New Zealand, Australia, US Westcoast

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