<?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 Siiri Hakulinen on Medium]]></title>
        <description><![CDATA[Stories by Siiri Hakulinen on Medium]]></description>
        <link>https://medium.com/@siirihakulinen?source=rss-c8dd5e71c3e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*hh5hq7qJ2qFWLeZt9Nrlgw.jpeg</url>
            <title>Stories by Siiri Hakulinen on Medium</title>
            <link>https://medium.com/@siirihakulinen?source=rss-c8dd5e71c3e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:07:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@siirihakulinen/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[Meet Our Product Development Teams: Midas]]></title>
            <link>https://medium.com/smartly-io/meet-our-product-development-teams-midas-a37d1ad2d0a1?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a37d1ad2d0a1</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development-team]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Thu, 19 Mar 2020 13:33:31 GMT</pubDate>
            <atom:updated>2020-03-19T13:33:31.047Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AsICRGWK49KhYRoDPhnPKw.png" /></figure><p>Team Midas owns the core areas of the Smartly.io app that handle campaign creation and management. Midas, like <a href="https://www.smartly.io/blog/meet-our-dev-teams-senators">Senators</a>, is a new team split from a large, old one that operated everything related to Facebook. “We are working with some of the oldest code in the house,” says <strong>Juha</strong>, the team lead for Midas. “It’s great to now have the bandwidth to fix some of the issues that have pained Smartlie developers for a long time.”</p><p>By chewing the old codebase into a more digestible form, Midas is building a foundation for scaling the app further as well as accelerating product development speed. “We’re slicing the legacy codebase into smaller, more manageable entities,” Juha explains. “We can’t shut the campaign engine down and wipe out the legacy code all at once. Instead, we have to refresh it piece-by-piece, without disrupting the ever-ongoing operations. It’s like doing brain surgery without anesthesia”.</p><h3>A team of experienced developers</h3><p>To accomplish this feat, team Midas is made up of very senior developers. “ <a href="https://www.linkedin.com/in/riikkakalliomaki/">Riikka</a>, <a href="https://www.linkedin.com/in/grigorii-sokolik/">Grigorii</a>, <a href="https://www.linkedin.com/in/iiro-saukkonen-96394978/">Iiro</a>, <a href="https://www.linkedin.com/in/valentin-nemcev-88a2b578/">Valentin</a>, <a href="https://www.linkedin.com/in/oksana-firtych-39731593/">Oksana</a> and <a href="https://www.linkedin.com/in/marko-kurjonen-761b874/">Marko</a> are all seniors with extensive expertise,” <a href="https://www.linkedin.com/in/juhalitola/">Juha</a> says. “Put us all together and we have close to 100 years of software development experience in the team.” The team is now looking for a <a href="https://www.smartly.io/open-positions/54c79fdd-e84d-43f5-881b-7cd63026c855?hsLang=en">Backend Developer</a> to help them improve the software architecture and build new services.</p><p>“It requires a lot of brainpower to plan a refactoring of a complex old codebase, and you have to have an archaeologist’s mindset,” Juha says. “Our work is interlinked with that of many other development teams, most importantly with Bobby Tables, Senators, and Top Gun, which means that we have to be mindful of the possible repercussions of our actions. And it only gets more difficult as we’re done with the low-hanging fruits and proceed to the trickier parts of the old codebase.”</p><h3>Something old, something new</h3><p>When they aren’t tearing down the old PHP codebase, Midas works with React, JavaScript, and TypeScript. “Our app is in the middle of a transformation, where most of the campaign editing features are moving from the original campaign overview into our new reporting tool. Midas has a key role in packaging the campaign data neatly so it’s easier for the other team to manage within reporting,” Juha recounts. “At the same time, we’re pruning the old features and functionalities, carefully assessing which ones we could do away with to simplify the app structure.”</p><p>Midas is currently aiming to fully revamp the campaign creation and management functionality. “We’re now building user prototypes for the new implementation and finishing up basic architectural components on the backend,” Juha says. “The plan is to verify our interaction models with the prototype and then go full steam ahead starting in April.”</p><p>Learn more about being a developer at Smartly.io: <a href="https://www.smartly.io/careers/developers">smartly.io/careers/developers</a>.</p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-product-development-teams-midas"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a37d1ad2d0a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-product-development-teams-midas-a37d1ad2d0a1">Meet Our Product Development Teams: Midas</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Our Development Teams: Kino]]></title>
            <link>https://medium.com/smartly-io/meet-our-development-teams-kino-c0b42e55a5af?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0b42e55a5af</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 09:25:37 GMT</pubDate>
            <atom:updated>2020-01-20T09:25:37.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oohrMiIcIyJvGi-u" /></figure><p>Team Kino owns two flagship solutions of the Smartly.io platform: the <a href="https://www.smartly.io/blog/how-we-built-a-video-templating-system-capable-of-producing-a-million-videos-a-month">video</a> and image templating tools. Their mission is to scale and automate the production of creative assets for digital advertising and help customers improve their campaign results through ad creatives. “To put it simply, we build image and video editors that allow users to create unique and customized ad videos and images at a massive scale,” says <strong>Pasi</strong>, the team lead for Kino. “During the last 30 days, our image templating tools rendered 16 billion images on hundreds of servers. During peak traffic times, we serve 30 gigabytes of data per second and generate 2.5 terabytes of videos daily.”</p><h3>The visual trend in advertising poses exciting challenges</h3><p>As advertising is becoming more visual than ever before, Kino is in an exciting position to drive the development of the Smartly.io platform towards a more visuality-centric form of advertising. “With visuality trending in the advertising industry, a whole new user group has been introduced to our platform,” Pasi explains. “Previously, we have focused on serving performance marketers, the people who create, manage and analyze advertising campaigns, but today we also build tools for designers, who are in charge of the visual look of the campaigns.”</p><p>A new user segment brings exciting new challenges as designers’ requirements for the platform are quite different from those of performance marketers. “Apart from serving the needs of both user types separately, we are finding ways to help them collaborate,” Pasi says. “Designers and performance marketers haven’t traditionally been working very closely together, so we’re trying to help bridge the gap between them.”</p><p>The growing importance of visuality leads to a higher demand for image and video rendering power, posing another intriguing challenge to team Kino. “At the moment, our image editing service relies on extensive caching to avoid any extra rendering,” Pasi says. “At the scale where we operate, optimizing rendering saves us a lot of server space and money.”</p><p>Previously, we have scaled our image templating tools to handle image generation at a massive scale. Scaling video templating is going to be even more complex to scale. “Building a browser-based video editor is a fairly exceptional task in itself, it’s not something you can do in every developer job,” Pasi says. “Our video rendering service Reindeer is a pretty inventive piece of tech, to be honest, and scaling it will be a thrilling project.”</p><h3>Now hiring a full-stack engineer</h3><p>Developing two flagship solutions keeps team Kino busy, which means they need to maintain a crystal clear focus and prioritize projects rigorously. Pasi hopes they will soon find time for some housekeeping, too: “Our image template editor was built using Angular, but we have moved on to use React.js, Redux, and TypeScript in our frontend since then, so we’re going to update the editor to use the same stack.”</p><p><a href="https://www.linkedin.com/in/pasi-tuominen-4bb4325/">Pasi</a> and his teammates <a href="https://www.linkedin.com/in/riku-laukkanen/">Riku</a>, <a href="https://www.linkedin.com/in/oluwasayo/">Sayo</a>, <a href="https://www.linkedin.com/in/hollyrgibson/">Holly</a>, and <a href="https://www.linkedin.com/in/joonas-mertanen-15403012b/">Joonas</a> make Kino a more frontend heavy than the average development team at Smartly.io. Kino also differs from other teams because it isn’t in contact with Facebook or Pinterest APIs at all. Instead, they provide the creative platform for other development teams, like Senators, Midas, AweSoMe, and Graham. Kino’s developers collaborate closely with their product manager Maria and product designer Mala, and they are currently looking for <a href="https://www.smartly.io/open-positions/e6374dde-df28-460b-b4e4-25db2abac528?hsLang=en">a full-stack engineer</a> to join their team. “We’d like to find a new teammate with a good understanding of React/Redux, as well as experience with TypeScript and in building Node.js applications,” Pasi says.</p><p>Learn more about working as a developer at Smartly.io at <a href="https://www.smartly.io/careers">www.smartly.io/careers/developers.</a></p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-development-teams-kino"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0b42e55a5af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-development-teams-kino-c0b42e55a5af">Meet Our Development Teams: Kino</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Our Development Teams: Oodi]]></title>
            <link>https://medium.com/smartly-io/meet-our-development-teams-oodi-c8a4e155390?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8a4e155390</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Fri, 13 Dec 2019 08:00:22 GMT</pubDate>
            <atom:updated>2020-01-31T11:07:07.530Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aiD3U6JaBwVrV7vD" /></figure><p>Team Oodi’s mission is to determine how our customers use their media assets across the platform and make those workflows as smooth as possible. The team owns the asset library that our customers use to organize their media assets, like photos, videos, fonts and sound. “As advertising is becoming more visual, we’re playing a crucial role in building the backbone of Smartly.io’s creative tools,” says <strong>Hugo</strong>, the team lead to Oodi.</p><p>Apart from offering asset management for end users, Oodi provides its fellow development teams with components for accessing the asset library, as well as an internal asset management service. Oodi worked recently with team Senators to integrate the asset library component into campaign creation, allowing customers to search for and add assets to their ads. Next, it will buddy up with team Bobby Tables to enable customers to analyze assets in the actionable insights tool. “It’s almost like we have our own library that other teams can use,” Hugo says.</p><p>“This is why we need to be extra mindful to produce well-written and documented code,” Hugo says. “If Oodi’s code isn’t clean, other teams can’t use our service safely without the risk of breaking other components elsewhere in the product. And if those components fail, customers can’t create their campaigns. So we have a very central role in securing the stability of our platform.”</p><p>Oodi recently finished a big and hairy rewrite project, where they extracted the asset management functionality from the monolithic code base into its own microservice. “It was a real chore, but now we get to enjoy the fruits of our labor,” Hugo says. “We get to work with a modern stack and a clean codebase with very few bugs.” The assets are stored in AWS S3 managed by a Ruby on Rails microservice using PostgreSQL and Redis as data storage. The user interfaces for working with assets are built as a <a href="https://www.smartly.io/blog/how-we-built-a-seamless-user-experience-from-multiple-small-front-end-applications">micro frontend</a> with React, Redux, Styled Components, Jest and TypeScript.</p><p>At the moment, Oodi focuses on building functionality for tagging assets. Tagging allows customers to organize and search for assets more efficiently. In the future, they will also be able to analyze asset content and performance in the reporting tool. “In the future we hope to also automate tagging with AI,” Hugo says. After the tagging project is done and dusted, team Oodi will reconsider its focus. “It will be exciting to explore new projects and plan our roadmap further,” Hugo says. “The team will have a say in what projects we’ll focus on in the future.”</p><p>Team Oodi has been aptly named after the new Helsinki Central Library that neighbors our office. <a href="https://www.linkedin.com/in/hugokiiski/">Hugo</a> and his teammates <a href="https://www.linkedin.com/in/julius-hietala-8967b8a2/">Julius</a>, <a href="https://www.linkedin.com/in/jere-vaara-60773390/">Jere</a>, <a href="https://www.linkedin.com/in/luismanuelramalho/">Luís</a>, <a href="https://www.linkedin.com/in/eelis-kostiainen/">Eelis</a>, <a href="https://www.linkedin.com/in/wschrauwen/">Wesley</a> and <a href="https://www.linkedin.com/in/locke23rus/">Kirill</a> have created a strong team identity and a sense of community. They also work closely with their product manager <a href="https://www.linkedin.com/in/%C3%A7i%C4%9Fdem-%C5%9Feftalio%C4%9Flu-3a013831/">Cigdem</a> and product designer <a href="https://www.linkedin.com/in/mala-patel-47679925/">Mala</a>. “We have a culture of helping each other,” Hugo says. “We like to do a lot of pair programming, and those who are more familiar with some parts of our stack help others learn. We have also been planning to start our own mini library, where teammates can bring books for others to read and learn from.”</p><p>Oodi is currently looking for a <a href="https://www.smartly.io/open-positions/4e2dbcae-8102-40d3-9320-def9ae57d9c2?hsLang=en">frontend-focused fullstack engineer</a> fluent in current front-end development technologies like React and TypeScript. “Experience in building robust and scalable web backends with Rails or other modern technologies would be helpful, too.” Hugo says. “We don’t expect everyone to master all the technologies we use, though. It’s more important to have a self-starting attitude and to be able to orient yourself on the backlog on your own. Good communications skills are a bonus, we’re a pretty talkative team.”</p><p>Learn more about <a href="https://www.smartly.io/careers/developers">how developers work at Smartly.io</a>.</p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-development-teams-oodi"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8a4e155390" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-development-teams-oodi-c8a4e155390">Meet Our Development Teams: Oodi</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet our Development Teams: Autopsy]]></title>
            <link>https://medium.com/smartly-io/meet-our-development-teams-autopsy-a10410a794a4?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a10410a794a4</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[team-introduction]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[nestjs]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Tue, 19 Nov 2019 08:48:51 GMT</pubDate>
            <atom:updated>2019-11-19T08:48:51.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-IaGq7w_o3nuCx5ELxvq8g.jpeg" /></figure><p>Team Autopsy builds <a href="https://medium.com/smartly-io/statistical-significance-for-humans-automated-statistical-significance-calculator-for-a-b-testing-49123cea1edb">A/B testing</a> and fully automated optimization tools to improve both short and long term performance for our customers. Its name, while sounding ominous, is actually an acronym for the words automation and optimization. As one of the oldest development teams at Smartly.io, Autopsy is redefining its focus and cleaning up some of its historical burden, all the while working on an exciting new project.</p><h3>Building a new tool for A/B testing</h3><p>“We’re now in the process of finding a product/market fit for a completely new A/B testing solution,” says <strong>Lauri</strong>, the team lead for Autopsy. “Our mission is to make A/B testing as easy as humanly possible for our users. While we use advanced Bayesian modeling in the backend, we want the tool to be super simple to use.”</p><p>Autopsy is an inspiring example of how an old team with lots of history can reinvent itself and kick off a new project. “It’s exciting to get to plan a fresh tool from scratch,” Lauri says. “We’re building something that doesn’t exist yet, which means that we have a huge responsibility in figuring out what is the best way to go about building it.”</p><h3>Working closely with the most advanced customers</h3><p>In their quest to find the product/market fit, the team spends a lot of time talking to customers and gaining an understanding of their needs. Lauri recently got back from a three-week stint in San Francisco, where he met with some of the most advanced Smartly.io customers. “Many of our largest customers visit our Helsinki office on a regular basis, too, and all of our team members get to meet them and workshop with them to solve their most painful problems,” Lauri says.</p><p>“Our biggest challenges at the moment have to do with prioritization and finding a balance between product development speed and writing scalable and sustainable code,” Lauri says. “While we want to produce value to the customers on a weekly basis, we don’t want to resort to quick fixes.”</p><p>Thanks to its close cooperation with customers to plan the A/B testing product, customer centricity is an important prerequisite for thriving in team Autopsy. “You have to be keen to understand the business and solving the customers’ problems,” Lauri says. “Being excited about solving technical problems only gets us so far.”</p><h3>Refactoring the old backend with modern technologies</h3><p>Team Autopsy is home to six developers: <a href="https://www.linkedin.com/in/sergey-susikov-49589b56/">Sergey</a>, <a href="https://www.linkedin.com/in/dmitry-kulikov/">Dmitry</a>, <a href="https://www.linkedin.com/in/dalibor91/">Dalibor</a>, <a href="https://www.linkedin.com/in/lukyanenko/">Andrey</a>, <a href="https://www.linkedin.com/in/janschupke/">Jan</a>, and <a href="https://www.linkedin.com/in/laurikovanen/">Lauri</a> are all experienced full stack engineers. They’re refactoring the old PHP backend with TypeScript and NestJS, and the old Angular frontend with React. The team works closely together with their product manager Martti, collaborating on projects and avoiding lonely work. Autopsy is also looking for a new team member: <a href="https://www.smartly.io/open-positions/a0c2e476-b834-4c1a-9dd0-d92cc51384fb?hsLang=en">a backend/fullstack engineer</a>, who is self-driven and excited to turn customer feedback into well-functioning solutions.</p><p>In six month’s time, team Autopsy hopes to be finished with the A/B testing project and planning its roadmap ahead. “It’s a nice place to be in: working on something new and fundamentally different, but at the same time knowing you won’t be married to that project indefinitely,” Lauri says. “It’s rewarding to be able to define a new direction for the team and the product we’re working with”.</p><p>Learn more about <a href="https://www.smartly.io/careers/developers">how developers work at Smartly.io</a>.</p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-development-teams-autopsy"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10410a794a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-development-teams-autopsy-a10410a794a4">Meet our Development Teams: Autopsy</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Our Development Teams: Value for Life]]></title>
            <link>https://medium.com/smartly-io/meet-our-development-teams-value-for-life-ff63ba5aa1da?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff63ba5aa1da</guid>
            <category><![CDATA[data-warehousing]]></category>
            <category><![CDATA[snowflake-computing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[data-architecture]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 08:37:13 GMT</pubDate>
            <atom:updated>2019-11-04T15:14:00.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xllQVP-bFsaSlnSsA9xTjg.jpeg" /></figure><p>Team Value for Life is on a mission to enable smart business decisions based on data. They are different from other development teams at Smartly.io because their direct customers are not our app users but other Smartlies. “We collect, warehouse, and refine data to support business intelligence, invoicing, sales operations, and product management,” Sampo, the team lead for VfL, explains. “We’re building a foundation for scaling the company by improving and expanding the underlying data architecture.”</p><h4>Data warehousing and a new invoicing service</h4><p>At present, the team has two bigger projects in its hands: data warehouse development and a Ruby on Rails project that aims to encapsulate all invoicing-related architecture into one service nicknamed Pennybags. “It’s not just refactoring,” Sampo says. “A big part of the project is to develop a new invoicing logic that empowers the future of our business, where we offer multiple product and service combinations on a variety of advertising platforms.”</p><p>Data warehouse development is another intriguing undertaking by team VfL. “Essentially, we’re moving a terabyte’s worth of data into a new database,” Sampo explains. “The old PostgreSQL database isn’t the ideal solution for analyzing big data, and we hope to fix that with the new Snowflake data warehouse.” Being able to analyze the large volumes of data our app generates is a key prerequisite for being able to produce market insights and productize optimization strategies for our users.</p><p>“One of our biggest challenges is to restructure the entire data pipeline,” Sampo says. “Before we turn to technical implementation, we need to be able to visualize what data is collected, how it is collected from a variety of endpoints, and how it is managed so that it is optimal for data analysis.” To accomplish their goal, VfL works closely with multiple teams around the company to build an understanding of how the data warehouse and pipeline should be built so that they serve the company in the best possible way.</p><h4>A team with a diverse skill set</h4><p>VfL is a unique team also because it houses professionals with a diverse set of expertise areas: <a href="https://www.linkedin.com/in/sampoverkasalo/">Sampo</a>, <a href="https://www.linkedin.com/in/beyondcompute/">Evgeny</a>, and <a href="https://www.linkedin.com/in/mikamarttila/">Mika</a> make up the developer subteam, each of them with six to 15 years of experience in software development, a backend focus and fluency in databases. They work closely together with their product manager <a href="https://www.linkedin.com/in/tiiatirkkonen/">Tiia</a>, business intelligence analysts German, Tuomas, Tomi, and Pekka, as well as business system specialist Katri. “We prepare the data in a way that it can easily be processed and refined by others,” Sampo explains. “For example, the BI team builds dashboards on top of our data warehouse, which in turn helps other Smartlies around the organization make decisions in a data-driven way.”</p><p>The team is looking for <a href="https://www.smartly.io/open-positions/39f3a820-f7a0-470f-8661-d108a335a0f7">a new member</a> to help with bringing Pennybags, the new invoicing service, towards its vision of encapsulating invoicing related logic and enabling new types of offerings. “Now that we have an opportunity to re-do the service, we want to double down on details and create a precise and sustainable system that’ll serve us well as the company scales,” Sampo says.</p><p>Learn more about how developers work at Smartly.io at <a href="https://www.smartly.io/careers/developers">smartly.io/careers/developers</a>.</p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-development-teams-value-for-life"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff63ba5aa1da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-development-teams-value-for-life-ff63ba5aa1da">Meet Our Development Teams: Value for Life</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Our Development Teams: Senators]]></title>
            <link>https://medium.com/smartly-io/meet-our-development-teams-senators-5ec00b13c08?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ec00b13c08</guid>
            <category><![CDATA[openapi-specification]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 06:36:02 GMT</pubDate>
            <atom:updated>2019-09-25T06:36:02.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uxRGMiXGtzHisMrfBj9nuA.jpeg" /></figure><p>Team Senators owns one of the most business-critical areas of the Smartly.io app-the one that creates the Facebook and Instagram ads you see in your social media feed. Theirs is the responsible job of keeping the functionality live at all times, as well as making the ad creation experience as hassle-free and intuitive as possible for the app users.</p><p>“If our system goes down, our customers can’t publish their ads. And if they don’t get their ads out there, they don’t spend their budget, which in turn means that we don’t make any money,” says <strong>Valtteri</strong>, the Senators’ team lead. “This means that a lot depends on us doing our job well, and building a resilient system that can handle large volumes of data.”</p><h3>Clear-cut focus and lots of responsibility</h3><p>Senators is a new team with five experienced developers: <strong>Sakari</strong>, <strong>Juha</strong>, <strong>Pablo</strong>, <strong>Andre</strong>, and Valtteri. They work intimately together, tackling projects one by one as a team. They strive to maintain a crystal clear focus by prioritizing heavily and accepting only a few projects to their quarterly roadmap.</p><p>“Senators was born when a larger twelve-person development team was split into two smaller autonomous teams. The new team structure allows us to focus on a more clear-cut, smaller area of the app. Being more focused keeps the team’s workload more manageable and results in higher developer happiness,” Valtteri explains. “There’s still a lot of work, but now it’s easier to see how your work contributes to the team’s goals in the big picture.”</p><p>In a small team, all developers need to take on a ton of responsibility, especially as Senators is working on a challenging frontend refactoring process. “Rewrites are always risky and require meticulous planning so that you don’t break anything or mess up what the other teams are working on,” Valtteri says. “But at the same time, the team is hyped up about the opportunity to code a new frontend from scratch. Especially as we can really take time to do it, and pay the needed attention to clean code and building a resilient and sustainable system using new technologies.”</p><h3>Modern technologies &amp; tricky rewrites</h3><p>The team works with technologies like React, Redux, TypeScript, PostgreSQL, Redis, and Kubernetes. They specify their APIs with OpenAPI, and Sakari even wrote a <a href="https://github.com/smartlyio/oats">library</a> that generates Typescript clients and servers from an OpenAPI spec to make their life easier. “As we’re working on refactoring the old monolith, we also need to know our way around PHP,” Valtteri adds. “But with the rewrite, we’re doing away with the legacy PHP, which is bound to make things more convenient.”</p><p>Senators also operates a microservice, a creative service called Goya that handles the ad creation process on the backend. “Moving from a monolithic structure to separate services allows us to narrow our focus, implement code faster, and spend less time coordinating with other development teams,” Valtteri explains. “When areas of ownership and overlap are more pronounced, we’re in a better place to make other teams’ work easier and faster where our work intertwines.”</p><p>As their first task, Senators needs to tackle an oncoming migration from one version of Facebook’s API to the next. “It perhaps doesn’t sound like the most exciting thing in the world, but API migrations can produce real brain teasers. This time, for example, Facebook made some major changes in their API, like splitting one API endpoint into three new ones. We need to figure out how we can accommodate those changes in our own app, without mixing things up for our users,” Valtteri explains.</p><p>Next, Valtteri and his team turn to the frontend rewrite. “It’s another intriguing challenge. There are many variables at play when you’re making an ad, and we need to simplify this complex process for our users as much as possible. It’s also going to be interesting to plan the UI in a way that it serves both power users and less advanced advertisers.”</p><p>Learn more about how developers work at Smartly.io at <a href="https://www.smartly.io/careers/developers">smartly.io/careers/developers</a>.</p><p><em>Originally published at </em><a href="https://www.smartly.io/blog/meet-our-dev-teams-senators"><em>https://www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ec00b13c08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/meet-our-development-teams-senators-5ec00b13c08">Meet Our Development Teams: Senators</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Experience Comes before Employer Branding]]></title>
            <link>https://medium.com/@siirihakulinen/employee-experience-comes-before-employer-branding-4bc488b2abb6?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bc488b2abb6</guid>
            <category><![CDATA[employer-branding]]></category>
            <category><![CDATA[recruitment-marketing]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 07:51:45 GMT</pubDate>
            <atom:updated>2019-03-20T13:07:28.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w3BOuRE4xxTr_9aX8dynGQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/JCWHWjP8u2w?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Juli Moreira</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We’re at war for talent. Companies are challenged and crippled by their inability to attract and hold on to brilliant employees.</p><p>As our world becomes more digitalized, the pain is worst in companies that seek software developers and other technically capable employees. In Finland, #codershortage has made national news, as <a href="https://www.hs.fi/talous/art-2000005225501.html">the local programmer workforce is 9,000 short</a> and the situation grows worse by the year. Globally, the “<a href="https://business.linkedin.com/talent-solutions/blog/trends-and-research/2018/industries-biggest-talent-shortages-2030">talent shortage could reach 85.2 million people by 2030 — costing companies trillions of dollars in lost economic opportunity</a>”.</p><p>What this means is that brilliantly talented people, whom companies need to build and sell their products and services, keep their customers happy, and bring in revenues, are courted from all directions.</p><h3>Employer branding is needed more than ever before</h3><p>Anyone who knows anything about the current talent market knows that the people you want to hire aren’t usually looking for a job. Most likely, they’re happily employed somewhere else, enjoying a top-of-market salary, great perks, and an environment where they get to grow and learn. They have little to no interest in eyeing other opportunities, let alone pouring time and energy into crafting a job application and going through a tedious recruitment process to prove themselves to you.</p><p>Instead of trying to persuade passive applicants to “apply now!”, you should make sure that when they grow tired of their old job, yearn for new challenges, or get a new boss they don’t like, you’ll be top of mind.</p><p>Employer branding is hardly ever direct-response and therefore does little to alleviate the acute talent shortage. But when wielded correctly, it can be a powerful tool for attracting and engaging brilliant talent in the long-term, which, essentially, is what any company in the current talent market should be striving for.</p><p>But before you jump on a witty employer branding campaign, hear me out.</p><p>Employer branding has two target audiences: the internal and the external. Your external audience is your leads, applicants, candidates, and all the people who aren’t there yet but you wish they’d be. Your internal audience is the people you’ve already hired — your employees.</p><h3>Your internal audience should outweigh your external audience ten to one</h3><p><a href="https://medium.com/@andywhitlock/why-you-should-build-you-brand-from-the-inside-out-d1b9224b5334">Andy Whitlock</a> writes about the importance of building the brand of a company from inside out. In the same way, your employer brand should be built inside-out, not outside-in.</p><p><strong><em>Successful employer branding starts with making your company the best place to work for your employees. Period.</em></strong></p><p>When you draft your employer brand strategy, don’t set out to sketch marketing communications or advertising campaigns. Start by making the employee experience stellar for the people who already work for you. If you succeed, you might not need to invest in expensive marketing campaigns afterward. Your people might just do your promoting for you.</p><h3>How we use people engagement surveys to improve the employee experience at Smartly.io</h3><p>At Smartly.io, we roll out people engagement surveys twice a year to find out how Smartlies feel about their workplace. We hear the good, bad and the ugly about how we’re succeeding and failing as an employer. This information, topped with employee exit interviews and Glassdoor reviews, are some of the most critical indicators of the state of our employee experience, and therefore of our employer brand. We should use this data to improve as an employer — nurturing the good and fixing the bad.</p><p>Last spring, our people engagement survey results showed that Smartlies were very happy with many aspects of their employee experience, but that we had loads to improve in feedback and recognition. We weren’t exactly living up to our ideal feedback culture (inspired by <a href="https://firstround.com/review/radical-candor-the-surprising-secret-to-being-a-good-boss/">Radical Candor</a>) nor did our people feel that they were getting enough credit for a job well done.</p><p>We set out to fix these shortcomings in our employee experience and turned them into the number one 6-month strategic goal for the whole company. The fixes included rolling out feedback training for all Smartlies, refreshing our compensation model for increased fairness, aligning benefits and perks globally, and developing an impact leveling system to provide more clarity in how Smartlies can influence their career progression and compensation.</p><p>Last fall, the people engagement survey showed improved results in feedback and recognition, but new issues came up, too. Many of these issues were linked to giving more concrete support and tools to our team leads for their work and responsibilities as managers. The survey results also indicated that Smartlies would like to see the company amplifying its social impact.</p><p>We acted on the feedback and raised team lead training among the key strategic initiatives for the whole company. We’re now putting together leadership principles, a team lead peer group, a handbook, and a training programme, with the first training sessions starting this month. Our social impact project is also underway, with the first volunteering opportunity coming later this spring.</p><h3>Only when you’re offering a great place to work can you start promoting it</h3><p>These internal improvement projects are some of the most important employer branding work we’ll ever do, because spin-doctoring doesn’t work. If we hoped to lure employees in by highlighting the good parts and fading out the less flattering stuff, sooner or later, we’d end up in a lose-lose situation. We’d lose the employee, and the employee would lose their trust and taste in us as an employer. The latter would hurt us even more than the former because bad news tends to spread fast.</p><p><strong><em>You can’t polish poop. Or maybe you can, but it’ll still be poop. Employers really need to have their home base in check before it makes any sense to promote it.</em></strong></p><p>It’s tempting to turn to easy solutions in internal employer branding: adding office amenities and cosmetic perks. Here Maslow’s good old hierarchy of needs strikes again. Your cold brew tap and office happy hours don’t help much if your people stress about their healthcare, if they can’t see how they can develop their career at your company, or if they feel your leadership culture is broken. So, focus on the most impactful things, and build from there.</p><p>Sure, internal employer branding is iterative, and it takes time, and sometimes you might need results faster. Building your employer brand from inside out doesn’t mean you should stay inside. While you work on your weaknesses, make sure you make noise about the things you already do well.</p><p>At Smartly.io, our employer branding relies heavily on our <a href="https://www.smartly.io/culturehandbook">company culture</a>, because we know (from people engagement survey results, for example) that Smartlies are generally very happy with our culture and that it plays a huge role in why they choose us and stay with us. It’s totally cool to write blog posts and devise marketing campaigns around our culture, as long as we take care to constantly improve it as well as work on fixing the things Smartlies are less content with to create an even better workplace for our people.</p><p>I love talking about employer branding. If this post raised any thoughts, please let me know and let’s have a talk!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bc488b2abb6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Our CTO Spends 50% of His Time on the Road]]></title>
            <link>https://medium.com/smartly-io/why-our-cto-spends-50-of-his-time-on-the-road-ad361cad8be7?source=rss-c8dd5e71c3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad361cad8be7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Siiri Hakulinen]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 07:05:29 GMT</pubDate>
            <atom:updated>2018-08-07T08:27:50.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eD7MWa3h3Hc6-5UKLoIkIQ.jpeg" /></figure><p>Smartly.io’s Founder and CTO Tuomo Riekki, who was recently included in <a href="https://www.forbes.com/30-under-30-europe/2018/media-marketing/#7ea5a6931793">Forbes 30 under 30 Europe</a>, spends most of his time in the front line of Smartly.io’s business, traveling to meet customers and prototyping new product initiatives to solve their pain points. In this blog post, he explains why being close to customers is both <a href="https://www.smartly.io/culturehandbook?utm_source=techblog&amp;utm_medium=tuomo30under30&amp;utm_campaign=organic-blog-link">a core company value</a> and his favorite part of the job.</p><p>“It’s just common sense that a new startup develops their product in close cooperation with their first customers. Seeing how (and if) customers use your product helps in finding a product-market fit. That’s what my co-founder Kristo and I did when we founded Smartly.io — we weren’t Facebook marketing experts, and our first customers played a huge role in teaching us what they needed,” Tuomo recounts.</p><p>A lot has changed since the early days of Smartly.io, but almost five years later, we still work extremely closely with our customers. Our leadership and engineers talk to customers regularly, and our customer success and sales teams get feedback and ideas from them daily. “Keeping close to customers helps us understand their pain points and bottlenecks, and build a product and service that solves their problems”, Tuomo explains. “Feedback from users continues to adjust our product design and development, and touching base with them often helps us keep a finger on the pulse of the whole industry.”</p><h3>Why customer intimacy is a no-brainer for engineers</h3><p>Tuomo is a self-taught programmer and he has worked with web development since his teens. Now that Smartly.io is an established company with over 170 people in eight offices, Tuomo’s number one priority is to drive new product initiatives by constantly meeting customers, partners, and Smartlies across the globe and discussing their needs, goals and challenges. His role is a mix of a technical salesperson, a product manager, and a product designer, and he gets his kicks out of coding new functionalities during meetings with customers to fix problems and delight them.</p><p>“I love spending time with customers, because that’s where the best ideas come from”, Tuomo says. “One time, I was sitting in a meeting in Berlin and noticed that the customer was copying custom audiences across multiple ad accounts manually, one by one. It looked very tiresome, so I coded a button for sharing audiences between accounts in bulk in the middle of the meeting, and the customer was very pleased.”</p><p>Customers really appreciate the opportunity to sit down with engineers and technical account managers, who can bring deeper product knowledge to the table. That’s why our engineers travel to meet customers across continents, attend sales demos, and do technical support regularly, answering customers’ questions and fixing their problems. Read more about how we do this in <a href="https://www.smartly.io/blog/what-does-being-close-to-customers-mean-to-a-data-scientist?utm_source=techblog&amp;utm_medium=tuomo30under30&amp;utm_campaign=organic-blog-link">this blog post by our Data Scientist Markus</a>.</p><p>Being close to customers is one of Smartly.io’s core values, and we believe it’s a key component in maintaining our product development speed. All Smartly’s significant features are developed in close cooperation with clients. We fly some of our most advanced customers to Helsinki, where they workshop with our engineering teams, demo how they use the tool, and provide valuable feedback to our product development and design teams.</p><h3>How we drive new product initiatives</h3><p>“The majority of new feature ideas kindle in customer meetings”, Tuomo repeats. “We’re serving over 600 online advertisers globally, which means we’re never short of ideas. Figuring out which ideas are the most wanted and how we could solve them through our product requires context which we can only get by spending a lot of time with the users. It’s our job to probe, ask loads of questions and really understand what the customers struggle with and what would make their work ten times easier.”</p><p>“Take the Video Templates feature, for example”, Tuomo says. “We had already built <a href="https://www.smartly.io/blog/excellence-in-innovation-winner?utm_source=techblog&amp;utm_medium=tuomo30under30&amp;utm_campaign=organic-blog-link">Dynamic Image Templates</a>, which allow the user to render up to millions of product images on-demand by pulling product images from a feed and modifying them with an in-app image editor. Image templates are automatically populated with other dynamic content from the feed, like price, discount percentage, brand logo, and so on. Customers loved it and it quickly became one of the best-selling features of our product. Over time, it became evident that our users wanted the same for videos.”</p><p>“After seeing that there’s demand for Video Templates, our product managers and product designers took a systematic approach to pitching an early prototype, testing the solution with a handful of customers, and iterating based on continuous feedback”, Tuomo explains. “We’re now in the process of building the feature, and we strongly believe it’ll become one of the top features that our customers simply love to use.”</p><p><em>Would you like to help us drive new product initiatives? We’re looking for a Product Manager and Product Designers to join our team.</em></p><p><em>Learn more and apply!</em></p><ul><li><a href="https://jobs.lever.co/smartly.io/8a6cf228-2e27-480f-aaf6-3044537c5c72?lever-origin=applied&amp;lever-source%5B%5D=TechBlog-tuomo30under30"><em>Product Designer</em></a></li><li><a href="https://jobs.lever.co/smartly.io/6b5bd47d-fd4d-45c0-bcfd-c00e76629d10?lever-origin=applied&amp;lever-source%5B%5D=TechBlog-tuomo30under30"><em>Product Manager</em></a></li></ul><p><em>Originally published at </em><a href="https://www.smartly.io/blog/why-our-cto-spends-50-of-his-time-on-the-road"><em>www.smartly.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad361cad8be7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartly-io/why-our-cto-spends-50-of-his-time-on-the-road-ad361cad8be7">Why Our CTO Spends 50% of His Time on the Road</a> was originally published in <a href="https://medium.com/smartly-io">Smartly.io Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>