\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

**OVERVIEW**\n\nWe're looking for Security Engineers to join our Engineering team. In this role, you will build innovative payments products that delight both engineering and finance teams. As an early member of the engineering team, you will help shape the engineering culture of a fast-growing startup.\n\nThe core platform at Modern Treasury sits between our customers and their banks. In the same way that Twilio abstracted away the complexity of working with communication networks, we have built an easy-to-use, common interface into the banking system. Our customers use our products to do things like move money to or from their users, automate back-office work, and record their transaction ledgers. The companies that can use Modern Treasury move over $750 trillion a year via bank payments, as compared to only $2 trillion per year on card payments.\n\nOur API is often the most critical piece of infrastructure that our customers use. We place a premium on building robust, scalable systems that can sustain a high volume of API calls and exceed the reliability requirements to move money at scale. We complement this with well-thought out interfaces for our users and pride in writing quality API docs.\n\nWe believe in using the best tool for the job, rather than always using open source or building things ourselves. We actively embrace open source in parts of our system but aren't afraid to roll our own solution for things like writing and parsing bank files. We also contribute to open source (for example, https://www.moderntreasury.com/journal/continuous-accounting-building-on-an-open-source-library).\n\nIn addition to our API, we have had a web platform since day 1 that is used by accountants, controllers, and engineers. They use our platform to do things like manage payment workflows and monitor their business. As an engineer, you will work with our product team to build products and features for these users.\n\n**ABOUT MODERN TREASURY**\n\nModern Treasury is payment operations software for businesses with a high volume of transactions or complex payment flows. Modern Treasury automates the full cycle of money movement — from payment initiation, through approvals, to reconciliation.\n\nOur mission is to transform the way businesses move and track money, driving toward a world where payments are real-time, reconciliation is instant, and accounting is continuous.\n\n**WEEK BY WEEK**\n\nDuring your first week you will:\n* Get to know our leadership, culture, and values\n* Onboard with the engineering team\n* Ship your first commit on day 1\n* Take on 1-2 small tickets to address bugs or make minor improvements\n* Read our favorite industry primers\n\nDuring your first six weeks you will:\n* Ship your first major project\n* Write your first blog post. We love writing at Modern Treasury (and have been on the front page of Hacker News multiple times with posts like "What Happens When You ACH a Dead Person?" and "How to Build an Insurance Company")\n* Shadow a few customer and partner meetings every week\n\nDuring your first six months you will:\n* Work with our product team to scope and ship products for both our engineering and finance users\n* Help grow our team by mentoring new engineers, writing internal tooling and documentation, and interviewing new hires\n\n**WHAT YOU SHOULD HAVE**\n* Experience building web applications professionally for 2+ years\n* Experience working with SQL/Relational databases\n\n**TECHNOLOGIES WE USE**\n* Ruby on Rails for our backend framework\n* React, GraphQL, and Tailwind CSS on the front end\n* Postgres for our database\n* Redis for caching\n* AWS for infrastructure and hosting\n* Docker for containerization\n* GitHub for source code management\n* Buildkite for continuous integration\n\n**EOE**\n\nModern Treasury is committed to equal employment opportunity and does not discriminate in any employment opportunities or practices based on an individual's race, color, creed, gender (including gender identity and gender expression), religion (all aspects of religious beliefs, observance or practice, including religious dress or grooming practices), marital status, registered domestic partner status, age, national origin or ancestry (including language use restrictions and possession of a driver’s license issued under California Vehicle Code section 12801.9), natural hair, physical or mental disability, political affiliation, medical condition (including cancer or a record or history of cancer, and genetic characteristics), sex (including pregnancy, childbirth, breastfeeding or related medical condition), genetic information, sexual orientation, military and veteran status or any other consideration made unlawful by federal, state, or local laws. It also prohibits unlawful discrimination based on the perception that anyone has any of those characteristics, or is associated with a person who has or is perceived as having any of those characteristics. \n\nPlease mention the words **DETECT COMMON PLATE** 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 $120,000 — $180,000/year\n \n\n#Location\nUnited States

**OVERVIEW**\n\nWe're looking for Full-Stack Software Engineers to join our Engineering team. In this role, you will build innovative payments products that delight both engineering and finance teams. As an early member of the engineering team, you will help shape the engineering culture of a fast-growing startup.\n\nThe core platform at Modern Treasury sits between our customers and their banks. In the same way that Twilio abstracted away the complexity of working with communication networks, we have built an easy-to-use, common interface into the banking system. Our customers use our products to do things like move money to or from their users, automate back-office work, and record their transaction ledgers. The companies that can use Modern Treasury move over $750 trillion a year via bank payments, as compared to only $2 trillion per year on card payments.\n\nOur API is often the most critical piece of infrastructure that our customers use. We place a premium on building robust, scalable systems that can sustain a high volume of API calls and exceed the reliability requirements to move money at scale. We complement this with well-thought out interfaces for our users and pride in writing quality API docs.\n\nWe believe in using the best tool for the job, rather than always using open source or building things ourselves. We actively embrace open source in parts of our system but aren't afraid to roll our own solution for things like writing and parsing bank files. We also contribute to open source (for example, https://www.moderntreasury.com/journal/continuous-accounting-building-on-an-open-source-library).\n\nIn addition to our API, we have had a web platform since day 1 that is used by accountants, controllers, and engineers. They use our platform to do things like manage payment workflows and monitor their business. As an engineer, you will work with our product team to build products and features for these users.\n\n**ABOUT MODERN TREASURY**\n\nModern Treasury is payment operations software for businesses with a high volume of transactions or complex payment flows. Modern Treasury automates the full cycle of money movement — from payment initiation, through approvals, to reconciliation.\n\nOur mission is to transform the way businesses move and track money, driving toward a world where payments are real-time, reconciliation is instant, and accounting is continuous.\n\n**WEEK BY WEEK**\n\nDuring your first week you will:\n* Get to know our leadership, culture, and values\n* Onboard with the engineering team\n* Ship your first commit on day 1\n* Take on 1-2 small tickets to address bugs or make minor improvements\n* Read our favorite industry primers\n\nDuring your first six weeks you will:\n* Ship your first major project\n* Write your first blog post. We love writing at Modern Treasury (and have been on the front page of Hacker News multiple times with posts like "What Happens When You ACH a Dead Person?" and "How to Build an Insurance Company")\n* Shadow a few customer and partner meetings every week\n\nDuring your first six months you will:\n* Work with our product team to scope and ship products for both our engineering and finance users\n* Help grow our team by mentoring new engineers, writing internal tooling and documentation, and interviewing new hires\n\n**WHAT YOU SHOULD HAVE**\n\n* Experience building web applications professionally for 2+ years\n* Experience working with SQL/Relational databases\n\n**TECHNOLOGIES WE USE**\n* Ruby on Rails for our backend framework\n* React, GraphQL, and Tailwind CSS on the front end\n* Postgres for our database, Redis for caching\n* AWS for infrastructure and hosting\n* Docker for containerization, \n* GitHub for source code management\n* Buildkite for continuous integration\n\n**EOE**\nModern Treasury is committed to equal employment opportunity and does not discriminate in any employment opportunities or practices based on an individual's race, color, creed, gender (including gender identity and gender expression), religion (all aspects of religious beliefs, observance or practice, including religious dress or grooming practices), marital status, registered domestic partner status, age, national origin or ancestry (including language use restrictions and possession of a driver’s license issued under California Vehicle Code section 12801.9), natural hair, physical or mental disability, political affiliation, medical condition (including cancer or a record or history of cancer, and genetic characteristics), sex (including pregnancy, childbirth, breastfeeding or related medical condition), genetic information, sexual orientation, military and veteran status or any other consideration made unlawful by federal, state, or local laws. It also prohibits unlawful discrimination based on the perception that anyone has any of those characteristics, or is associated with a person who has or is perceived as having any of those characteristics. \n\nPlease mention the words **COPPER SNAKE VIEW** 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 $120,000 — $180,000/year\n \n\n#Location\nUnited States

At Scribd (pronounced “scribbed”), we believe reading is more important than ever. Join our cast of characters as we work to change the way the world reads by building the world’s largest and most fascinating digital library: giving subscribers access to a growing collection of ebooks, audiobooks, magazines, documents, Scribd Originals, and more. In addition to works from major publishers and top authors, our community includes over 1.5M subscribers in nearly every country worldwide.\n\nOur team\nThe Publisher Content Management team is responsible for building and evolving Scribd’s content and metadata ingestion services, publisher payout pipelines and the tools that enable our Content Operations team to manage the availability of our ever growing corpus of premium content. The team’s technical work is currently divided between our online Rails application and our offline Databricks environment (Scala, Spark, Airflow). Many of the systems we're responsible for span both environments, so engineers regularly work within both. Though the tech stacks differ between environments, the engineering work covers the same domains. Our team has a lot of interesting and challenging problems to tackle over the next few years as we continue to improve our systems and tools, while also investing in evolving and scaling them.\n\nThe team is located in San Francisco, but we foster a remote first culture. We use tools that emphasize asynchronous communication (Slack, Github, Jira, Google Docs) but will also pair program or jump into a meeting room when those are the best approaches. Regardless of the medium, excellent communication skills are a must. We operate with autonomy (developers closest to the code will make the most well-informed decisions) while holding ourselves and each other accountable for using good judgement when faced with each day's unique challenges.\n\nWe value team first Individuals. We work collaboratively, not as engineers working on individual projects in silos. We continually strive for inclusivity and strongly value diversity. We recognize that everyone has a unique set of work and life experiences, and believe that a broader set of perspectives will produce better results for all. Each day provides both opportunities to perform and opportunities to learn. We support others' growth and celebrate our collective achievements.\n\n\nThe role\nAs the Lead Software Engineer of the Publisher Content Management team, your job will be to provide hands-on technical leadership across all of the team's in-progress work as well as the team's technical roadmap. \nThe responsibilities include:\n• Leading the design, implementation, and delivery of your primary project.\n• Managing all aspects of technical project delivery, including system and architectural design, project planning, implementation, deployment, and operations.\n• Ensuring consistency of design, adherence to Scribd engineering principles and practices, and operational excellence across all team work.\n• Working closely with the team's Engineering Manager to prioritize technical projects and improvements relative to requested feature work.\n• Help shape the long term roadmap for evolving team systems to support orders of magnitude growth of Scribd's subscribers, and publisher/premium content.\n• Being a presence that makes every engineer on the team better via mentoring, coaching, and leading by example.\n\nAs the responsibilities demonstrate, the Lead Software Engineer role is more than just an advanced IC role. It is a hands-on leadership role, where you will balance the responsibilities of project work with technical team leadership. Your years of experience allow you to give guidance on projects you aren't deeply familiar with and quickly diagnose root causes of bugs. You and the Engineering Manager will be a team, with your expertise and ability to handle daily technical blockers enabling the Engineering Manager to focus on interviewing and hiring, people management, and project and roadmap planning.\nIf these responsibilities strongly match your interests in your next role, then you should apply!\n\n\nOffice or remote? \nAt this time the role will start as full-time remote, as all of our employees are working from home. When everyone is able to return to the office this role is available at our San Francisco office. This position can also be fully remote for candidates with experience leading development remotely.\n\nRequirements\n• 10+ years of experience as a professional software engineer with a focus on backend systems\n• 3+ years experience working with data pipelines\n• Experience managing multiple projects or a strong desire to take on these new responsibilities\n• Deep knowledge of common data architectures and industry technologies\n• Bachelor’s in CS or equivalent professional experience\n\n\nBenefits, Perks, and Wellbeing at Scribd\n\n• Healthcare Benefits: Scribd pays 100% of employee’s Medical, Vision, and Dental premiums and 70% of dependents\n• Leaves: Paid parental leave, 100% company paid short-term/long-term disability plans and milestone Sabbaticals\n• 401k plan through Fidelity, plus company matching with no vesting period\n• Stock Options - every employee is an owner in Scribd! \n• Generous Paid Time Off, Paid Holidays, Flexible Sick Time, Volunteer Day + office closure between Christmas Eve and New Years Day\n• Referral bonuses\n• Professional development: generous annual budget for our employees to attend conferences, classes, and other events\n• Company-wide Diversity, Equity, & Inclusion programs which include learning & development opportunities, employee resource groups, and hiring best practices.\n• Learning & Development and Coaching programs\n• Monthly Wellness, Connectivity & Comfort Benefit\n• Concern mental health digital platform\n• Work-life balance flexibility\n• Company events + Scribdchats\n• Free subscription to Scribd + gift memberships for friends & family\n\nWant to learn more? Check out our office and meet some of the team at www.linkedin.com/company/scribd/life\n\nScribd is committed to equal employment opportunity regardless of race, color, religion, national origin, gender, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law.\n\nWe encourage people of all backgrounds to apply. We believe that a diversity of perspectives and experiences create a foundation for the best ideas. Come join us in building something meaningful. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Engineer, Executive, Developer, Digital Nomad and Backend jobs that are similar:\n\n $65,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
\n\n#Location\nRemote - US/Canada

## About us\n\n[Eleos Technologies](https://eleostech.com/) is a growing 8-year-old company building communication software for truck drivers and field workers.\n\nWe're helping a diverse mix of customers—from mom and pop operations to household names—improve how they communicate with their employees by tackling information overload, reducing phone calls, and eliminating obsolete technologies.\n\nOur engineering team has been 100% distributed since day one. This means we're tooled up to handle product, architectural, technical, and ops work all from home or remote. You won't miss out of office conversations, and you won't have to learn to drive a telepresence robot.\n\nWe offer robust healthcare (dental, medical, vision), paid time off, and a generous equipment budget.\n\n## About the role\n\nYou'll be the primary caretaker of the Erlang web application powering our product, as well as collaborating Ruby on Rails services and the virtual infrastructure they run on.\n\nBecause the Erlang system has no direct user interface, you'll work closely with our iOS, Android, and frontend web engineers to evolve the backend's functionality to solve new problems, all while improving performance and ensuring reliability.\n\nYou'll be helping us make our development cycles more efficient by owning the technical design and implementation of new features, extending our automated test suite to reduce the need for manual testing, and shipping fixes on a regular basis.\n\nYou'll have opportunities to flex your skills around automated deployments, automated testing, tracing and visibility, and learn from others in a collaborative environment.\n\nIn time, you'll also help onboard and mentor junior engineers as we grow our team.\n\nThis is a full-time position open to anyone who can work legally in the United States.\n\n## About you\n\nWe're looking for a senior-level engineer to own the backend systems powering our product.\n\n### Key skills\n\n* 4+ years professional experience implementing and operating HTTP web services\n* 2+ years professional experience working with Erlang, Elixir, or another functional programming language like Clojure or Haskell\n  **Or:** Substantive OSS contributions in these languages, in lieu of professional experience\n* Confident use of SQL, relational storage, and key/value storage to optimize for correctness and performance\n* A willingness to mentor other engineers and to share your knowledge to help them grow\n* The ability to quickly convey ideas, opinions, and technical details in written English\n* Ability to participate in an on-call rotation to respond to and resolve (rare ⭐️) major incidents and outages affecting our stack\n* Able to work 8-5 Eastern Standard Time ± 3 hours, to facilitate realtime collaboration when needed\n\nThe following aren't requirements, but be sure to mention them if they apply to you:\n\n* Experience working with Amazon Web Services or one of the other major cloud providers, with an emphasis on configuration languages and infrastructure-as-code\n* Experience with Docker or other common containerization platforms\n* A working knowledge of Ruby or JavaScript\n\n### Technologies\n\nWe take a "reasoned opinions, weakly held" approach to tools, and resist letting those tools define our identity. That said, we've had positive experiences with (and made significant investments in) the following, which does mean you'll be working with them at least in the medium term:\n\n* Erlang/OTP (using the Cowboy and Hackney libraries heavily)\n* Ruby on Rails\n* Clojure\n* PostgreSQL\n* Amazon Web Services\n\nIf this sounds like a fun challenge and your kind of environment, drop us a line and let's talk! \n\nPlease mention the words **BROOM LOVE MOON** 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 No salary data published by company so we estimated salary based on similar jobs related to Clojure, Erlang, Engineer, Backend, Full Time, Amazon, Cloud, Ruby and Junior jobs that are similar:\n\n $70,000 — $120,000/year\n \n\n#Location\nUnited States