\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

Oddball believes that the best products are built when engineers understand and value the things they are working on. We value learning and growth and the ability to make a big impact at a small company. We believe that we can make big changes happen and improve the daily lives of millions of people by bringing quality software to the federal space.\n\nWhat we’re looking for is a Full stack engineer with experience developing, testing and debugging new moderately complex software solutions or enhancements to existing software in a maintenance capacity, and is committed to delivering and improving quality services to the Veterans Administration and the entire Veterans community. Need to have an understanding and desire to discover the existing business application and how it works.\n\nOur engineering team is distributed, and largely asynchronous. We value a calm, collected environment where you can focus on doing great work. Aside from a couple of weekly check-ins or project updates, you'll be able to work interruption-free.\n\n**What you'll be doing:**\n\nWorking hand in hand with other engineers in developing end-to-end testing solutions and API endpoints and services. Day to day work will involve writing code, developing tests, and debugging. Room for growth to work on various applications and teams within the Platform as we continue to expand and grow.\n\n**We are looking for someone with the following skill set:**\n\nBachelor’s Degree with 4+ years of experience \n4+ years experience working with Rails\n3+ years experience with a front end JS framework (preferable React)\nThe ability to write code that is a pleasure for other engineers to read and understand\nThe ability to speak and write in terms that non-developers can understand clearly, whether it be in a conference call, blog post or support email\nA solid understanding of API design and how backend systems work \nExperience with all phases of the software development lifecycle - from gathering and analyzing user/business system requirements to creating application system models\nMust be self-motivated, detail-oriented, and take initiative in performing tasks.\nTeam player must be able to work professionally and collaboratively with the government customer and other contract members of the project team.\n\n**Salary**\n\nSalary for this position is competitive and is a contract role. We offer both a tech, and a continuing education stipend.\n\n**Clearances**\n\nAbility to obtain low-level federal clearance is required \n\nPlease mention the words **EAGLE WHEN TRUCK** 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 No salary data published by company so we estimated salary based on similar jobs related to JavaScript, React, Ruby, API, Engineer, Design, Digital Nomad, Education and Backend jobs that are similar:\n\n $65,000 — $120,000/year\n
\n\n#Benefits\n ⏰ Async\n\n
\n\n#Location\nUnited States

\nChristian Care Ministry’s mission is to connect and equip Christians to share their lives, faith, talents, and resources with others. We primarily do so through Medi-Share, but as an association of churches, we’re rapidly expanding our “ministry portfolio” and we think technology will be at the center of accomplishing that goal. That’s where you come in. We need help creating and supporting applications (mobile + browser) for the future products and projects we’ve got in the proverbial “hopper.”\n\nBut before we go any further, you need to know if you’ll like working with us. We think you will.\n\nA bit about us: You already know the mission of Christian Care Ministry (CCM). We have about 580 employees in various states, but most of them are either at our headquarters in Melbourne, FL, or our Colorado Springs, CO branch. Medi-Share has been growing in every way imaginable since about 2010. It has become commonplace for our CFO to say things like “We’ve grown 30% year over year …again” at seemingly every quarterly employee town hall meeting. We’re extremely humbled and grateful to the Lord for the growth.\n\nChristian Care Ministry is a community of Christians that requires its employees to share its Christian religious beliefs and practices. CCM complies with all anti-discrimination laws applicable to religious employers. \n\nAbout the role: This position serves on the New Product Engineering Team in a Product Team setting. This small, sub-department of our IT team (which is currently under 10 people) is mostly remote. Their main focus has been making some dreams of the leadership team come true (well, at least the dreams that involve amazing code :). \n\nLife as an Employee with CCM’s New Product Engineering Team: We work really hard to make working here an amazing experience. It’s hard to find great talent like you, but if you pick us, we want to keep you for a long time. We have a team full of truly exceptional people—the kind you’ll be excited to work with. Here’s how we operate:\n\nDo you prefer mountains or oceans?\n\nWhile the majority of the NPE Team is distributed, it is our overwhelming preference that you live near our Colorado Springs, CO office or our headquarters in Melbourne, FL.  However, with modern tools, proximity doesn’t influence productivity and if absolutely necessary, we can discuss an exception (as long as it’s a state listed below that we already are a registered employer within). For this job in particular, we do need some collaboration though, so just make sure you have a reliable internet connection, of course.\n\nNo Crazy Hours\n\nThe New Product Engineering Team is operating in “start up” mode. This means that we work hard and smart to get projects completed in a reasonable timeline. On occasion, there may be instances when extra time is needed (usually around a product launch or a really big release), but those are pretty infrequent. Basically, we commit you to at least 6 hours of coding per day in our Sprints and as long as you get the work done, we’re okay with when you get it done. Just be available when the team may need your help, or when you may need their help. Sometimes life happens in the middle of the day, and we understand that. We also think “more meetings” means less time for coding so we protect your time. We have one morning stand-up at 10am EST where we find out when there could be overlap that day. Oh, one more cool thing about the only meeting you attend – we “eat our own dog food” and close each stand-up praying for Medi-Share members’ needs listed in our mobile app.\n\nUp Your Game\n\nWe’re serious about helping you improve your craft. We budget for it by giving you those extra 2 hours per workday to collaborate or learn. The stack we generally work on is relatively new so taking time to hone in your skills is pretty imperative. We send members to conferences or webinars as we need to. We love seeing our people growing.\n\nNow, back to you, our new Full Stack Developer…\n\nThis is the part where we describe the experience necessary to be considered for the position.\n\nYou’re a skilled developer, but maybe you haven’t gotten a chance to prove it yet professionally. We can give you that chance. \n\nBut before you get _too_ excited, let me explain. We only hire great developers, and this position is no exception. When we ask you to write or debug code during our interviews, you’ll do so confidently. You might not be able to show us 5 applications you’ve shipped, but you can point to something recent you’ve spent significant time coding that you’re really proud of, like your university project, your open source contributions, or your project at your last job. If we ask your professors, classmates, or coworkers about you, they’ll have great things to say.\n\nIn short, we won’t teach you how to be a good programmer, since you already are, but we can certainly help you be a better, professionally-experienced programmer.\n\nOur ideal candidate either has a college degree in computer science, or if not, 2+ years of recent, solid professional programming experience. Our especially ideal candidate has experience with either Node.js or React.js. Having only done that in your free time is fine. That tells us you are curious enough to learn on your own.\n\nOur stack contains a very healthy JavaScript client utilizing Heroku, Node.js, React.js, and a few others. CCM is in the process of migrating to Salesforce so we often interact with their APIs. For our mobile apps we’re using React Native, because, well, basically, it’s awesome (and we really think our philosophies of “API First” and “Learn Once, Code Everywhere” are going to be the norm in the near future). Our backend API servers use either Ruby on Rails or Node.js/Express, with PostgreSQL and Redis as our data layer. Despite those being our “sweet spots” before we take on a new product, we pick the stack that works best for that solution.\n\nYou’re the one we’re looking for if you:\n\n\n* Live in (or, if you want to live in) one of these states: AL, CO, FL, GA, IL, IN, OH, TN, TX, VA, WA, or WV.\n\n* Are curious how things work, you are self-motivated and self-driven.\n\n* Are an excellent developer and can adapt to new languages quickly.\n\n* Write code that is easy for other programmers to understand and use.\n\n* Thrive with directions like:\n\n\n* “Here is the mock up for feature X. How do you think we should approach this?”\n\n* "Check out the Jira story and play a bit with library X on GitHub. This might solve our problem Y. Let's discuss the pros and cons tomorrow."  \n\n* "This component needs to be re-architected to allow for X. How do you think we should do it and why do you think that's a good idea?"\n\n\n\n\n\n* Are excited to work across multiple platforms with different technologies.\n\n* You got a smirk on your face when you saw you could work on the stack listed above, AT A MINISTRY!\n\n* As you’ve read this job description, you realize this team obviously is comprised of people who you’d enjoy spending a work week with. (ended that sentence with a preposition, we're not paid for our grammatical skills)\n\n\n\n\nBonus Points\n\n\n* You already are a Medi-Share member or would want to join membership even if you didn’t work here.\n\n* You’ve built stuff using React Native (even if it was for your mom’s bingo club or something crazier).\n\n\n\n\nNext Steps\n\nSuper important stuff that sounds like it was written by lawyers:\n\nThis job description in no way states or implies that these are the only duties to be performed by the employee(s) incumbent in this position. Employee(s) will be required to follow any other job-related instructions and to perform any other job-related duties requested by any person authorized to give instructions or assignments. This document does not create an employment contract, implied or otherwise, other than an "at will" relationship.\n\nChristian Care Ministry is committed to serving the Lord and our membership with excellence. As employees we are committed to adhering to the same standard of Biblical principles of lifestyle and health as required for membership in our Medi-Share program which include:\n\n\n* Have a verifiable Christian testimony indicating a personal relationship with the Lord Jesus Christ, and profess the Statement of Faith\n\n* Attend a fellowship of believers, regularly and actively support that ministry, and live under the discipline of that body\n\n* Share the conviction that believers are to bear one another’s burdens according to Galatians 6:2\n\n* Believe the Biblical doctrine that their bodies are temples of the Holy Spirit and therefore are to be kept pure\n\n* Must not engage in sex outside of traditional Christian marriage\n\n* Cannot use tobacco or illegal drugs in any form, or abuse legal drugs or alcohol\n\n\n\n\n How To Apply\n\n\n* Apply here. In your cover letter, introduce yourself and explain why this position is of interest to you, and why you would be a great fit.\n\n* Please include links to apps you’ve built or anything else that makes you look good, and describe your role in building those apps. (If they’re internal, you can skip the link part.)\n\n* If you have a prepared resume, attach it in PDF form. If you don’t have a resume because you aren’t even sure you’re looking to change jobs, that’s fine! An informal list of your work and education history are all we’re looking for. Plus, you’ll see at our site we ask for a lot of the same info anyway.\n\n* Please complete the following questions, and include them with your cover letter. This shouldn’t take you very long.\n\n\n* What are your two strongest programming languages? Is there another language that you’re curious to learn next?\n\n* If you were interviewing a prospective candidate for this position, what would be a good interview question to ask to find out if a candidate really knew their stuff?\n\n* In a 2-3 sentences, what has your life with Jesus looked like over the last 3 weeks? There’s no wrong answer.\n\n\n\n\n\n\n\n\nThere will be a few other things if we get past the first interview, but we’ll cover that later. We even like doing our hiring on an iterative basis. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Full Stack, Developer, Digital Nomad, React, Jira, JavaScript, Education, Salesforce, Ruby, API, Mobile, Legal 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