Level is building a modern remote monitoring and management solution. We are a small, well-funded, team that recently launched our product. We are searching for a strong, multi-talented individual contributor who is comfortable with systems-level programming and networking who can contribute to our agent, written in Go.\n\n**Must-Haves**\n- Deep knowledge of a systems language like C, Rust, or Go.\n- Not afraid to dig into an RFC. Low-level internals excites you, rather than scares you away.\n- Experience with system-level APIs in Windows (win32), macOS, and/or Linux.\n- Excellent written communicator.\n- Willing to learn and work with Go.\n\n**Nice-to-Haves**\n- You are comfortable using GCC, and find yourself at home going through a C codebase.\n- Familiarity with RPC and common methods of IPC such as sockets and named pipes.\n- Video encoding experience. You have worked with VP8 and understand the spec.\n- Building cross-platform libraries, our Go agent compiles to Windows, Darwin, and Linux on a variety of architectures.\n\n**Things you might work on**\n- Building a cross-platform patch management system to give users control over OS updates.\n- Working with VP8 to reduce the latency and bandwidth when streaming a device.\n- Creating a system tray GUI for the agent.\n- Expanding desktop streaming to work on Mac and Linux.\n- Adding a proxy to the agent to enable remote access to routers and switches.\n- Implementing Trickle ICE to improve WebRTC connection times.\n\n**Why you might want to work with us**\n- We are a small, fully remote engineering team, and there are no layers of bureaucracy. You can have a huge impact here.\n- We are very flexible with working hours, we don't expect you to work a consistent block of time, we trust you to get your work done.\n- We've recently launched and are starting to grow.\n- We will offer profit sharing so our small team will receive dividends on profits the company makes.\n\n**Why you might not want to work with us**\n- We are an early-stage startup, and while we are well funded, we are careful with our runway and haven't splurged on extra perks like gym memberships or 401k matching.\n- You want to work with a large team. We do not intend to hire more until it is painful enough to warrant doing so.\n\n**More About Us**\nWe are a startup headquartered in beautiful downtown Asheville, NC. We are a small, close-knit team working to upend the RMM market with our new product. We have recently launched and have acquired our first customers. Though we are a startup, our investors have given us a multi-year runway.\n\nCurrently, our agent team is made up of a single amazing developer. This hire will join them to expand the agent team. This developer should be an experienced self-starter that can make an impact on our product development. We aren't interested in someone that just wants to work down a list of pre-defined tasks. Our ideal candidate loves working on products and will help shape the direction of ours. We're going to be improving this product for years and want someone to come on this journey with us.\n\nWe really like the Basecamp philosophy and try to make sure that it doesn’t have to be crazy at work. We won’t ask that you work weekends, or late into the night. We don’t mind if you need to leave for an appointment in the middle of the day. We understand that software development doesn’t happen for 8 hours straight and don’t worry about counting time in the chair. We trust that given a fair timeline with a scope that you help us determine you will be able to deliver features. We are concerned with the end goal, not micromanaging you on the way there.\n\n**About the Application Process**\nCollaboration and communication are a critical aspect of how we work, a cover letter is a great way to provide a sample of how you communicate.\n\nIn your cover letter, please describe why you’re interested in working at Level, and what draws you to this role in particular. Specifics of your past experience that are relevant to this role are great to include, too.\n\n**Pay**\nWe're looking for someone great but we're an early-stage startup. We are offering a rate of 120k plus profit sharing (once we have profits 😅). We hope to grow quickly and are committed to increasing the base pay of everyone on the team at each stage of growth. \n\nPlease mention the words **VIOLIN FETCH STUDENT** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xNDY=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $120,000 — $120,000/year\n
\n\n#Benefits\n 💰 Profit sharing\n\n
\n\n#Location\nWorldwide

At pganalyze, we redefine the user experience for optimizing the performance of Postgres databases. Our product helps customers such as Atlassian, Robinhood and DoorDash to understand complex Postgres problems and performance issues.\n\nApplication developers use pganalyze to get deep insights into complex database behaviors. Our product is heavy on automated analysis and custom visualizations, and makes automatic recommendations, such as suggesting the best index to create for a slow query.\n\nYou will enjoy working at pganalyze if you are a software craftsperson at heart, who cares about writing tools for developers. You will take new features from idea to production deployment end-to-end within days. Your work will regularly involve writing or contributing to open-source components as well as the Postgres project.\n\nWe are a fully remote company, with the core team based in the San Francisco Bay Area. Our company is bootstrapped and profitable. We emphasize autonomy and focus time by having few meetings per week.\n\n### About the role\n\nYour core responsibility: To develop and optimize our Postgres statistics and analysis pipeline, end-to-end, and work on the processes that generate automated insights from the complex data set. This work involves having a detailed understanding of the core data points that are collected from the source Postgres database as a timeseries, optimizing how they get retrieved, transported to the pganalyze servers, and then processed and analyzed.\n\nToday, this data pipeline is a combination of open-source Go code (in the [pganalyze collector](https://github.com/pganalyze/collector)), and statistics processing written in Ruby. You will be responsible for improving this pipeline, introducing new technologies, including a potential rewrite of the statistics processing in Rust.\n\nSome of the work will lead into the depths of Postgres code, and you might need to compile some C code, or understand how the pganalyze parser library, [pg_query](https://pganalyze.com/blog/pg-query-2-0-postgres-query-parser), works in detail.\n\nYour work is the foundation of the next generation of pganalyze, with a focus on the automatic insights we can derive from the workload of the monitored Postgres databases, and giving fine-tuned recommendations such as which indexes to create, or which config settings to tune.\n\n#### At pganalyze, you will:\n\n* Collaborate with other engineers on shipping new functionality end-to-end, and ensure features are performant and well implemented\n* Be the core engineer for the foundational components of pganalyze, such as the statistics pipeline that processes all data coming into the product\n* Develop new functionality that monitors additional Postgres statistics, or derives new insights from the existing time series information\n* Write Ruby, Go or Rust code on the pganalyze backend and the pganalyze collector\n* Evaluate and introduce new technologies, such as whether we should utilize Rust in more places of the product\n* Optimize the performance of pganalyze components, using language-specific profilers, or Linux tools like “perf”\n* Scale out our backend, which relies heavily on Postgres itself for statistics storage\n* Contribute to our existing open-source projects, such as pg_query, or create new open-source projects in the Postgres space\n* Work with upstream communities, such as the Postgres project, and contribute code back\n\n#### Previously, you have:\n\n* Worked professionally for at least 5 years as a software engineer\n* Written complex, data heavy backend code with Rust, Go, Ruby or Python\n* Used Postgres for multiple projects, are comfortable writing SQL, and are familiar with “EXPLAIN”\n* Created indexes on a Postgres database based on a query being slow\n* Looked at the source for a complex open-source project to chase a hard to understand bug\n* Written code that fetches data and/or interacts with cloud provider APIs\n* Structured your work and set your schedule to optimize for your own productivity\n\n#### Optionally, you may also have:\n\n* Written low-level C code, for fun\n* Used Protocol Buffers, FlatBuffers, msgpack or Cap’n Proto to build your own APIs\n* Analyzed patterns in time series data and run statistical analysis on the data\n* Experimented with ML frameworks to analyze complex data sets\n* Optimized a data-heavy application built on Postgres\n* Written your own Postgres extensions\n* Used APM and tracing tools to understand slow requests end-to-end\n\n#### You could also be familiar with:\n\n* Building your own Linux system from scratch\n* The many [regards](https://twitter.com/regardstomlane) of Tom Lane on the Postgres mailing list\n* Reproducible builds, and why it would be really nice to have them, like yesterday \n\nPlease mention the words **TREAT PHOTO TOAST** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xNDY=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $140,000 — $180,000/year\n \n\n#Location\nUnited States / Canada