Medior/Senior Product Engineer (backend)

<p><strong>Location</strong> : Budapest, Hungary (hybrid)</p><p><strong>Seniority :</strong> Mid-level // Senior level</p><p><strong>Hours</strong> : Full Time</p><p>---</p><h2><strong>About Craft</strong></h2><p></p><p>At Craft, we are on a mission to redefine productivity through software. We believe that current solutions are outdated and bloated. We are building products that are fun and effortless to use, software that blends into the background, allowing individuals to focus on their tasks at hand - as it should be. We have an amazing team of experienced product engineers.</p><p></p><h2><strong>About the role</strong></h2><p></p><p>Our<strong> Services</strong> team is responsible for the foundational building blocks on the Craft platform. From databases, authentication, realtime content sync and management, to APIs and everything in-between, this team provides core functionality for other teams so they can conveniently build the brilliant features that our users love in Craft.</p><p>As a Backend Engineer at Craft you will be responsible for design, planning, scoping, and implementing services that integrate our mobile and web clients with our core services and data. These API's need to be highly performant, scalable and reliable and you will need to be familiar with CI/CD and 'infrastructure as code' environments. You will mainly be using Node.js and TypeScript but you will also get involved with our cloud-native backend platform using PaaS and serverless on AWS. Familiarity with all these technologies is a real bonus, but we mainly need you to come with a willingness to learn and make impact.</p><p></p><h2><strong>What we're looking for</strong></h2><p></p><p><strong>You must have:</strong></p><p></p><ul><li><p><strong>Experience with databases and data management</strong> - Ideally you have solid experience with relational databases and data search technologies.</p></li><li><p><strong>Experience with Cloud architectures and best practices </strong>- You will need to have at least basic familiarity with PaaS, FaaS, DBaaS, containers, etc. (in an ideal world: on AWS)</p></li><li><p><strong>A passion for writing testable code</strong> - you can architect code so critical code paths can be covered with comprehensive, automated test suites.</p></li><li><p><strong>Continuous Delivery &amp; Deployment Mindset</strong> - You are comfortable with frequently deploying changes to production; right after they end up on the master branch.</p></li><li><p><strong>Attention to detail</strong> - you have deep interest in figuring out how things work underneath.</p></li></ul><p></p><p><strong>It would be great if you have:</strong></p><p></p><ul><li><p><strong>Familiarity with Node.js and Typescript</strong> - you can start building production services value with these technologies, or you can quickly learn and get up to speed with them</p></li><li><p><strong>Familiarity with “Infrastructure as code”</strong> - you do infrastructure deployments with sourced controlled definitions (preferably AWS CloudFormation)</p></li><li><p><strong>Experience with building scalable and resilient distributed systems </strong>- you have experience with microservice architectures and cloud-native systems that can serve millions of customers globally 24/7</p></li><li><p><strong>Security awareness</strong> - as you respect user privacy, you always consider security during every phase of development.</p></li></ul><p></p><h2><strong>How we work in the backend team</strong></h2><p></p><ul><li><p><strong>Daily standup: </strong>we have daily focused standup meetings which we prepare for using Craft, we write daily notes about what we did yesterday and what we are planning to do during the day. This helps us during the standup to focus on what matters and unblock each other if needed.</p></li><li><p><strong>Weekly-sprint planning: </strong>every Friday we close the week with a planning session for next week, to discuss next week's priorities.</p></li><li><p><strong>Retrospective every 3 weeks: </strong>here we provide the space and time to thank one another for going the extra mile, and highlight what went well and what could've gone better. These discussions help us to adapt and introduce new approaches for the next 3-week cycle.</p></li><li><p><strong>Services Guild meeting:</strong> Common topics are: knowledge-sharing about particularly complex projects, raising attention to tech debt or developer experience improvement possibilities, proposing solutions for upcoming projects, and reviewing new tools, libraries, and technologies.</p></li></ul><p></p><h2><strong>Your future colleagues said: What makes someone successful as a backend engineer? </strong></h2><p></p><p><em>"Maybe two things.<strong> Attention to detail:</strong> paying attention to the smallest detail and not waiting for others to search/solve things for you. <strong>End-to-end ownership:</strong> build with the thought in mind, that you'll be responsible for it to serve th