Position Summary\n\nThe Sr. Staff Software Engineer influences the long-term evolution of web technology for the country’s first tech-driven healthcare staffing platform. \nResponsibilities\n\n\nDevelop features and improvements to the Nomad Health platform in a secure, well-tested, and performant way.\n\nWork with Product Management and other stakeholders (Backend, UX, etc.) to iterate on new features within the product and exert significant influence on the overall vision and long-range goals of the team.\n\nCraft code that meets our internal standards for style, maintainability, and best practices for a high-scale web environment. Maintain and advocate for these standards through code review.\n\nConsistently ship small and large features and improvements with minimal guidance and support from other team members. Collaborate with cross-functional teams on larger projects.\n\nHelp improve the overall experience of our product through improving the quality of the Frontend features both in your group and features that benefit other groups.\n\nHelp identify areas of improvements in the code base, both specific to your group and outside your group (e.g. component library) and help contribute to make it better\n\nLearn from, collaborate with, and mentor other Frontend Engineers to help them grow in their technical responsibilities and remove blockers. Everyone can contribute something new to the team regardless of how long they’ve been in the industry.\n\nDrive innovation on the team with a willingness to experiment and to boldly confront problems of immense complexity and scope.\n\nProactively seeks out difficult impediments to our efficiency as a team ("technical debt"), propose and implement solutions that will enable the entire team to iterate faster\n\nRepresent Nomad Health and its values in public communication around broad initiatives, specific projects, and community contributions. Interact with customers and other external stakeholders as a consultant and spokesperson for the work of your team.\n\nParticipate in the Incident Management on-call rotation to help ensure the availability goals for Nomad Health platform are met, by working with reliability engineers and development team members.\n\nSupport the team and the business by providing context and technical specifications, leading the implementation of complex and sometimes high-risk projects, while maintaining efficient communications with all stakeholders including product partners and engineering leadership.\n\n\n\nRequirements\n\n\n15+ years of experience as a software engineer, 8+ years of experience in a lead role\n\nProfessional experience with modern JavaScript web frameworks, preferably React\n\nExperience with writing automated tests (e.g. Jest, Karma, Jasmine, Mocha, AVA, tape)\n\nA solid understanding in core web and browser concepts (e.g. how the browser parses and constructs a web page)\n\nA solid understanding of semantic HTML, CSS, and core JavaScript concepts.\n\nDemonstrated capacity to clearly and concisely communicate complex technical, architectural, and/or organizational problems and propose thorough iterative solutions to achieve consensus with peers and cross-functional teams\n\nExperience tackling performance and optimization problems with a demonstrated ability to both diagnose and prevent them\n\nSelf-motivated and self-managing, with great organizational skills and proven ability to thrive in a fully remote organization working in a highly agile, intensely iterative software development process.\n\nShare our values, and work in accordance with those values\n\n\n\nNice to Have\n\n\nWorking knowledge of Python and Flask\n\nAbility to integrate with and develop GraphQL APIs\n\nExperience implementing Authentication and Authorization solutions\n\n\n\n\n \n\nWe are committed to providing care and that starts with equipping Nomad employees with benefits focused on enhancing physical, financial, emotional, and social well-being. Our packages may include comprehensive health plans, 401k matching, equity, flexible PTO, sick leave, paid parental leave, a remote-first work environment with an annual stipend to kit out your home office, and more! Compensation for this role for a candidate based in Colorado is expected to be between $216,000 and $272,500, and for a candidate based in NYC to be between $216,000 and $272,500. Actual pay may be higher or lower depending on geographic locations, skills, experience, and other factors permitted by law. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Finance, Flutter, Full Stack, Digital Nomad, GraphQL, Python, JavaScript, Senior, Medical and Engineer jobs that are similar:\n\n $67,500 — $125,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\nNew York City, New York, United States

\nRubiconMD is an innovative healthcare company bringing better care at lower costs to providers and their patients across the country. RubiconMD’s mission is to ensure that all patients have access to the care they need, no matter who they are or where they live. It’s no small order, but we achieve it with the right team. That’s why we hire empathetic, passionate, and strong leaders who are looking to make an impact in the world through our core values: Human, Agile, Innovative & Collaborative.\n\nIf you’re passionate about having a positive impact by revolutionizing the healthcare system and democratizing access to care, we’d love to learn more about you!  Our engineering team is located across the US, primarily based in New York City, and throughout Spain.  \n\nKey responsibilities include:\n\n\nChampion end-to-end feature development with participation in system design & architecture, engineering implementation, software release, and technical support\n\nShare and be open to learn from your peers via pair programming, technical writing, code reviews, architecture discussions, and active engagement with stakeholders\n\nMake explicit tradeoffs between technical implementation directions, and strive to clearly communicate to your peers what data drove you to make these choices\n\nIdentify and advocate for opportunities to improve the performance, reliability, and scalability of technical stack and processes\n\nBuild accessible, secure, and performant software solutions in a highly regulated healthcare environment. These may include on platform features, internal support tooling, mobile applications, and third party integrations\n\n\n\n\nAbout our stack:\n\nEverything's up for debate but we want to leave you with a good idea of what tools we are using today. While keeping our current tool box up to date, we are open minded about trying new technologies and ideas that may better fit our needs.\n\nAt the highest level, our Ruby on Rails backend is hosted in AWS with our Angular frontend being served through a CDN. We process tasks asynchronously and leverage a frontend cache to help reduce network calls against our GraphQL APIs. Our Data Science team works off of a data lake, pulling dataframes into python for reporting and analytics.\n\nThis is the general idea and we’re happy to jump into all the details with you!\n\nDesired skills and experience:\n\n\nWe are using Angular 13 which means we hope you’ve had strong experience in TypeScript with modern web frameworks that utilize the virtual dom, change detection, and have explored Observables / Streams.\n\nWhen things get tough, we count on you to jump into the Chrome Debugger and utilize your underlying experience in JavaScript, HTML, and best practices using CSS.\n\nWe favor reusability, and share libraries across projects. You should have opinions on defining and maintaining shared resources and both internal and external libraries.\n\nIn delivering robust software, we expect you to bring some opinions about clean code, testability, and design patterns.\n\nWe use GraphQL as a query language for our API between frontend and backend. You should have experience utilizing APIs and designing contracts between engineering teams.\n\n\n\n\nHow we work:\n\nWe use scrum to organize into delivery teams which are autonomous, and responsible for holistically delivery features and pilots to our users. Our teams include fullstack, frontend, and backend engineers. We round out the team with a dedicated Scrum Master and Product Owner. These teams operate on a two-week sprint.\n\nAdditionally we have DevOps and Data Science teams providing support and insight across team functions.\n\nOur Hiring Philosophy:\n\nRubiconMD’s founding mission is to democratize medical expertise, so that all patient populations have access to the care they need. In order to deliver on this, we focus on empowering primary care providers, who we believe are the key to a thriving, equitable health care system. It’s no small order, but we can achieve it with the right team. That’s why we hire people with drive and leadership, who are also highly accountable—to each other, to the providers we serve, and to the impact we exist to make.\n\nRubiconMD is an equal opportunity employer and prohibits discrimination against persons of any kind on the basis of race, color, religion, gender, sexual orientation, nation of origin, age, disability, and genetics.\n\n**COVID-19 vaccination is a condition of employment for US employees unless there is a legally protected reason for an accommodation. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Software, DevOps, Python, Typescript, Angular, Ruby, API, Mobile, Medical, Engineer and Backend jobs that are similar:\n\n $70,000 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n

# We're building the Data Platform of the Future\nJoin us if you want to rethink the way organizations interact with data. We are a **developer-first company**, committed to building around open protocols and delivering the best experience possible for data consumers and publishers.\n\nSplitgraph is a **seed-stage, venture-funded startup hiring its initial team**. The two co-founders are looking to grow the team to five or six people. This is an opportunity to make a big impact on an agile team while working closely with the\nfounders.\n\nSplitgraph is a **remote-first organization**. The founders are based in the UK, and the company is incorporated in both USA and UK. Candidates are welcome to apply from any geography. We want to work with the most talented, thoughtful and productive engineers in the world.\n# Open Positions\n**Data Engineers welcome!** The job titles have "Software Engineer" in them, but at Splitgraph there's a lot of overlap \nbetween data and software engineering. We welcome candidates from all engineering backgrounds.\n\n[Senior Software Engineer - Backend (mainly Python)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Backend-2a2f9e278ba347069bf2566950857250)\n\n[Senior Software Engineer - Frontend (mainly TypeScript)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Frontend-6342cd76b0df483a9fd2ab6818070456)\n\n→ [**Apply to Job**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp) ← (same form for both positions)\n\n# What is Splitgraph?\n## **Open Source Toolkit**\n\n[Our open-source product, sgr,](https://www.github.com/splitgraph/splitgraph) is a tool for building, versioning and querying reproducible datasets. It's inspired by Docker and Git, so it feels familiar. And it's powered by PostgreSQL, so it works seamlessly with existing tools in the Postgres ecosystem. Use Splitgraph to package your data into self-contained\ndata images that you can share with other Splitgraph instances.\n\n## **Splitgraph Cloud**\n\nSplitgraph Cloud is a platform for data cataloging, integration and governance. The user can upload data, connect live databases, or "push" versioned snapshots to it. We give them a unified SQL interface to query that data, a catalog to discover and share it, and tools to build/push/pull it.\n\n# Learn More About Us\n\n- Listen to our interview on the [Software Engineering Daily podcast](https://softwareengineeringdaily.com/2020/11/06/splitgraph-data-catalog-and-proxy-with-miles-richardson/)\n\n- Watch our co-founder Artjoms present [Splitgraph at the Bay Area ClickHouse meetup](https://www.youtube.com/watch?v=44CDs7hJTho)\n\n- Read our HN/Reddit posts ([one](https://news.ycombinator.com/item?id=24233948) [two](https://news.ycombinator.com/item?id=23769420) [three](https://news.ycombinator.com/item?id=23627066) [four](https://old.reddit.com/r/datasets/comments/icty0r/we_made_40k_open_government_datasets_queryable/))\n\n- [Read our blog](https://www.splitgraph.com/blog)\n\n- Read the slides from our early (2018) presentations: ["Docker for Data"](https://www.slideshare.net/splitgraph/splitgraph-docker-for-data-119112722), [AHL Meetup](https://www.slideshare.net/splitgraph/splitgraph-ahl-talk)\n\n- [Follow us on Twitter](https://ww.twitter.com/splitgraph)\n\n- [Find us on GitHub](https://www.github.com/splitgraph)\n\n- [Chat with us in our community Discord](https://discord.gg/eFEFRKm)\n\n- Explore the [public data catalog](https://www.splitgraph.com/explore) where we index 40k+ datasets\n\n# How We Work: What's our stack look like?\n\nWe prioritize developer experience and productivity. We resent repetition and inefficiency, and we never hesitate to automate the things that cause us friction. Here's a sampling of the languages and tools we work with:\n\n- **[Python](https://www.python.org/) for the backend.** Our [core open source](https://www.github.com/splitgraph/splitgraph) tech is written in Python (with [a bit of C](https://github.com/splitgraph/Multicorn) to make it more interesting), as well as most of our backend code. The Python code powers everything from authentication routines to database migrations. We use the latest version and tools like [pytest](https://docs.pytest.org/en/stable/), [mypy](https://github.com/python/mypy) and [Poetry](https://python-poetry.org/) to help us write quality software.\n\n- **[TypeScript](https://www.typescriptlang.org/) for the web stack.** We use TypeScript throughout our web stack. On the frontend we use [React](https://reactjs.org/) with [next.js](https://nextjs.org/). For data fetching we use [apollo-client](https://www.apollographql.com/docs/react/) with fully-typed GraphQL queries auto-generated by [graphql-codegen](https://graphql-code-generator.com/) based on the schema that [Postgraphile](https://www.graphile.org/postgraphile) creates by introspecting the database.\n\n- [**PostgreSQL](https://www.postgresql.org/) for the database, because of course.** Splitgraph is a company built around Postgres, so of course we are going to use it for our own database. In fact, we actually have three databases. We have `auth-db` for storing sensitive data, `registry-db` which acts as a [Splitgraph peer](https://www.splitgraph.com/docs/publishing-data/push-data) so users can push Splitgraph images to it using [sgr](https://www.github.com/splitgraph/splitgraph), and `cloud-db` where we store the schemata that Postgraphile uses to autogenerate the GraphQL server.\n\n- [**PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) and [PL/Python](https://www.postgresql.org/docs/current/plpython.html) for stored procedures.** We define a lot of core business logic directly in the database as stored procedures, which are ultimately [exposed by Postgraphile as GraphQL endpoints](https://www.graphile.org/postgraphile/functions/). We find this to be a surprisingly productive way of developing, as it eliminates the need for manually maintaining an API layer between data and code. It presents challenges for testing and maintainability, but we've built tools to help with database migrations and rollbacks, and an end-to-end testing framework that exercises the database routines.\n\n- [**PostgREST](https://postgrest.org/en/v7.0.0/) for auto-generating a REST API for every repository.** We use this excellent library (written in [Haskell](https://www.haskell.org/)) to expose an [OpenAPI](https://github.com/OAI/OpenAPI-Specification)-compatible REST API for every repository on Splitgraph ([example](http://splitgraph.com/mildbyte/complex_dataset/latest/-/api-schema)).\n\n- **Lua ([luajit](https://luajit.org/luajit.html) 5.x), C, and [embedded Python](https://docs.python.org/3/extending/embedding.html) for scripting [PgBouncer](https://www.pgbouncer.org/).** Our main product, the "data delivery network", is a single SQL endpoint where users can query any data on Splitgraph. Really it's a layer of PgBouncer instances orchestrating temporary Postgres databases and proxying queries to them, where we load and cache the data necessary to respond to a query. We've added scripting capabilities to enable things like query rewriting, column masking, authentication, ACL, orchestration, firewalling, etc.\n\n- **[Docker](https://www.docker.com/) for packaging services.** Our CI pipeline builds every commit into about a dozen different Docker images, one for each of our services. A production instance of Splitgraph can be running over 60 different containers (including replicas).\n\n- **[Makefile](https://www.gnu.org/software/make/manual/make.html) and** [docker-compose](https://docs.docker.com/compose/) **for development.** We use [a highly optimized Makefile](https://www.splitgraph.com/blog/makefile) and `docker-compose` so that developers can easily spin-up a stack that mimics production in every way, while keeping it easy to hot reload, run tests, or add new services or configuration.\n\n- **[Nomad](https://www.nomadproject.io/) for deployment and [Terraform](https://www.terraform.io/) for provisioning.** We use Nomad to manage deployments and background tasks. Along with Terraform, we're able to spin up a Splitgraph cluster on AWS, GCP, Scaleway or Azure in just a few minutes.\n\n- **[Airflow](https://airflow.apache.org/) for job orchestration.** We use it to run and monitor jobs that maintain our catalog of [40,000 public datasets](https://www.splitgraph.com/blog/40k-sql-datasets), or ingest other public data into Splitgraph.\n\n- **[Grafana](https://grafana.com/), [Prometheus](https://prometheus.io/), [ElasticSearch](https://www.elastic.co/), and [Kibana](https://www.elastic.co/kibana) for monitoring and metrics.** We believe it's important to self-host fundamental infrastructure like our monitoring stack. We use this to keep tabs on important metrics and the health of all Splitgraph deployments.\n\n- **[Mattermost](https://mattermost.com/) for company chat.** We think it's absolutely bonkers to pay a company like Slack to hold your company communication hostage. That's why we self-host an instance of Mattermost for our internal chat. And of course, we can deploy it and update it with Terraform.\n\n- **[Matomo](https://matomo.org/) for web analytics.** We take privacy seriously, and we try to avoid including any third party scripts on our web pages (currently we include zero). We self-host our analytics because we don't want to share our user data with third parties.\n\n- **[Metabase](https://www.metabase.com/) and [Splitgraph](https://www.splitgraph.com) for BI and [dogfooding](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)**. We use Metabase as a frontend to a Splitgraph instance that connects to Postgres (our internal databases), MySQL (Matomo's database), and ElasticSearch (where we store logs and DDN analytics). We use this as a chance to dogfood our software and produce fancy charts.\n\n- **The occasional best-of-breed SaaS services** **for organization.** As a privacy-conscious, independent-minded company, we try to avoid SaaS services as much as we can. But we still find ourselves unable to resist some of the better products out there. For organization we use tools like [Zoom](https://www.zoom.us) for video calls, [Miro](https://miro.com/) for brainstorming, [Notion](https://www.notion.so) for documentation (you're on it!), [Airtable for workflow management](https://airtable.com/), [PivotalTracker](https://www.pivotaltracker.com/) for ticketing, and [GitLab for dev-ops and CI](https://about.gitlab.com/).\n\n- **Other fun technologies** including [HAProxy](http://www.haproxy.org/), [OpenResty](https://openresty.org/en/), [Varnish](https://varnish-cache.org/), and bash. We don't touch them much because they do their job well and rarely break.\n\n# Life at Splitgraph\n**We are a young company building the initial team.** As an early contributor, you'll have a chance to shape our initial mission, growth and company values.\n\n**We think that remote work is the future**, and that's why we're building a remote-first organization. We chat on [Mattermost](https://mattermost.com/) and have video calls on Zoom. We brainstorm with [Miro](https://miro.com/) and organize with [Notion](https://www.notion.so).\n\n**We try not to take ourselves too seriously**, but we are goal-oriented with an ambitious mission.\n\n**We believe that as a small company, we can out-compete incumbents** by thinking from first principles about how organizations interact with data. We are very competitive.\n\n# Benefits\n- Fully remote\n\n- Flexible working hours\n\n- Generous compensation and equity package\n\n- Opportunity to make high-impact contributions to an agile team\n\n# How to Apply? Questions?\n[**Complete the job application**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp)\n\nIf you have any questions or concerns, feel free to email us at [[email protected]](mailto:[email protected]) \n\nPlease mention the words **DESERT SPELL GOWN** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4yNTA=). 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