<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Benoit Guillon on Medium]]></title>
        <description><![CDATA[Stories by Benoit Guillon on Medium]]></description>
        <link>https://medium.com/@benoit_86663?source=rss-228dd27a587e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rdLOCHBVxKWgjyRS8RXUsA.jpeg</url>
            <title>Stories by Benoit Guillon on Medium</title>
            <link>https://medium.com/@benoit_86663?source=rss-228dd27a587e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:37:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@benoit_86663/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Engineering career path at Malt]]></title>
            <link>https://blog.malt.engineering/engineering-career-path-at-malt-3e76e8318281?source=rss-228dd27a587e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e76e8318281</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[principal-engineer]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[staff-engineer]]></category>
            <dc:creator><![CDATA[Benoit Guillon]]></dc:creator>
            <pubDate>Thu, 21 Apr 2022 00:29:26 GMT</pubDate>
            <atom:updated>2022-04-21T09:59:53.232Z</atom:updated>
            <content:encoded><![CDATA[<p>This articles introduces the first public version of our engineering career path at Malt. It mainly explains how our career path works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SWDVQnFaxGT0k1dorjQcqA.png" /></figure><p><a href="https://docs.google.com/document/d/e/2PACX-1vTZGJWF1EUx0CG8s005Ge7ui2hYr5hGE_6HXK9O-CHEAHZj2NDIgomLbkJhs_i60x_cAASTvCPXqtQe/pub">You can access the full version here.</a></p><p>The purpose of this career path is to formalise what is expected from software engineers at the different levels of their career, what they can do to level up and the different options they have to evolve at Malt.</p><h3>How it works</h3><p>In order to assess individual performances, we rely on a set of clear expectations we hold about individuals: it covers how they master different expertise areas (hard skills), how they behave (soft skills) and what is their impact on the product and the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sxogF7MkpVHyogdQ" /></figure><h3>Ladders and steps</h3><p>The engineering career path is composed of 3 ladders: individual contributor, leader and manager. A ladder is a linear path of career progression that is followed by employees during their career at Malt. Switching from a ladder to another is possible under the conditions described later in this document.</p><p>A ladder is composed of several steps. Each step is defined by a title (junior, senior, intermediate, staff…) and a clear description of the employee’s <strong>expected impact</strong>.</p><p>To be more precise, this impact is described as a list of general expectations the employee has to meet continuously to be successful at this step. These expectations are general enough to be applicable to any role in the engineering organisation and require both hard and soft skills.</p><h3>Impact</h3><p>Being impact oriented is one of our mantras in Malt’s engineering team. It means to be focused on outcome (results) more than output (projects, technology, deadlines).</p><p>Software engineers’ influence area can be seens as a set of concentric circles, centred on the person. Progressing in this career path means improving impact’s intensity as well as extending this area.</p><p>As individual contributors, software engineers start working for themselves (junior) and progressively start becoming good (intermediate) and major (senior) players for their team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v-OpHxSQ-Wtym_Dd" /></figure><h3>Expertise</h3><p>Building a product like Malt requires people mastering different specific technical areas, going from frontend development to cloud operations or data engineering. Mastering all these areas in depth is not a goal for a single person. Instead, software engineers will usually start with a strong technical area they will develop during their career and gradually explore additional areas while keeping on developing this strong primary area of expertise.</p><p>At Malt, we value people with strong technical skills, and having a primary area of expertise is more than expected of software engineers. It defines the role they will play in their team (being a frontend developer in the freelancer tribe for example) or will potentially define the team they belong to (being a data engineer in the data team). It will also set the expectations we can have towards people — basically don’t expect a data engineer to quickly create a super fancy landing page ;-)</p><p>The primary area of expertise of software engineers define their expertise in the organisation.</p><p>At some steps in the engineering career path, it is expected that people become knowledgeable outside their primary area of expertise and gain expertise in different related areas.</p><h3>Step + Expertise = Job</h3><p>The combination of a step (e.g. senior) and an expertise (e.g. frontend engineer) makes a job (senior frontend engineer). This combination determines the expectations we hold on engineering team members and are used both to assess individual performance and hire new people.</p><h3>Steps, levels, and salary</h3><p>Each step of each ladder is mapped to a level from 1 to 11, which determines a range in the salary grid. It is totally possible that two steps from two different ladders are mapped to the same level.</p><h3>Career evolutions &amp; progression</h3><p>Career evolution is the process of changing jobs within the organisation.</p><p>3 cases are covered:</p><ul><li><strong>Stepping up within the same ladder</strong>: progression from one step to the next one is not automatic. An employee may only reach the next step when all the expectations of the current step are continuously met during a given period of time, and when some expectations of the next step are at least partially met. Some steps may also be reached after a minimal experience in the previous one.</li><li><strong>Switching to a different ladder</strong>: at some specific steps of a ladder, it is possible to switch to a different ladder. Ladder transitions are challenging! They require the help of management, HR and/or a specific coaching and mentoring.</li><li><strong>Changing expertise</strong>: a software engineer can expect to focus on a different area of expertise (for example, a backend engineer wants to switch to data engineering). This transition does not involve any progression in the career path but an expertise change and probably a team change. So, there is no associated ladder or step change and consequently no salary change.</li></ul><h3>Organizational roles vs levels</h3><p>Malt’s engineering team’s internal organisation defines 3 specific roles (or labels) in the engineering team: tech lead, guild lead and head of.</p><p>These roles are not described in this document as they are not considered as levels in the career path per-se.</p><p>The main reasons are:</p><ul><li>It wouldn’t scale as we can have only one tech lead per squad and one guild lead per guild, and one head of per matter so it would limit the number of people that could be promoted to some levels due to organizational constraints</li><li>It would narrow engineering leaders’ role to very specific positions in the organisation</li><li>It would prevent from sharing this role with someone else or set-up round robins within teams to take these roles</li><li>It would go against the philosophy of these roles (help group of people).</li></ul><p>However, as mentioned later in the document, taking one of these roles and being successful at it is a prerequisite to enter the engineering leader ladder.</p><h3>Some obvious points that are worth mentioning</h3><p>The expectations listed for each level are tasks that engineers must achieve, or behaviors that engineers must adopt while doing their day-to-day job in their team. So this list of expectations should not prevent engineers from doing their duty or what is best for their team.</p><ul><li>Being a senior engineer does not mean ignoring “trivial” tasks and only focusing on designing more complex tasks.</li><li>On the other hand, being an Intermediate Software Engineer 2 should not prevent you from investigating complex performance issues.</li><li>Finally, expectations are cumulative within a ladder: someone being on level X is expected to meet level X expectations and all expectations of previous levels.</li></ul><h3>Want to read more ?</h3><p><a href="https://docs.google.com/document/d/e/2PACX-1vTZGJWF1EUx0CG8s005Ge7ui2hYr5hGE_6HXK9O-CHEAHZj2NDIgomLbkJhs_i60x_cAASTvCPXqtQe/pub">You can access the full version here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e76e8318281" width="1" height="1" alt=""><hr><p><a href="https://blog.malt.engineering/engineering-career-path-at-malt-3e76e8318281">Engineering career path at Malt</a> was originally published in <a href="https://blog.malt.engineering/">malt-engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malt Tech Days, product and tech culture on steroids]]></title>
            <link>https://blog.malt.engineering/malt-tech-days-product-and-tech-culture-on-steroids-4da9e5ba19eb?source=rss-228dd27a587e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4da9e5ba19eb</guid>
            <category><![CDATA[curiosity]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[engineer]]></category>
            <category><![CDATA[malt]]></category>
            <dc:creator><![CDATA[Benoit Guillon]]></dc:creator>
            <pubDate>Thu, 14 Apr 2022 07:54:15 GMT</pubDate>
            <atom:updated>2022-04-14T07:54:15.078Z</atom:updated>
            <content:encoded><![CDATA[<p>We organized the 4th edition of ‘Malt Tech Days’ on March 15 and 16. And as in previous years, we pulled out all the stops :-) Here we take a look back at this in-house meetup which, like a good wine, improves from year to year.</p><p>The principle of Malt Tech Days is simple: it is a tech conference that is organized, presented and attended by Malt’s engineering team.</p><p>Everything else gets put on hold: projects, support, recruitment, we’re only available if there is an absolute emergency! And as with every edition, the event was greeted with goodwill and interest from our Malt colleagues, who were happy to drop by out of curiosity.</p><p>While the last edition was held by videoconference (due to the health regulations), this time the whole team put down their keyboards for two days and got together in our Parisian offices. Considering they mostly work remotely, it was a real pleasure to be able to spend time together.</p><p>In total, we were able to attend 18 talks with different formats (presentations, live coding, mob workshop, demos, magic tricks) and we welcomed 2 guests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7qVCiIYAV1rERWEn9MKMkA.jpeg" /></figure><h3>Cultivating curiosity, together</h3><p>Curiosity is an essential element in Malt’s engineering team ethos. We promote this in our job descriptions, our career path and during interviews with applicants. And we provide ourselves with the resources to cultivate this curiosity: team members have a choice of formats between books, e-learning platforms and/or taking part in conferences.</p><p>Guilds (front, back, security, data, design system…) are also mechanisms for working on our technical culture. These communities focus on cross-teams practices and are open to all. Their active members can devote one day per week to technical watch activities or to technical improvements to the product or the tools that are used on a daily basis.</p><p>As in previous years, this edition of the Malt Tech Days was an opportunity for the speakers to share their daily experiences or feedback on past situations.</p><p>Johan presented some of the internals in our brand-new CI / CD on GitLab CI. The central question for the project was highly technical: starting from a mono-repository containing hundreds of modules, how can we create an efficient and scalable CI, building only the bare essentials for each git push… and he had the pleasure of answering a lot of extremely interesting questions ;-)</p><p>Nicolas P. took a look under the hood of our front build mechanism in a plenary session, walking us step-by-step through the process of building the different front assets that are in production. Guided tour backstage for pnpm and webpack.</p><p>Cédric gave us a guided tour of the CQRS/ES architecture for our brand-new customer-freelance relationship management application. The application is the foundation for many future product enhancements to make the current messaging-based relationship more streamlined. Here, CQRS/ES is not used randomly. Storing every event to do with the relationship will enable us to better understand its dynamics, and therefore make the product even more relevant in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LwqNGTM0TGpa-VXQOcALA.jpeg" /></figure><p>Théo and Nicolas M., two of the team’s data scientists, shared with us the basics of performance evaluation and explainability of machine learning models. With simple and concrete examples, they managed to demystify the subject while putting into perspective the inherent complexities at scale.</p><p>Although we are more focused on trunk-based development, Christophe reminded us of how some organizations use git-flow, during a workshop that quickly turned into a discussion group on our ability to deliver quickly.</p><p>We also hosted two guest speakers, and we would like to thank the people we invited for their participation and the quality of their talks:</p><p>Arthur, CEO &amp; co-founder of Promyze, came to give us his feedback on sharing best practices within dev teams. How can we manage to formalize team decisions, perpetuating and implementing good dev’ practices without creating documentation that nobody will read after a couple of days? Arthur shared with us some good practices that he was able to put in place in different companies and presented us with some solutions that Promyze develops to meet these challenges.</p><p>Finally, Xavier and Jérémie from the leboncoin engineering team came to present their work on webperfs. What were the impacts of a series of small webperf regressions on the company’s business? They explained how they managed to get all the dev, product and business teams on board in a webperf virtuous circle: decentralized approach, simple, pertinent toolset and close monitoring.</p><h3>T-shaped profiles?</h3><p>Autonomy (or rather ownership) is one of Malt’s values. This is reflected in the engineering team, with each team being responsible for its part of the product from floor to ceiling. But you still need to have control over the ground (e.g. Terraform) and the ceiling (e.g. SQL injections or pnpm configuration)… The complementarity of team members is key, but that’s not all!</p><p>At Malt, we are quite keen on the notion of “T-shaped profiles”. This is a way of representing a person’s skills in the form of a capital T: the vertical and longest line represents the person’s main skills (e.g. backend development) and the shorter horizontal line represents their secondary skills (e.g. terraform or view.js for a backend developer). The secondary skills enable the person to be self-reliant, carrying out a task from A to Z. The representation is all the more appropriate since the horizontal line of the T is centered above the vertical one. Our secondary skills therefore mean we can go beyond our role, both upstream and downstream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VflBCFhrZ6XAXSbDlpCCig.jpeg" /></figure><p>The presentation by Ludovic and Jordan, representing the data engineering team, was a good illustration of what can be expected from T-shaped profiles. They shared with us their experience with serverless architecture on Google Cloud Platform. Starting from the background of their experiments, they shared with us the limitations they encountered and the countermeasures they implemented to overcome them. In the end, this talk was not really specifically about data engineering-related issues and was of interest to both our Cloud Ops team and backend developers. Being a data engineer at Malt is not just about developing data ingestion pipelines into Google BigQuery, you also need to have a firm grasp of the infrastructure needed to implement them.</p><p>For their part, Nicolas and Achille, front-end developers at Malt, tried their hand at the risky exercise of live coding in a plenary session. They managed to take us step by step through setting up a micro-frontend in vue.js embedded into a page rendered on the server side in JSP. To do this, the only solution is to implement backend controllers or to modify the service build configuration. There are no exclusive domains at Malt: “just do it”.</p><p>We use Elasticsearch quite extensively at Malt. Julien and Raphaël went over the basics of how ES works in tutorial mode, using a demo. Newcomers appreciated the presentation’s educational approach. Often a little removed from the issues related to server-side data storage and retrieval, the team’s front-end developers were able to grasp the basic concepts of ES.</p><p>Lionel, an Android developer, led a mob programming workshop on Flutter that was open to all. The stated goal: to build a Yuka-inspired application in 2 hours using Flutter. The experience enabled the workshop participants to discover a new technical stack and also to understand how to develop a hybrid desktop / mobile application. Beyond the purely technical aspects, some people who are not usually involved in mobile development had the opportunity to get to grips with the specific issues of the job.</p><p>Alexandre, a data analyst in the Sales Ops team, looked back at our migration project from Chart.io to Looker, which happened earlier this year. He explained the main principles of our new data visualization architecture and how it will enable us to make teams more self-reliant overall when producing new data visualization dashboards.</p><h3>Investing to increase our impact</h3><p>“Impact” is probably one of the words we use the most right now within the team. We ask our leads or staff engineers to work on their positive impact on their squad, tribe, guild, the product, Malt, freelancing, industry. We learn to measure this impact, to value it, to better communicate results, to be exemplary. We believe that every engineer’s progress depends on having a growing positive impact on the ecosystem around them.</p><p>Sahbi, fullstack engineer within the Financing &amp; Payment squad, gave us a perfect demonstration of what it is to have a direct positive impact on the product and therefore the company. During his talk entitled “How to scale the financial brick of a marketplace”, Sahbi shared with us how his team managed to drastically reduce payment times for Malt freelancers, improve the take-up of long missions in our freelance community in Germany and, in passing, make life easier for our finops teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUaWz-M2R_-m8UhYbZ_wzQ.jpeg" /></figure><p>Starting from problems encountered in the past or still present in our code base, Nicolas helped us gain some perspective on inter-service communication. When retries, circuit breakers and command queues are no longer enough to guarantee the reliability of our complex and long-living workflows, it is time to implement new solutions, such as sagas. A technical but accessible talk to help people to get to know this pattern. This talk will clearly have a positive impact on our marketplace reliability in the near future.</p><p>During his workshop “No mock is the new mock”, Jean shared best practices on how to set up robust and genuinely useful unit tests with the participants. Mocks can be appealing, especially when using tools that make them easy to deploy, but it is also easy to fall into their trap and end up writing tests that are based on the mocks’ behavior rather than the code that is actually being tested.</p><h3>Engineering managers also on board</h3><p>During 2021, we created the position of engineering manager at Malt, convinced that these managers should be hands-off and fully dedicated to supporting individuals and teams, as the best way to cope with team and company scalability. Two of our engineering managers took part in this year’s Malt Tech Days, each delivering a high caliber talk in their own style.</p><p>We already knew about Fabien’s talents as an iOS developer, since he was our historical developer on the platform before becoming engineering manager. On several occasions, Fabien has also treated us to demonstrations of his skills as a magician. This time, Fabien shared with us another of his passions: how to solve the Rubik’s cube. After a brief historical overview, Fabien presented an iOS application, developed by himself, which guides the user through solving a Bluetooth-connected Rubik’s cube. After the technical part, it was time for the one-man show: Fabien blew us away by recreating, off the top of his head and in a matter of seconds, the configuration of a Rubik’s cube that had been scrambled by an independent party and that he had committed to memory in 10 seconds.</p><p>An engineering manager in the client tribe, Jean’s presentation on the risks of burn-out was highly praised. Based on his personal experience, Jean humbly shared with us the burn-out warning signs, using a metaphor of a prairie/rabbit system that is stretched to the limit. The authenticity of his testimony, the honesty with which it was shared and the humility with which he spoke, held the audience spellbound. No doubt this talk will be remembered for many Malt Tech Days to come.</p><h3>Organization: “it takes a community”</h3><p>On the organizational side: we agree on a date, a place and off we go! Actually, it’s a little more complicated than that: you have to book travel, accommodation, meals, organize a call for paper, votes, set an agenda, book rooms, make sure that all the audio and video equipment works, invite guests… The Malt Tech Days have become an ‘event’!. The resources available are in proportion to our ambitions, and we are only at the beginning of this adventure.</p><p>When it takes place IRL, the event also gives rise to informal and spontaneous interactions that are difficult to have when working in a geographically distributed team. This is why we had planned long lunch breaks, a few coffee breaks and a social gathering in the evening.</p><p>As in every edition, the speakers took risks, stepped out of their comfort zone. For some people, this was their first time as a speaker in a “conference” format, so it was a good experience, despite the attendant measure of stress. For others, it was also an opportunity to test a format or subject within a familiar setting. In any case, goodwill and benevolence prevailed.</p><p>To round things off, we finished with a Google Form sent to all participants, allowing them to give feedback on each presentation as well as on the general organization.</p><p>We owe its success to the organizing team for the event, which was absolutely fantastic, so we’ll end this blog post with warm thanks to Fabien, Adèle, Camille, Elodie and Jelly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4da9e5ba19eb" width="1" height="1" alt=""><hr><p><a href="https://blog.malt.engineering/malt-tech-days-product-and-tech-culture-on-steroids-4da9e5ba19eb">Malt Tech Days, product and tech culture on steroids</a> was originally published in <a href="https://blog.malt.engineering/">malt-engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>