\nProduct Engineer\nHigh level stuff you might be filtering against 🔍\nLocation: Remote (UK timezone +/- 6 hrs generally). In the UK we will hire you as an employee. In other countries you’ll need to be setup as a contractor initially.\nType: Full-time\nSalary: Location dependent. As a reference, our current range in the UK is £75k to £110k. If you will work from another location, you should map this to your equivalent market rate to be competitive. We are open to negotiation as we recognise there are different situations, but these are our general guardrails.\n\n\nWhat I am looking for\n👋 Hi, I’m Martin, VP of Engineering at Zen Educate and I’m looking for engineers who can make an impact on the real world problem of education staffing, and do it through engineering excellence.\n\n\nEvery place has its own understanding of what engineering excellence looks like (sometimes written down, sometimes not). Here’s what it means to me and Zen:\n• Valuing real world outcomes and shared learning over output\n• Product thinking over pure tech - start with the problem, ship quickly and iterate. \n• Team success and sustainability over individual heroics. \n\n\nWe are a small, but mighty team and so every engineer has the opportunity to make an outsized impact and put their stamp on what excellence looks like in practice. What do I mean by “small”? Today we have 4 product teams and 24 engineers including Tech Lead Managers and Principals.\n\n\nWe recognise the world is not static - “what got us here, won’t get us there” - so we look for curiosity, adaptability and proactiveness as fundamental traits. The engineers I see be the most successful are those who focus on solving problems, look to help others and just happen to typically leverage technology to do so.\n\n\nSo whether you’re passionate about building great products, scaling systems, or improving team processes, you’ll thrive at Zen if you care deeply about users, focus on real-world outcomes, pursue continuous learning and strive to make others better 💪\n\n\nWhat we are building and why\nGetting the right teacher into the right school at the right time is a crucial problem to solve, both for education outcomes for children and for the sustainability of an industry that spends billions on this.\n\n\nToday the platform we are building supports internal operations teams on filling roles, educators on finding roles via our mobile app and schools on getting educators in for both short-term and long-term roles. The more we develop the platform (and the ability to self-serve in the marketplace), the more efficient the whole process becomes, which means more money going back to educators and into classrooms (over £30 million since 2017). \n\n\nWe are well established in the UK and growing at a phenomenal rate in the US 🚀\n\n\nWhat we need now is to reach the next level in how we build our platform to support this growth. That’s where you come in 😉\n\n\nWhat the role looks like in practice\nI’ve written a bunch of words above that I hope capture your interest and excitement ✨. But what really matters is what reality looks like and the best people to share that are the existing engineers on the team. So here are a few glimpses from your potential peers of some of what they have done in a week:\n\n\n“I liaised with the Finance team to help re-run a set of invoices that originally failed from our automated invoice service, and I helped implement a feature to convert a long term booking into a job role - to more accurately reflect how teachers work and track job conversions. Then I shared some design feedback for a booking credit system that was initially less well defined.” - Jai\n\n\n“I implemented a compensation system that will cover the additional fees for teachers, which will allow schools to book needed teachers” - Kamil\n\n\n“I was updating the job details view in our React Native app to show more information to teachers about the school and job dates to make the job offers more attractive and useful. I also upgraded our backend Rails app to use latest version of Ruby, Sidekiq, Rack and Puma” - Adrian\n\n\n“I started the week by pushing some small updates to our React Native app, and then finished the week by shipping a feature to improve the experience of schools finding teachers and managing to clean up a bunch of legacy code in the process.” - Chris\n\n\n“I explored the feasibility of using Google Document AI to extract data from documents uploaded by candidates and validate them, improving automation for our onboarding process" - Lucas\n\n\n“I implemented backend and frontend MixPanel events for crucial workflows to better understand how users interact with our product and what we can improve on." - Georgi\n\n\n“I spent some time monitoring Sentry to spot performance trends and debug issues. I also built an automated rota in Coda for our Native release process, before reviewing Product Refinement Docs and contributing to shaping the solutions.” - Ethan\n\n\nWhat you might like or dislike \nEvery place makes tradeoffs based on what they value and where they are in their journey ⚖️. Here’s a list of things you might find useful in figuring out if this is the right role for you. If we end up chatting, feel free to dig deeper into any of them. Note that some of these are recent changes in our approach and may be “work in progress” when you join.\n\n\n💻 How We Work\n• Boring tech for the obvious, experimentation for the rest. Our core is Ruby on Rails, React, React Native, running on Heroku + Cloudflare etc.  But we have also evaluated Amazon Personalise as a candidate for our matching system and spiked out our own AI powered knowledge-base. \n• Process serves performance. We use agile sprints and other structure to support, but our focus is on outcomes not following rules. Greater performance gives greater freedom - think “Master your instrument, master the music, and then forget all that and just play.”\n• Engineers as problem shapers (not ticket takers). You’ll thrive here if you want to shape problems, not just deliver tickets. Our Product Managers and Designers are partners you pull on for leverage rather than task givers who hide the users away.\n• Daily shipping culture. We ship regularly and want to get even better at it. We are investing in this and welcome those who’ll help us start smaller and iterate faster.\n\n\n🌱 Growth & Progression\n• Choose your own career path. We care more about impact and learning than rigid competency grids. This means greater flexibility in what progression looks like, but requires you to build an understanding of what we value from guiding principles and shared real-world examples.\n• Few Titles, infinite Levels. We use Levels instead of Titles to show growth in a Role. You won’t see titles like Associate, Senior, or Staff here. Instead, you can grow continuously by getting better at your current role - e.g. working faster, safer, and more independently. Changing roles is possible too, but depends on business needs, since different roles aim for different business outcomes and typically use different skills.\n• Investment over reward as a mindset. Level changes are tightly coupled to compensation changes. Confidence in a Level change is based on sustainably doing great work at your current level. We think it is fairer to invest in what you do next, rather than reward you doing the next Level first for free!\n\n\n💸 Compensation\n• Market reality. Compensation is based on your competitiveness in your local hiring market (note that’s not just where you live). We don’t believe anyone has found a great solution to global compensation, so we aim instead to be clear and equitable in how we do it.\n• Solid, but not flashy compensation. We pay decently, but we won’t beat out companies with deeper pockets (yet!).\n• Think long term investment. If you are in a place where you need to prioritise immediate financial gain then this probably isn’t the right time to join us.\n\n\n🤝 Team Culture & Collaboration\n• Distributed engineering team. Solid communication skills and async habits are key to be effective. You’ll find strong connection here, but not through engineering getting together in-person. If you like the buzz of working near others you are welcome to work from one of our offices, but there won’t be many engineers there on any given day.\n• We believe in impact and measurable outcomes, alongside shared learning. If your work moves the needle or teaches us something meaningful then that’s a win. If not, then we’ll want to understand why. \n• Balanced, sustainable work. Long hours are not a badge of honour - they are an indication something isn’t working well. We value a sustainable pace and healthy teams.\n• Diversity is good in some ways and lacking in others. You might be the first of something here. That matters and we’ll support appropriately if you are.\n\n\nHow we hire\nHire fast, fix fast.  Hiring today is...not great, with most companies being too cautious and taking too long to make a decision 😦. We move quicker - our ideal is: apply Monday, offer by Friday. Then we invest heavily in the most important part - your onboarding. We ensure you are setup for success, with clear direction, experience of different teams and shipping to production within days.\n\n\nWhilst fast doesn’t mean frivolous, it does slightly increase the risk that you or we made a mistake. So we include regular check-ins during onboarding to make sure expectations match reality. If either side feels something is off then we try to fix it fast. And sometimes that will mean saying “let’s not carry on” with respect.\n\n\nReal talk. We believe in being direct and authentic. We’ll share the good, the messy and the challenges. We recognise we won’t have all the answers, still have much to learn, and that’s all part of the fun of this wild ride 🚀. We expect the same from you - after all we are just a bunch of humans trying to do great work together.\n\n\nMindset, not tools. We hire for how you think and create leverage, not what specific tools you’ve used before. To us, experience is just another tool - it is only valuable through how you leverage it. Curiosity, adaptability, product thinking - those are the durable qualities in a changing world. And we value different opinions, so ensure you share yours - have a point of view, maybe debate a little and we will respect that.\n\n\nAlways open to great people. We are always hiring and happy to chat even if the timing isn’t quite right. That’s why you might see this job post open for a long time. We are not collecting resumes or doing stealth market research, we just believe in the power of serendipity. To make that more transparent - right now we have a clear need for at least 2 more engineers in the team.\n\n\nOkay, so what will the actual process look like? 👀\n• Recruiter quick chat. Our recruiter will check you are human, can communicate effectively and cover some of the basics like compensation, benefits and availability.\n• Technical expertise. We will do a paired session with a twist - we will be the ones sharing our screen and writing the code. So come prepared to ask questions, drive progress with another engineer and dig through an ambiguous past problem in our codebase.\n• Product thinking. Chat to either our CPTO or a Product Manager about how you’ve demonstrated a product mindset in the past. Or if you haven’t had opportunity to do that, tell us why and what you’d do differently with us.  \n• Role chat. This will be with me and I’ll be wanting to understand how you think and approach the role and engineering excellence. I’ll start by asking you the question you include in your application. And I’ll want to dig into your answers so that this becomes more of a conversation and shared exploration than a Q&A session 😃. \n\n\nAfter the recruiter chat, the remaining sessions can happen in any order and as quickly as our schedules can align. You could do them all in a day if you want or spread them out a bit.\n\n\nOnce interviewers have shared their feedback from each session we do an internal debrief - that’s where we discuss what we are excited about you for in the role, any challenges we see and whether we think we can mitigate them at this time. From there we will make a decision and either proceed to offer or tell you that we not offering. \n\n\nWe believe feedback is important, but also know not everyone wants it - so we don’t share it by default. If you’d like feedback after the process, just let us know. Note that we’ll frame the feedback from our perspective of why we did or did not have the confidence rather than as a commentary on you.\n\n\nInterested? Let’s go!\nIf you read all of the above and are excited (maybe even a little nervous) about the opportunity and how we work then I recommend applying now! If you skipped or skimmed the above, feel free to apply anyway but you’re missing a bunch of useful information that could streamline the process for you 😉\n\n\n\n\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, Amazon, React, Ruby, Mobile, Heroku, Engineer and Backend jobs that are similar:\n\n $70,000 — $122,500/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\nLondon

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 (#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 $140,000 — $180,000/year\n \n\n#Location\nUnited States / Canada

\nRuntime Sr., Lead, or Principal Level Platform Engineer, Heroku\nHeroku operates the world’s largest PaaS cloud, continuously delivering millions of apps with 6+ million container deployments, 16+ billion routing requests, and 10+ terabytes of application logs per day. Our vision is for developers to focus on their applications and leave operations to us.\nWe work in small groups who are heartfelt about our users’ problems. We plan weekly, chat daily and work closely together. Our team is a remote community with members excited to work together on challenging distributed systems problems. Equality is a core value for Salesforce; it's at the heart of everything we do and strive to be. That means Equal Opportunity, Equal Advancement and Equal Pay for all. We do not discriminate on the basis of race, religion, color, national origin, gender identity or expression, sexual orientation, age, marital status, veteran status, or disability status.\nWe hope you are passionate about joining our community of engineers who love to learn, work, and operate a gigantic distributed system, build and sustain a remote culture and help grow and mentor other engineers.\nExamples of recent work Runtime engineers have done at Heroku\nCore infrastructure scaling and growth: broke up a critical, monolithic Ruby application that performs many container scheduling tasks and refactored it as a set of well scoped gRPC Go services.\nSupporting critical customer applications: diagnosed and fixed a very elusive bug in how signals are forwarded between our platform logging process and customer containers that was causing customer apps to crash unexpectedly.\nDelivering features to customers: built an automated cert management capability using the Let's Encrypt API to provision free customer SSL certs for domains added to apps and automatically renew expiring certs.\nResearching and learning: prototyped a Kubernetes orchestration backend for our internal Runtime API as part of a larger effort to learn about and adopt new technologies in our runtime.\nInfrastructure improvements: transitioned our use of K8s from self-managed to managed by integrating EKS and implemented a new authentication scheme to integrate our container registry with EKS.\nIncident response: conducted emergency response when a remote operation timed out during routine API maintenance in our EU runtime, corrupting routing state data for a single node. Incident responders followed documented procedure in our ops playbooks to identify the corrupted node and flush its cache. Remediation work included refining our metrics to reduce our time to diagnose and improving our automated tooling used for system maintenance.\n\nProfiles relevant specifically to the Senior Engineer role would feature:\n3+ years in a full-time, professional software engineering role\nExperience developing production software in Go or Ruby\nExperience developing on IaaS (AWS, GCP, Azure, OpenStack, etc)\nDemonstration of strong software development best practices, such as documentation driven design, code review, test coverage, continuous integration, continuous delivery, phased rollouts\nEnthusiasm for learning new languages, frameworks, and skills\nExcellent written and verbal communication skills, including the ability to work effectively with geographically distributed teams and people of various backgrounds\nExperience participating in an on-call rotation\n\nProfiles relevant specifically to Lead and Principal roles would additionally feature:\n5+ years in a full-time, professional software engineering role\nExperience in a technical leadership role in a collaborative team environment\nExperience deploying, operating and supporting critical production systems\nExperience deploying services on Kubernetes\nExperience participating in an on-call rotation\n\n\nSalesforce, the Customer Success Platform and world's #1 CRM, empowers companies to connect with their customers in a whole new way. The company was founded on three disruptive ideas: a new technology model in cloud computing, a pay-as-you-go business model, and a new integrated corporate philanthropy model. These founding principles have taken our company to great heights, including being named one of Forbes’s “World’s Most Innovative Company” six years in a row and one of Fortune’s “100 Best Companies to Work For” nine years in a row. We are the fastest growing of the top 10 enterprise software companies, and this level of growth equals incredible opportunities to grow a career at Salesforce. Together, with our whole Ohana (Hawaiian for "family") made up of our employees, customers, partners and communities, we are working to improve the state of the world. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Heroku, Engineer, Executive, Cloud, Scheme, Salesforce, Node, Ruby, API, Senior 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