🕑 Full Time 📌 Remote (US/CA time zones)
Salary: USD 140,000 - 180,000 per year
Equity: 1.0 - 1.5%
Benefits: 401k match, health insurance, hardware setup of choice, flexible work hours
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.
Application 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.
You 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.
We 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.
You will be responsible for driving feature development from concept to writing code to deployment, ensuring that the user experience is thought through, test coverage is adequate, and all the data supporting a feature is retrieved correctly and stored effectively in the Postgres database that powers pganalyze itself. Sometimes you might have to dig deep into Postgres internals to explain information correctly in a visual way.
Your work will take pganalyze to the next level, from its foundation as a monitoring service, to an intelligent advisor that tells application developers and DBAs the right insights at the right time.
At pganalyze, you will:
- Collaborate with other engineers on shipping new functionality end-to-end, and ensure features are well implemented and easy to use
- Write code in Ruby, Typescript/React.js, or Go to ship customer-facing features
- Think outside the box and focus on first principles when looking at a problem, for example to find better ways of visualizing complex data
- Try new approaches of combining different libraries and frameworks, such as combining React and d3.js (read more about how we solved this)
- Write public-facing documentation for features you develop, announce them on the pganalyze blog, and take customer feedback to improve and iterate on your work
- Take time to consider different data formats and data models to effectively implement APIs and associated backend systems
- Work on additional functionality that supports the core product use case, from Single-Sign On integrations to subscription billing code
- Work on our existing open-source projects and collaborate with upstream communities to contribute code back
Previously, you have:
- Worked professionally for at least 5 years as a software engineer
- Written complex, data heavy backend code with Ruby or Python
- Created features end to end with Typescript and React.js
- Rendered a chart in a browser using a high-level charting library or d3.js
- Used Postgres for multiple projects, are comfortable writing SQL, and are familiar with “EXPLAIN”
- Created indexes on a Postgres database based on a query being slow
- Written code that fetches data and/or interacts with cloud provider APIs
- Structured your work and set your schedule to optimize for your own productivity
Optionally, you may also have:
- Launched new products from scratch, taking something from nothing to the first users
- Created your own libraries for rendering charts, or analyzing time series
- Explored different ways of visualizing data sets for easy understanding
- Optimized a data-heavy application built on Postgres
- Experimented with ML frameworks to analyze complex data sets
- Written a VScode extension, or a GitHub marketplace plugin
- Used WebAssembly to run C, Rust or AssemblyScript in the browser
You could also be familiar with:
- The good old days when Internet Explorer didn’t render transparent PNGs
- CVE-2018-1058 and why most people did not fix their databases completely