Many Backend Engineers reach a crossroads at some point in their career when thinking about future progression. Some specialise further, some go down the people management route, and others follow the technical leadership track. While equally valued, the three paths carry different kinds of responsibility and impact. Finding the right one for you can make all the difference.That’s exactly what Paulina Overaitė, Staff Engineer, Trust &amp; Safety, did after joining us in 2019. In just 6 years of working here, she progressed from Junior Backend Engineer to a technical leadership role. We sat down with her to find out more about her journey: from finding her feet to winning awards – sometimes as the only woman in the room.<h3>Paulina's career timeline at Vinted</h3>

<h2>The day-to-day life of a Staff Engineer</h2>A self-described mix of the Architect and Right Hand <a href="https://staffeng.com/guides/staff-archetypes/" target="_blank" rel="noopener noreferrer">staff engineer archetypes</a>, Paulina’s daily work involves designing scalable system architecture, mentoring other engineers, helping teams untangle complex technical challenges, and setting the Trust &amp; Safety domain’s technology vision to ensure our platforms are future-proof.To put it simply, think of a sports team. If the Director of Engineering is the General Manager, who is responsible for building the team and setting the overall strategy, the Staff Engineer is more like the Head Coach. They focus on the playbook, technical design, and how everyone actually plays together, working alongside the Lead Engineer, who is like the team captain.Some weeks are heavily focused on deep-dive technical design, while others are almost entirely dominated by organisational alignment. Paulina’s impact comes less from writing code herself and more from empowering others – stepping in only when technical guidance is needed. What matters most is that our teams are set up for success and pulling in the same direction.Another important focus is balancing rapid delivery with long-term architectural integrity. While AI coding assistants have accelerated software development, reviewing code for quality, maintainability, and architectural alignment remains a deeply human, cognitively demanding task. Tied to this is the challenge of finding the right level of involvement. As a Staff Engineer, you are a technical authority, but you must avoid micromanaging every decision, or you’ll create a bottleneck and stifle team growth. The real art is learning how to step back and trust teams to make their own choices, while having the intuition to know exactly when to step in and guide them on critical issues.&nbsp;<h2>Career growth through experimentation</h2>Paulina’s career progression at Vinted hasn’t always been linear. She has experimented with different roles and projects, guided by the realisation that the real "north star" of a career isn’t gained by climbing the career ladder, but by finding the best fit for where you are in life.She explored the people management pathway when she was a Backend Engineer, and became an Engineering Manager for our Engineering Academy participants. But it was while she was covering for a Staff Engineer during their holiday that she realised the technical leadership pathway was a better fit for her skills, passions, and long-term aspirations: &nbsp;

Some Backend Engineers at Vinted choose to go down a specialist path and work on highly-specific, technical challenges. Others, like Paulina, decide to focus on a more holistic view of how our different systems and platforms intertwine – working across teams to solve company-wide problems. Becoming a Staff Engineer wasn’t a dramatic turning point, but a natural progression for someone who felt drawn to engineering projects that lived outside her team’s scope."I wanted to solve systemic issues – things that technically weren't my "direct responsibility" but still caused friction and pain points for us at the end of the day."The biggest shift for Paulina came from the transition from Lead Backend Engineer to Staff Engineer, when all of a sudden, she didn't have a single home team anymore. This meant losing the familiar structure of daily standups, sprint planning, and the typical agile or scrum ceremonies. Without the immediate dopamine hit of closing Jira tasks or shipping features, it can be harder to recognise your immediate impact. Day-to-day coding gets delegated, and other engineers lead specific projects. Paulina discovered that her new role was about multiplying impact through others rather than driving the execution herself.<h2>Tips for career progression</h2>Having gone from Junior Backend Engineer to Staff Engineer in just 6 years, we asked Paulina if she worked on any skills or formed any habits that helped her progress to senior levels. For her, it’s all about "proactive ownership" of both your own career and your team’s success. In practice, this came down to four "rules" she started following early on:1. Be strategic and proactive with your growth. Don't wait until the end of the quarter to think about your impact. Focus on tasks that align with the path you want to pursue – not just when it's time to write your self-evaluation.2. Your team’s success is your success. Don’t chase individual projects at the cost of your team. If your team fails, any individual "star" work doesn't matter. Real seniority is about making sure the whole ship succeeds.3. Keep a record of your work. Not everyone will remember every smart design decision, helpful comment, or project milestone you achieved. Keep a running list of your accomplishments and invest real effort into branding yourself during quarterly and yearly reviews.4. Apply common sense over checklists. Look at what your team actually needs right now and tackle those blockers – whether that means calling out a risky timeline, sharing feedback, or raising your hand to ask for help when a task is slipping. This mentality has also helped Paulina approach promotions. Rather than aggressive negotiations, which don’t come naturally to her, she broaches the topic through transparency – while always aligning her expectations with organisational restraints and business realities.&nbsp;

<h2>Diversity as an organisational superpower</h2>In 2023, Paulina was a mentor for Women Go Tech. In 2024, she won Build Stuff’s prestigious "Woman in Software" award for her visionary leadership at Vinted while enhancing the Trust &amp; Safety domain. Winning the award helped Paulina feel seen and appreciated. Since then, she has made a point of giving others the same kind of genuine, positive recognition to help them move forward.We all carry a mix of what society considers "masculine" and "feminine" qualities. Early in her career, Paulina was often the only woman in the room. At times, she felt like only the more “masculine” parts of her identity were worth sharing, while believing the more “feminine” parts should be kept hidden – glossing over her dance classes and instead bringing up her weekend of snowboarding, for example. Part of this hesitation came from the awareness that, in some working environments, women’s soft skills can be dismissed as “too emotional”, while men displaying the same qualities are more likely to get praised for their emotional intelligence. Joining Vinted gave Paulina the opportunity to do things differently. Challenging the status quo and showing up as your authentic self can be scary, but this authenticity often encourages others around you to do the same. Paulina believes this mindset has been a key part of her success.&nbsp;With AI increasingly handling raw coding tasks, working in tech is no longer just about writing code. The most complex challenges are human and organisational: team structures, communication bottlenecks, and balancing cost versus effectiveness. It requires a mixture of skills that go far beyond just being good at maths or writing syntax. Paulina remembers working with an Agile Coach who had a degree in psychology. Her ability to look at our teams from an outsider's perspective, diagnose communication breakdowns, and figure out why a team was struggling was incredibly impactful.Having career switchers or people with non-traditional backgrounds in the room is a huge superpower for engineering organisations. After all, sometimes it’s incredibly difficult to debug what’s not working when the bug isn't in the code!<h2>Want to be part of Vinted’s long-term technical direction?</h2>Technical leadership at Vinted is grounded in clarity, care, and ambition done right. If you’re ready to align high-level technical vision with business strategy, we could be just the place for you. Explore open <a href="https://careers.vinted.com/jobs?page=1&amp;q=staff&amp;gh_src=fw02s0s2teu" target="_blank" rel="noopener noreferrer">Staff Engineer roles</a> at Vinted.&nbsp;

Paulina-Overaite

From Junior to Staff Engineer: Scaling beyond a single team

At many companies, engineering stays behind a screen. You develop features and maintain systems, but rarely get to see the real-life results of your work.But we do things differently at <a href="https://careers.vinted.com/vintedgo" target="_blank" rel="noopener noreferrer">Vinted Go</a>, a new part of the <a href="https://careers.vinted.com/about-vinted" target="_blank" rel="noopener noreferrer">Vinted Group</a>, dedicated to developing a better approach to shipping. Whether it’s scaling our pick-up and drop-off network or streamlining warehouse logistics, we believe that to build systems for the real world, you need to step into it.That’s why our Engineers spend time in the field, testing products in practice and learning directly from the people who use them. It leads to better decisions, stronger solutions, and work that feels more meaningful. Here, engineering has a physical footprint. The code we write moves parcels, supports drivers and helps shape how millions of people send and receive items.So join us as we sit down with Judita (Web Engineer), Liudas (Backend Engineer), and Viktorija (QA Engineer), to discover how the projects they work on create change you can see.&nbsp;<h2>Testing a UI on the streets of Paris with Judita</h2>For Web Engineer, Judita, working at Vinted Go means bridging the gap between a digital UI and physical parcel lockers. She describes it as “a place you can literally touch your work”, where Engineers aren’t just “pushing code” but building meaningful products shaped by genuine user experiences.

And that connection to reality goes beyond the office. Recently, Judita travelled to Paris for a drive-along with one of our delivery drivers, to understand how the lockers she works on perform under day-to-day operations. She described the experience as eye-opening, saying it provides a vital reality check for Engineers: “As Engineers, we often assume a user will interact with a feature in a specific way, but seeing a human interpret it differently in a real-world environment is invaluable.”Judita notes how it’s one thing to view a feature test in a sandbox environment, but it’s “another thing entirely to watch a driver use a feature you built and see the genuine excitement in their eyes because your work just made their day easier.”Experiencing that first-hand changed how Judita approached her project. It helped her focus on the core driver flow and spot friction points that wouldn’t show up in testing. “After spending two months on the details of a major feature, I’d spent so much time worrying about complex 'edge cases' and fail scenarios that I’d lost sight of the core driver flow…watching a driver use the interface in a busy, high-pressure environment, I saw immediate UI/UX friction points that weren't obvious on a monitor.”For Judita, the most fulfilling part of on-the-ground testing is the immediacy. Instead of taking notes to fix later, you’re solving problems in the moment, alongside the people using the platform.

<h2>Writing the logic behind robotic movement with Liudas</h2>Working at Vinted Go means solving puzzles that don’t stay on a screen. For Backend Engineer, Liudas, that takes shape in the warehouse, where his code directly controls robots and keeps parcels moving through the system at scale. “Moving a single robot in a warehouse is easy in isolation. The complexity comes when we combine operational flows, state management, infrastructure reliability, scale, and people.”That complexity is at the heart of his role. From defining how robots move and what they carry, to keeping systems aligned and machines running reliably, all while giving key stakeholders a clear insight into performance, Liudas’ backend code sits at the centre of a sophisticated physical and digital operation.At this high volume, even small changes can have an immediate effect. A few lines of code can shift how key processes run, with feedback arriving almost as soon as something is released. Witnessing it all in motion brings a different kind of clarity:

For Engineers who thrive on speed, scale, and constant problem-solving, the job is very rewarding: “At Vinted Go, there’s always something new waiting just beyond what we’re currently working on. We’re constantly adjusting, testing, and building new ideas. There’s no chance of getting bored.”<h2>Taking quality assurance international with Viktorija</h2>At Vinted Go, when a product launches in a new market, testing travels with it. Recently, QA Engineer, Viktorija, travelled to New York City to support the US launch of our Parcel Shops. For her, working at Vinted Go means more than testing software from a desk – it’s about seeing how the product performs in “real shops, with real people.”That’s because performing Quality Assurance on a physical-digital solution in a new country introduces more variables than a test environment can account for. You’re not just validating how the system should behave, but how it holds up in day-to-day use.Plus, in a new market, there’s less familiarity with the user base. User behaviour and expectations can differ from those in the markets you’re accustomed to, making preparation even more important. Being on the ground helps close that gap. It adds context you can’t get from your desk and reveals details that only appear in live environments:

And it’s this experience that makes the position so fulfilling to Viktorija: “Once you see with your own eyes how much people are impacted by something you work on every day, the work stops feeling abstract. It becomes something tangible – something that genuinely makes people’s jobs easier.”<h2>Build code you can see in the real world</h2>Across Web, Backend, and Quality Assurance, one thing stays the same at Vinted Go: Engineers stay close to what they build.Whether it’s riding along with delivery drivers in Paris, watching robots move parcels in the warehouse, or launching a product in New York City, the work doesn’t stop at release. It continues in live conditions, with real users.That creates a stronger sense of ownership. On our teams, you’re not just maintaining features behind the scenes; you’re creating tools that power lockers, warehouses, and delivery experiences used by millions of members every day.As Viktorija puts it: “at Vinted Go, there’s never a dull day. We’re constantly working on something new, something bigger, and sometimes on ideas that might have seemed impossible just a year ago – but now we’re implementing them. It’s a great place for engineers who want to see the impact of their work.”So, if you want your code to do more than just render on a screen, Vinted Go might be your next big move.<a href="https://careers.vinted.com/jobs?unit%5B0%5D=Vinted%20Go&amp;page=1&amp;departments%5B0%5D=Engineering&amp;gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">Explore our open Engineering roles</a> and help shape how shipping works in the real world.

vinted go - robots (1).jpg

Inside Engineering at Vinted Go: building beyond the screen

Scale changes everything – not just in systems, but in how we lead. Moving from an Engineering Manager to a Director of Engineering isn’t a simple step up the ladder; it’s a chance to expand your reach and evolve your mindset. It’s the shift from leading teams that deliver key outcomes to enabling entire domains of leaders to guide a platform that connects millions and keeps growing fast. All while driving our mission: making second-hand the first choice worldwide.In this interview,&nbsp;Karolis Žilinskas,&nbsp;Director of Engineering, shares how he made that leap: what inspired him, how he prepared, and the lessons he’s learned about leadership, strategy, and sustainable evolution along the way.<h2>When an idea becomes a leadership journey</h2>The shift to Director didn’t come from chasing titles, but from following an idea that refused to fade. “I had an idea about building an identity platform: how it could work, how it would fit within our organisational design, and how it could strengthen our overall security posture…I began exploring it, talking to people across the company, and shaping how it could become a key enabler for Vinted.”That journey of exploration soon became something bigger than a side project. As the idea evolved, Karolis realised that to make it real, to drive it at a company-wide level, he needed to take on a broader role. Stepping into the Director position became a natural progression, allowing him to turn that vision into reality and bring multiple teams together behind it.<h3>Defining the moment &nbsp;</h3>The recognition that he was ready to lead came gradually. “The realisation came when I started to clearly understand what my manager was doing – not just observing, but imagining how I’d approach things differently and what I’d improve. I began taking on stretch tasks that mirrored those responsibilities to test myself. Once I was comfortable operating at that level and still felt hungry for more, I knew it was time to take the next step.”But readiness was about more than confidence; it required preparation. Karolis invested time in learning from mentors and peers whose leadership styles he admired. The combination of curiosity, feedback, and self-awareness made the transition smoother and helped him enter the Director role with clarity and purpose.<h2>The shift in scope</h2>At Vinted, the role of a Director of Engineering is defined less by control and more by context. “As an Engineering Manager, I focused on my team…their development, focus, and delivery. As a Director, the scale multiplies. My attention goes to the health of an entire domain, collaboration between teams, and whether our processes and practices are setting up everyone for long-term success.” &nbsp;His work now involves shaping how Vinted plans, decides, and executes across engineering as a whole. Instead of optimising locally, he looks at how systems enable others to deliver, learn, and succeed sustainably.<h2>Leadership built on care and clarity</h2>Karolis’s leadership philosophy is straightforward: results matter, but they depend on a healthy, motivated team. He focuses on creating an environment where people are clear on priorities, supported in their work, and confident to make decisions.

<h2>Turning strategy into action</h2>One of Karolis’s proudest achievements reflects how strategic leadership works at Vinted: turning alignment into real results. “The topic of centralised bot management had been discussed many times, but it never quite moved forward. Different domains saw it differently. I worked to align those perspectives…to define the shared problem, the risks, and the opportunity.” &nbsp;What started as a recurring discussion became a company-wide initiative. Karolis and his team secured support to create a dedicated group for managing automation risks, a shift that now strengthens the resilience and scalability of Vinted’s platform. It’s a clear example of how deliberate planning and persistence can turn a difficult problem into meaningful, lasting change.<h2>Challenges worth having</h2>Leading at scale means knowing when to let go of what’s working. That, Karolis admits, is one of the hardest parts. In a rapidly expanding company, systems have to evolve constantly, and what was reliable last year might limit progress the next. It’s a continuous balance between maintaining stability and having the courage to rethink.He leans on collaboration when change feels tough. “What’s helped me most is staying deeply connected to the work that excites me…in my case, security. When you genuinely care about the problem space, the hard parts of leadership become easier to navigate because you’re driven by purpose, not just responsibility.”He’s also quick to point out that being in charge doesn’t mean doing it alone. “At the Director level, you simply can’t do it on your own. I’ve learned to actively lean on my domain leadership team, my Director peers, and senior colleagues. Knowing when to ask for help – and creating a culture where that’s normal – has been one of the biggest enablers of success.”<h2>Empowering others to lead with impact</h2>Mentorship has become a natural part of Karolis’ work. “I bring Engineering Managers into decision-making as early as possible. The best way to learn is to see how complex decisions are made…especially the hard ones. I also try to show that I don’t have all the answers. Transparency builds trust and confidence.”&nbsp;That openness runs deeper than one-to-one guidance. Karolis helped shape peer-learning sessions within the domain leadership group, creating space for managers to discuss the real hurdles and share how they approach them. Together, they often tackle live topics such as balancing priorities or leading through uncertainty, which helps build collective ownership.This investment in others is something Karolis sees as essential for keeping Vinted’s culture strong. “A company scales sustainably only if its leaders keep developing leaders. That’s where the real leverage happens.”<h2>Advice for future Directors</h2>Karolis’s advice for ambitious Engineering Managers is both practical and encouraging. He believes stepping into a Director role is more than a promotion; it’s an opportunity to expand how you make your mark and evolve how you lead.&nbsp;

Balance, he adds, is essential. “Strong support structures, at work and at home, matter more than people think. You can’t lead effectively in isolation. And physical health is just as important; it’s not about pushing harder to do more, but making sure your energy levels can sustain the pace. Consistency and longevity come from looking after both your mind and body.”<h2>Reflection and what’s next</h2>Looking back, Karolis is most proud of how his thinking has evolved. Earlier in his career, he was focused on execution: solving problems directly and keeping delivery moving. Now, he approaches obstacles with a strategic lens, considering how today’s decisions will shape the business years from now.His goal now is simple: keep evolving. “It’s easy to settle once things feel comfortable, but progress for me, like for Vinted…never stops. Every few months, I look for new opportunities that stretch me and the systems I help shape.”<h2>Make your next step count</h2>Leadership at Vinted is grounded in clarity, care, and ambition done right.&nbsp;If you’re ready to level up from managing a team to shaping an organisation&nbsp;– and want to see the difference your work makes for millions of members&nbsp;– this could be the next chapter in your story.Explore open <a href="https://careers.vinted.com/jobs?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog&amp;departments%5B0%5D=Engineering&amp;page=1&amp;q=Manager" target="_blank" rel="noopener noreferrer">Engineering Manager roles</a>.

3110 Vinted9886 (1).jpg

The journey from Engineering Manager to Director: Leading at Vinted

Taking on an Engineering Manager role isn’t about leaving coding behind, it’s about building on what you already know and discovering a new way to make an impact. Vinted is a great place to do that. With millions of members across more than 20 markets, it’s where technology meets scale and purpose. Many of our leaders started exactly where you might be now: writing backend code, solving technical puzzles, and wondering what comes next.Two of them, Audronė Šopauskaitė and Rugilė Lukoševičiūtė, made that move into management after finding a new kind of problem‑solving – helping people and teams grow. In this post, they share how their journey developed, what shaped them most, and the mindset that drove their success.<h2>Starting out</h2>Rugilė and Audronė started their careers outside tech, but curiosity led them into engineering. For Rugilė, it began in civil engineering and architecture. “I worked as an Architect for four years but realised problem‑solving excited me more than design,” she said. “I began coding in my free time, building small apps to practise. After months of learning, I applied for a Backend Developer role and got hired. That’s how my path in IT began.”Audronė’s journey took a similar turn. After studying history, she planned to become a professor but soon realised that path wasn’t for her. Curious about new challenges, she started learning to code at home and quickly got hooked, describing it as “feeling like solving puzzles all day”. That experimental mindset led her to join a programme that helped people switch careers into tech, which is where her engineering path began.

Working in Backend Engineering at Vinted gave both a strong sense of structure, teamwork, and ownership. “Since engineering and problem‑solving tasks were already my bread and butter, it didn’t seem too far away from being an Engineering Manager!”<h2>Taking the leap&nbsp;</h2>For Rugilė, the move into management came from a desire to work more closely with people. But stepping up to lead the same team she once worked in wasn’t easy. “The biggest adjustment was gaining trust,” she adds. “It’s strange at first when you go from teammate to manager.” Over time, she also learned how to find a better rhythm – something that now helps her lead with more confidence and balance.Audronė’s transition unfolded gradually. She describes the main obstacle as shifting her sense of progress. “I had to move from the joy of coding to making sure projects run smoothly,” she explains. “At first it felt like I was doing nothing, just talking, but eventually I saw my contribution through the team’s success.”<h2>What Engineering Managers do at Vinted</h2>At Vinted, Engineering Managers balance human leadership and technical understanding, keeping projects aligned, supporting progress, and connecting technical context to wider company goals.“We do an important job: &nbsp;translating technical decisions into business language and vice versa, shaping our teams’ vision and supporting people’s development and well‑being.” - Rugilė “The biggest difference at Vinted,” she adds, “is that we don’t expect Engineering Managers to have been programmers. What matters is interest in technology and the ability to make informed decisions. They are both a technical partner and a people lead.”

Roles differ across teams, and that’s by design. “The shape of the job shifts to fit each opportunity… In one team, I focused on long‑term goals; in another, on communication and dependencies.” - Rugilė. Her current mission centres on Trust and Safety. “We earn members’ trust through fair and transparent restrictions. We remove potentially harmful content while keeping processes open and accountable.”<h2>Challenges that shape growth</h2>For Audronė, the biggest change was shifting how she approached technical decisions. Having been a Backend Engineer throughout her career, it was an adjustment to move into a more advisory role rather than being the one making or executing those decisions. “A lot of Engineering Managers struggle with this, and I was no exception… but I got in the swing of things pretty quickly.”For Rugilė, a major hurdle was managing her calendar – moving from one meeting a day to a schedule packed with them was a big difference. It took time to find space for everything, balance work with personal life, and make room for meaningful focus.They both agree that leadership broadens your perspective, from building trust to changing how you make decisions and manage your time; the learning never stops.

Tips for backend engineers aiming for leadership

<h2>Ready to lead at Vinted?</h2>Engineering Managers at Vinted don't just lead teams, they connect technical depth with human insight. Across Vinted’s Marketplace and our new payments and shipping companies, Vinted Go, and Vinted Pay, they shape how millions experience second-hand fashion online. &nbsp;If you're driven by growth, wondering about leadership, and ready to support others while still staying close to the tech, this could be your next opportunity.See our open <a href="https://careers.vinted.com/jobs?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog&amp;departments%5B0%5D=Engineering&amp;page=1&amp;q=Manager" target="_blank" rel="noopener noreferrer">Engineering Manager roles</a>

Vinted20240418_48289_1.jpg

Becoming an Engineering Manager: A Backend Engineer's Guide at Vinted

Millions of people rely on Vinted every day. Behind that scale is a platform built to handle massive amounts of data and constant change – powered by the engineers who keep it all running smoothly. Our Engineering Managers (EMs) lead those teams. They connect people, shape ideas into products and keep the technology strong as we expand to more than 20 markets.We spoke with 3 Engineering Managers from across the Vinted Group about what the role really involves, how it differs between departments, and what they've learned about leading ambitious engineering work. Audronė Šopauskaitė, Rugilė Lukoševičiūtė, and Karolis Žilinskas each have different stories that show how technical skill and genuine care come together to build something that truly evolves with the company, and why Vinted is a place where talented engineers can become exceptional leaders.<h2>What being an Engineering Manager means at Vinted</h2>Some managers have a full Engineering, Product, Design &amp; Analytics (EPDA) team, but Audronė's is all Backend Engineers. Keeping close to the tech and working with a very technical team keeps her sharp.&nbsp;

There’s no single way to be an EM here. The details change from team to team, but the goal stays the same: help great engineers accomplish their potential and keep scalable systems moving forward.

Across the Vinted Group, managers spend less time in meetings about processes and more time helping people perform at a high level. They connect dots across product, delivery, and design, fostering real autonomy among their groups. It’s a role that mixes engineering context with leadership craft, and for ambitious engineers, it’s a chance to shape how millions experience the platform every day.

The skills that make a difference – what our team thinks

Good leadership at Vinted takes many forms, but the biggest misconception? That you need to be the strongest coder, or the only expert in the room. Many think that as an Engineering Manager, you’re the one making technical decisions that the team later has to implement, but that's not true! As an Engineering Manager, you enable others to own and deliver the tasks, making it more about the group, not just your own skills.<h2>Meeting new challenges, finding your stride</h2>Taking on leadership brings fresh complexity – different concerns, new problem spaces, and the challenge of defining success through others' progress. But here’s a little secret our Engineering Managers shared: When you're new to it, you might feel you have to own every issue. In reality, you rarely face obstacles alone. Peer support and asking for advice make a big difference.Rugilė had the challenge of joining a group that was still finding its footing. At first, there were no clear ownership boundaries, which made things a bit uncertain, but then, through workshops, mapping responsibilities, and improving shared knowledge, real structure was built. The team became more aligned, and the results showed.

<h2>Building a positive team culture</h2>Culture can make or break a team. One simple rule guides many of our leaders: "Would I want to return as an individual contributor to this department? If not, it's time to reflect and fix what's missing." &nbsp;A meaningful, lasting culture is created when leaders lead by example. These Engineering Managers agree that Vinted treats them as partners, not layers of management. Everyone has a voice in shaping how things get done. When trust and communication flow openly, quality follows naturally.Encouraging feedback, experimenting boldly, and celebrating learning wins – big or small – create a space where people can grow together.<h2>Advice for the next generation of Engineering Managers</h2>

<h2>Ready to lead at Vinted?</h2>Engineering Managers here have a real stake in the future of second-hand. If you want to combine technical expertise, leadership, and meaningful impact on a product used by millions, Vinted offers a place to shape your own path. Bring your ideas, growth mindset, and curiosity – we'll back you to take the next step.Explore open <a href="https://careers.vinted.com/jobs?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog&amp;departments%5B0%5D=Engineering&amp;page=1" target="_blank" rel="noopener noreferrer">Engineering roles -&gt;</a>

Vinted20240619_14298.jpg

Life as an Engineering Manager at Vinted

<a href="https://careers.vinted.com/vintedpay?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">Vinted Pay</a> is a big step for our community with an ambitious mission: building an in-house payment platform that makes buying and selling across borders feel even easier, safer, and more supported. We approach this as a new part of Vinted – a chance to shape something important from the ground up, with the backing of a team that believes in moving fast but getting things right.Our upcoming payment system not only connects buyers and sellers, but does it with stability, speed, and the ability to adapt fast as we grow – qualities at the heart of Vinted engineering. So, join us as we explore how we scale testing at Vinted Pay and what it really takes to deliver reliability for millions with the help of our Lead Test Automation Engineer.

<h2>Solving technical puzzles at scale</h2>From the start, Vinted Pay has meant taking on fresh challenges. We needed to deliver all the payment features our members use – like card payments, Vinted Balance withdrawals, and verification – while also preparing to migrate millions of members from our previous providers to the new platform. From there, our focus turned to scaling even further: supporting additional users, introducing multiple currencies, and handling large transaction volumes, all without any disruption to the Vinted experience.For this, "just running the usual tests" wasn't enough. Each step raised new questions: Would this experience scale for everyone who uses Vinted? Would it hold up under pressure? Could our systems recover quickly if something unexpected happened? To answer these, we developed a layered approach using API contract test automation, chaos and performance testing. More on this next!<h2>A team effort, every step of the way</h2>At Vinted Pay, testing is a team sport. Our architecture is built around microservices – so we work closely with SRE, Security, Backend, and Frontend Engineers to ensure everything integrates seamlessly and performs as it should. The frameworks and tools we create often reach far beyond their original scope, supporting more engineering teams than we anticipated, which means more ownership and faster feedback for everyone involved.

Teams collaborate closely – coordinating releases across services, building shared tools, and contributing ideas to sharpen our methods. When we're working on something unfamiliar or tricky, support from other engineers means there's usually someone who's seen a similar challenge before – or is keen to help find a fresh solution.<h2>Learning as we build</h2>Testing at scale means we learn as we go – spotting potential bottlenecks early, making more confident decisions, and building resilience into every part of the process.Sometimes our work brings unexpected insights: we've used our test results to choose tools, compare programming languages, and refine how we work with data. The main thing that keeps coming up is simple: don't just assume something will work. Take the time to check and use the results to improve. At Vinted, we don't rely on assumptions; we build on evidence.<h2>What you'll find at Vinted Pay</h2>If you're looking for an environment that values hands-on technical growth, open problem-solving, and building something meaningful for our community, Vinted Pay could be the place for you. Here, you'll work with tools like Ruby, JavaScript, TypeScript, k6, Chaos Toolkit, CI/CD pipelines, GO, Kubernetes, AWS, Elasticsearch, Temporal, Grafana, Kibana, Datadog, Clean-Swift, Kotlin, Appium, ES6+, SCSS, HTML5, Playwright, and Postman – with the room to shape our engineering approach alongside skilled colleagues, all while making an impact beyond the code.<h3>Your next step?</h3>Vinted Pay is growing, and so are the possibilities. We're still early in the journey, but every challenge brings us closer to a payments system that’s ready for the future of second-hand. Want to help us build it? We'd be glad to <a href="https://careers.vinted.com/jobs?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">hear from you.</a>

IMG_4546.JPG

Scaling Testing at Vinted Pay: How we Build Reliability for Millions

At Vinted, behind every seamless transaction, there's a team of Site Reliability Engineers (SREs) keeping everything running smoothly for millions of members in over 20+ markets. By building, scaling and securing the infrastructure behind our pre-loved marketplace, they ensure Vinted stays reliable and ready for our members to discover their next great find. From orchestrating deployments to solving unique technical challenges, SREs play a key role in our platform's success.In this post, you'll get a glimpse into SRE at Vinted – explore our tech, see how we solve problems at scale, and find out what it's like to be part of the team.<h2>What SRE Means at Vinted</h2>SRE at Vinted isn't just about keeping the lights on or maintaining servers. Here, it's about innovation – creating scalable solutions and giving developers what they need to deliver quickly, confidently and securely. We go beyond off-the-shelf systems, often designing and operating our own tools and infrastructure in our data centres, which means our SREs are at the core of productivity and the experience our members enjoy.Vinted’s Site Reliability Engineers shape their own path. You’ll work across a range of challenges – from coding and automation to refining infrastructure and resolving complex issues – often all in the same week. Our teams’ mission is to offer a truly reliable platform that can scale with our community, always allowing room for innovation and backed by a supportive team.

If you love working at the cutting edge – this is the place for you.&nbsp;

Our technology toolkit

We run most of our infrastructure in 3 on-premise data centers with more than 7,000 physical servers – a scale where usual approaches don’t apply – giving you the chance to solve unique challenges, boost performance, and bring innovations to life that you won’t find anywhere else.<h3>Meeting complexity with creativity &nbsp;</h3>Not every problem has a standard solution. At Vinted, SREs take on large-scale engineering challenges – designing and implementing innovative solutions for complex systems at scale. Whether it’s optimising Kubernetes clusters running up to 90,000 CPU cores, or running Redis at a scale where you have to get inventive, for each of our SRE teams, creative problem-solving is central to the role.Some days, that means troubleshooting elusive bugs that turn out to be buried deep in the Linux kernel. Other times, it’s reimagining how we deploy infrastructure or developing custom tools to route millions of members’ traffic efficiently. Our goal is always the same: reliability, performance, and creating a seamless experience for both our members and our developers.<h3>A day in the life of a Vinted SRE</h3>Collaboration is the name of the game. SREs at Vinted bridge the gap between infrastructure, product development, and support – partnering with everyone from backend and data engineers to product managers and other SRE teams. On any given day, this might mean:<ul><li>Writing and deploying code that supports real Vinted users.</li><li>Helping teams adopt new best practices.</li><li>Automating repetitive work so developers can focus on new features.</li><li>Debugging a critical incident and finding solutions that keep Vinted running smoothly.</li><li>Building, benchmarking, and deploying next-gen platform improvements.</li></ul>

<h3>On-call with confidence</h3>On-call at Vinted is designed to be sustainable and fair. Rotations are predictable and typically last a week (depending on the team). Most issues can be handled during the day, and clear runbooks make even the trickiest alerts straightforward for any engineer to follow. Each team member takes their turn, with plenty of support from colleagues whenever it’s needed. Our monitoring and alerting are continuously improved to streamline the on-call experience and ensure SREs always feel supported when incidents arise.<h3>What sets our team culture apart</h3>Walk into any SRE meeting – or hop on Slack – and you’ll spot a few things: trust, support, and a genuine passion for experimentation. Teams are invested in elevating each other, freely sharing what they know, and helping colleagues pick up new skills. We’ve cultivated a feedback-rich, blame-free environment, where learning from every experience is not just accepted, but encouraged.There’s a deep respect for personal growth – engineers are supported to explore projects, attend conferences, and share ideas with the team. Whether you’ve recently joined the industry or you’re a seasoned expert, there’s always space to ask questions, contribute, and develop your craft.

There’s no single background or ideal checklist that defines our teams – our SREs come from all sorts of paths. But there are some things that unite us:

What makes a great SRE?

And don’t worry – nobody expects you to have all the answers on day one. If you’re keen to learn and ready to ask questions, you’ll find your home here.<h3>Ready to join us?</h3>If you want to work where your code, ideas, and curiosity can help millions shop (and live) a little more sustainably, we'd love to hear from you. Explore our current SRE opportunities and take the first step toward your next adventure at Vinted –&nbsp;<a href="https://careers.vinted.com/jobs?page=1&amp;q=Site%20Reliability%20Engineer&amp;gh_src=4dae07a2teu" target="_blank" rel="noopener noreferrer"> see open roles and apply here.</a>

tim_de_vos.jpg

Life as a Site Reliability Engineer at Vinted

At Vinted, our mobile engineers are developing an app used by millions of people across 20+ countries. Whether it’s enabling seamless second-hand shopping or creating intuitive tools to manage listings and deliveries, mobile is at the heart of how members experience Vinted.So what’s it like to work behind the screen of one of Europe’s most-loved apps? To find out, we sat down with two of our mobile engineering leaders: Sam Vesali, iOS Staff Engineer, and Andrius Semionovas, Android Staff Engineer. They shared what makes our mobile domain special, how our teams work, and what it takes to thrive in this environment.<h3>What’s Special About Mobile at Vinted?</h3>Mobile is not a separate lane—it’s a central one. Our mobile engineers are not just implementers. They’re co-creators, collaborating closely with Product Managers, Designers, QAs, and Backend Engineers to build features that solve real-world problems for our members. &nbsp;

Mobile teams contribute to all areas of Vinted’s business, from member experience to logistics. That means working at scale, building for multiple markets and millions of users, and constantly evolving our architecture to stay ahead.We also maintain open communication across platforms. Android and iOS engineers regularly align to ensure feature parity and consistency, while still keeping pace with platform-specific innovations.<h3>Our Tech Stack &amp; How We Work</h3>We maintain a strong engineering culture that focuses on scalable architecture, modular codebases, and cross-platform consistency. Here's how we break it down:

<figure class="table" style="height:100%;width:100%;"><table class="ck-table-resized" style="border-collapse:collapse;" border="1"><colgroup><col style="width:10.46%;"><col style="width:42.1%;"><col style="width:47.44%;"></colgroup><thead><tr><th style="padding:8px;text-align:left;vertical-align:top;">&nbsp;</th><th style="padding:8px;text-align:left;vertical-align:top;">iOS</th><th style="padding:8px;text-align:left;vertical-align:top;">Android</th></tr></thead><tbody><tr><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Language &nbsp;.&nbsp;</td><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Swift</td><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Kotlin (fully migrated since 2018)</td></tr><tr><td style="padding:8px;vertical-align:top;">Architecture &nbsp;.&nbsp;</td><td style="padding:8px;vertical-align:top;">Modular Clean Swift, contract / implementation layering</td><td style="padding:8px;vertical-align:top;">MVVM, modular pluggable system</td></tr><tr><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Tools</td><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Tuist, Fastlane, GitHub Actions, Firebase Crashlytics</td><td style="background-color:#EDF9F9;padding:8px;vertical-align:top;">Gradle, Jenkins, OpenAPI for shared contracts, Jetpack Compose</td></tr><tr><td style="padding:8px;vertical-align:top;">Testing</td><td style="padding:8px;vertical-align:top;">Unit tests, snapshot, and integration tests</td><td style="padding:8px;vertical-align:top;">Unit tests, integration tests, static analysis, A/B testing</td></tr></tbody></table></figure>

These tools and frameworks are just part of the story. Working at Vinted means solving technical challenges at scale—from modularising our architecture while avoiding tight coupling, to gradually adopting modern technologies like SwiftUI and Jetpack Compose. Across both platforms, engineers focus on secure, scalable, and privacy-first solutions that support independent team workflows and meet evolving business needs.<h3>Cross-Platform Collaboration</h3>Consistency matters, especially when millions rely on us daily. Our iOS and Android teams coordinate closely through shared specs, regular syncs, and aligned release strategies. From shared backend APIs to unified feature flags, both platforms deliver updates in tandem, ensuring every member has the same great experience, no matter their device.

<h3>Day-to-Day in Mobile Engineering</h3>A typical day includes stand-ups, cross-team planning sessions, deep focus time for development, and collaborative reviews. Mobile engineers lead discussions on architecture, run experiments, and share feedback across various disciplines. Mentorship and pair programming are encouraged, especially for junior engineers joining through our <a href="https://careers.vinted.com/engineering-academy" target="_blank" rel="noopener noreferrer">Engineering Academy</a>. &nbsp;

The scale is energising. You ship something in the morning and see real-world impact by the evening. However, scaling brings complexity—tight architectural discipline, legacy code migration, and the challenge of meeting diverse market needs across devices and platforms.<h3>Advice for Future Mobile Engineers at Vinted</h3>We value engineers who see beyond their code — think holistically about user experience, technical debt, and collaboration.&nbsp;

From day one, our engineers are trusted and supported. You’ll learn fast, receive regular feedback, and grow into broader responsibilities—whether it’s leading architectural efforts, mentoring others, or shaping product direction. Your own career growth depends on you. The path can lead towards Staff or Principal roles, switching tracks entirely (e.g. from iOS to Backend), or challenging yourself with a technical leadership position! There's plenty of room to evolve.

<h3>Ready to Build Mobile Products Used by Millions?</h3>If you love clean architecture, solving tough problems, and you're excited to make an impact by building high-quality mobile products with a passionate, experienced team—check out our <a href="https://careers.vinted.com/jobs?departments%5B0%5D=Engineering%20Academy&amp;gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">open roles</a> or apply to the <a href="https://careers.vinted.com/engineering-academy" target="_blank" rel="noopener noreferrer">Vinted Engineering Academy</a>.

Iryna Horova.jpg

Engineering at Your Fingertips: Life in Mobile at Vinted

Have you ever wondered how Vinted effectively manages the thousands of items uploaded to our platform? For our Ontologies team, it boils down to one crucial element: collaboration. Join us as we sit down with Product Designer Eidvilė Bagdonaitė and Taxonomists Laura Horan and Charlie Lapin to discover how they leverage their unique areas of expertise to co-create a better member experience for all.<h2>About the Ontologies team</h2>Ontology is all about describing items&nbsp;– from defining the category they fit into to details like their size and the materials they're made from. By exhaustively cataloguing each aspect of an item in our database, the Ontologies team helps Vinted members find&nbsp;exactly what they're looking for.&nbsp;In other words, the Ontologies team ensures items are discoverable throughout the member journey, including the moment a member uploads an item to Vinted and when they use filters to find the items they need while browsing our platform.&nbsp;"We do this by making sure our platform includes the metadata terms that members use to describe these items."&nbsp;Eidvilė Bagdonaitė says.

<h2>The Buyer domain</h2>As part of the Buyer domain, Laura, Charlie, and Eidvilė's work focuses on the initial stages of the buying and selling process. This covers everything from opening the app and listing an item for sale to searching for something to buy. The Buyer domain also includes the stage where members chat about an item or when they make an offer to buy something. The following steps – payment, shipping and feedback – are handled by another branch of the team.<h3>A unique structure</h3>Vinted’s Ontologies team is an Engineering Product team, which means Engineers, Data Analysts, Product Managers, and Product Designers all come together to achieve the same goal.What makes our Ontology team unique at Vinted is that it also includes Taxonomists. As Laura puts it, "Charlie and I were the first taxonomists at Vinted and the first employees with this background and expertise. Our first order of business was to meet with an array of stakeholders across the matching domain to introduce our skillset and ways we might be able to support their work through improved data modelling."As taxonomists working with colleagues from many different fields, the team finds it essential to clarify the language they use so they can keep their communication clear. After all, words that mean one thing to Product Designers may mean something else to Taxonomists.There are many different paths to the role of Taxonomy, including a History, Librarian, Museum Curation or Knowledge Management background. The ideal taxonomist is someone who’s a logical thinker and enjoys creating order from chaos.<h2>How Taxonomy meets Product Design at Vinted</h2>While our taxonomy data model is the backbone of every item on Vinted, having extensive information is only helpful when we can display it to our members. That’s why we've learned it's vital to get Product Design involved as soon as possible, as it's a lot easier to work in tandem before a launch than it is to start the design process after.So, how do these different approaches come together in the Ontology team’s projects? Eidvilė states, "One of the most straightforward ways we collaborate is by including member insights and perspectives into data structure decisions."&nbsp;This can involve user testing or showcasing how different data structure options influence user flow. Whenever a new approach is suggested, the team discusses how it will change the way Vinted members learn about an item and how this could benefit them. "By anchoring our communication around the user perspective, we're able to find common ground and collaborate towards member-centric experiences", Laura Horan says.Furthermore, in some scenarios, to address the needs of sellers on Vinted, we may need to present information in a way that’s relevant to them but would require a different level of granularity to be user-friendly for buyers. As Eidvilė puts it,&nbsp;“This nuanced understanding has empowered me to approach my design process with greater depth and to develop more solutions that meet the diverse needs of various member groups”.Another way the Ontology team collaborates is through the Kanban method. The team uses a virtual Kanban board to keep track of what everyone’s working on and facilitates meetings that foster collaboration and communication. Every day, the team has a 15-minute standup meeting where they update the status of their Kanban board tickets as a team. They also have weekly planning meetings, where they add new items to their Kanban board and host post-launch retrospectives for projects that go live. The Ontology team also uses Slack to discuss work topics and ask questions more freely&nbsp;– sometimes, these can be answered in a simple thread, but the team is always happy to jump on a quick call to explain the details, too. These methods help everyone to stay on the same page.

<h2>Achieving results</h2>Although Taxonomy has some Member-facing results (e.g. creating a new category in our taxonomy "tree"), they tend to fall into the existing Product Design framework. "We're not reinventing the wheel when adding a new subcategory under Jackets or Skirts", Charlie says.But their collaboration truly shines when the Ontology team works on a new concept. Charlie explains: "For example, in our current project we're working on...Taxonomy has a few options to choose from when building a data model, and we would have been stuck, but product design helped us settle on the best choice, and now we're actively working on implementing it for our members!"Sometimes, the taxonomy design options are limited by the current systems or product designs in place. By collaborating with a Product Designer, the Ontology team can identify opportunities for product design improvements, which enables us to create better data models that enhance the member experience. Eidvilė elaborates: "Like Charlie, I've realised that taxonomy and product design go hand-in-hand. When we combine our skills – thinking how to organise information with a solid grasp of how members think and manage information, it can help create solutions that make a difference to the user experience."<h2>Find out more &nbsp;</h2>Are you a logical thinker who excels at bringing order to chaos? Consider joining our Ontology team and collaborating on projects that make a real impact on millions of members. See our open positions <a href="https://careers.vinted.com/jobs?gh_src=4dae07a2teu&amp;utm_source=web&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">here</a>. &nbsp;

Taxonomy

Fostering Collaboration in Engineering Teams: How does taxonomy fit into product development? 

Successfully rebuilding a career from scratch in a completely different field with no formal education or work experience is tough. But Tom Slaytor managed to defy all odds and successfully become a Backend Engineer, despite starting from a very different line of work. Read on to find out more about Tom’s remarkable journey into Vinted via our Engineering Academy, and discover how we at Vinted welcome and support our thriving career changers into our teams.<h2>Meet Tom Slaytor</h2> After working as a professional drummer for several years, followed by a role in sales, Tom Slaytor decided to pursue a new career path that ignited his passion. After developing an interest in engineering by chance, Tom stumbled upon an advert for the Vinted Engineering Academy and decided to apply (spoiler alert – he got the job). But switching careers is never easy – particularly without formal education or training. In his own words, let’s find out how Tom got on with this mammoth transition from professional drummer to Backend Engineer at Vinted, and hear the advice he’d give to people thinking of applying for the Engineering Academy. &nbsp;<h2>It all started with an app</h2> My work experience is pretty varied. After studying music at University, I worked as a professional drummer for several years. Following that, I had a job in sales within the finance sector. A career in engineering was never a consideration. Until one day I had a sudden idea for a training app for drummers. Without having any technical knowledge of engineering, I asked a developer friend to help me create it. As I worked alongside him, I watched him work on the code. I was immediately drawn to it, and found myself quickly getting to grips with what he was doing. The problem-solving element was particularly appealing, but without any experience or training in the field, it never occurred to me that this could be something I could do for myself. &nbsp;

<h2>Time for a change</h2> My job in sales came to an end, but I soon realised I didn’t want to pursue another role in this field. It didn’t spark my interest, so I began looking for another job that I felt more passionate about. I had some time and savings to fall back on, which gave me the opportunity to pursue something else. I took on some freelance work in the meantime, and set myself a deadline to begin applying for jobs, or start getting into a different field within a year. This was the springboard that allowed me to take the idea of programming more seriously, and further develop my skills in that area. As time started running out, the more I realised I really didn’t want to go back into sales. I always liked the idea of working for Vinted – it looked like a good company to join. But I didn’t feel like I had the skills, confidence, or experience to apply for a regular engineering role. I almost jumped out of my seat when I saw the advert for the <a href="https://vc-frontend.nordcode.io/blog/engineering-academy" target="_blank" rel="noopener noreferrer">Engineering Academy</a>, which requires no experience to join. I applied straight away.<h2> Making the cut</h2> The selection process was pretty relaxed. We were asked to share examples of some projects we’ve previously worked on, but there was no strict specification. We just had to showcase the extent of our skills and experience. After that, I had to do some tests and scenario-based questions designed to find out if I would be a good fit within the company’s values and culture, making sure that I had the right soft skills to thrive here. The next stage in the whittling down process was technical. We had to complete a homework assignment in our own time. It was quite challenging, but interesting. I learned a lot from it, and I took it as a good sign that if I found the assignment interesting, I’d find the job interesting as well. Finally, there was the interview with a couple of future team members. It wasn’t as daunting as I expected, and felt like a discussion. Half the questions were centred around my values and how I would react in certain situations or overcome challenges, and the other half were about the technical &nbsp;decisions and choices I made during the homework assignment. &nbsp;

<h2>Finding my way</h2> After successfully making it through the selection process, I was hired. On my very first day at Vinted I learned that there’s a structured onboarding process for academy participants. This came in two parts: technical onboarding, which really focussed on the academy, and general company onboarding. For the first week of technical onboarding, we joined a lot of workshops, and got to grips with the basics. It was all very structured, and we had the opportunity to learn more about how things work, the different workflows, and the programming languages used at Vinted that we were unfamiliar with. After that was Vweek – company onboarding for all new joiners (not just academy participants). We were introduced to different departments and had the opportunity to get to know colleagues in different teams from all over the world. It was a great introduction to what the company is all about – it’s like a big community.<h2> Expectations vs. reality</h2> It sounds cheesy, but working at Vinted is even better that I thought it would be. I’m genuinely excited to wake up every morning and come to the office to work. I was expecting loads of pressure to achieve more or do more in the Academy, but that’s not the case. We push ourselves because we want to. Even with lack of experience, in an unfamiliar system, with languages we’ve never used before, we’re never made to feel not good enough. Many of us haven’t worked in an environment like this before. It’s very comfortable and stress-free. From the people you’re working with, to the projects we’re working on, managers’ expectations, and the way everybody within the company helps each other, the atmosphere is really positive. I’ve quickly bonded with people both inside and outside of the Academy. Everyone is really supportive and accepting of one another. The people and the company culture really make this a fantastic workplace to be in.<h2> Want to join the Engineering Academy? Here’s my advice</h2> Engineering skills are important. But they aren’t the be-all and end-all. To be successful in any company you have to feel like you belong, and that your values align. Stay curious, and keep solving problems. Get ready to tackle new challenges. If that means having to learn a new language, or familiarise yourself with a new paradigm, just dive in and have a go, even if you’re unsure. Take it step-by-step, and eventually you’ll find the answer. If you’re on the fence about applying, I’d say go for it, even if you’re not sure you’re ready. I wasn’t sure I was ready either, but here I am. What’s there to lose? Are you looking for a new career challenge in engineering like Tom? Find out more about the <a href="https://careers.vinted.com/engineering-academy?gh_src=4dae07a2teu&amp;utm_source=blog&amp;utm_medium=blog" target="_blank" rel="noopener noreferrer">Vinted Engineering Academy</a>. &nbsp;

Show all

Vinted stories

Vinted 07 270172 1 (1).jpg

From Drums to Development: Tom’s Journey to Backend Engineering

Engineering environment is a dynamic and constantly evolving domain, and the learning culture is deeply rooted at Vinted. To help you navigate through and thrive in your journey, here’s a list of descriptions and recommendations for you that align with your unique interests and aspirations within the engineering discipline.About Git &amp; GitHub:<ul class="ul1"><li class="li3"><a href="https://eu.udacity.com/course/how-to-use-git-and-github--ud775">How to Use Git and GitHub</a></li><li class="li3"><a href="https://www.udemy.com/course/github-ultimate/">GitHub Ultimate: Master Git and GitHub - Beginner to Expert</a></li><li class="li3"><a href="https://nvie.com/posts/a-successful-git-branching-model/">A successful Git branching model</a></li><li class="li3"><a href="http://engineering.vinted.com/2015/01/02/proper-git/">Proper Git</a></li><li class="li3"><a href="https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control">What is version control?</a></li><li class="li3"><a href="http://engineering-principles.onejl.uk/">Software Engineering principles</a></li></ul>

<h2 class="p1">Backend Engineering</h2>&nbsp;To experiment with Ruby, you can use:<ul class="ul1"><li class="li3"><a href="https://github.com/abdelrahman-hsn/ruby-ebooks/blob/master/Ruby%20on%20Rails%20Tutorial.pdf">20 books or even more (free) on GitHub</a></li><li class="li3"><a href="https://repl.it/languages/ruby">A very good place to start&nbsp;</a></li><li class="li3"><a href="https://guides.rubyonrails.org/getting_started.html">Another great place to start</a>&nbsp;</li></ul>&nbsp;Syntax:<ul class="ul1"><li class="li3"><a href="https://www.youtube.com/watch?v=Dji9ALCgfpM">Video</a> on Ruby Programming and a <a href="https://guides.rubyonrails.org/getting_started.html">Document on getting started with Rails&nbsp;</a></li><li class="li3"><a href="https://www.ruby-lang.org/en/documentation/quickstart/">Ruby in 20 minutes</a></li><li class="li3"><a href="https://medium.com/@noordean/understanding-ruby-blocks-3a45d16891f1">Understanding Ruby Blocks</a> on medium.com<a href="https://medium.com/@noordean/understanding-ruby-blocks-3a45d16891f1">&nbsp;</a></li><li class="li1"><a href="https://ruby-doc.org/core-2.6.1/Enumerable.html">Enumerable</a>, where the most important are - map, each, each_with_object, find, filter, select</li><li class="li3"><a href="http://www.pragtob.info/rails-beginner-cheatsheet/#ruby">Cheatsheet on pragtob.info</a></li></ul>&nbsp;Ruby on Rails (RoR):We recommend not to spend much effort on understanding how to build HTML using RoR. We will use RoR in API only mode, which means we will be building JSON responses only<ul class="ul1"><li class="li3"><a href="https://skillcrush.com/2015/01/29/13-ruby-rails/">What is RoR</a></li><li class="li3"><a href="https://www.sitepoint.com/model-view-controller-mvc-architecture-rails/">MVC in RoR</a></li><li class="li1"><a href="http://www.pragtob.info/rails-beginner-cheatsheet/#rails-folder-structure">RoR folder structure cheat sheet</a> (folder structure, commands)</li><li class="li3"><a href="https://medium.com/@gianpaul.r/ruby-on-rails-generators-and-how-to-undo-them-30a53ac8dfb3">Generators</a></li><li class="li3"><a href="https://guides.rubyonrails.org/v3.2/migrations.html">Migrations</a></li></ul>&nbsp;HTTP:<ul class="ul1"><li class="li3"><a href="https://www.w3schools.com/whatis/whatis_http.asp">What is HTTP</a></li><li class="li3"><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods">Request methods</a></li></ul>&nbsp;RESTful API’s:<ul class="ul1"><li class="li3"><a href="https://www.howtogeek.com/343877/what-is-an-api/">What is an API</a></li><li class="li3"><a href="https://restfulapi.net/">What is REST</a></li><li class="li3"><a href="https://restfulapi.net/resource-naming/">Resource naming guide</a></li><li class="li3"><a href="https://www.w3schools.com/whatis/whatis_json.asp">JSON</a></li><li class="li1">Extra: Ruby on Rails comes with API only option. <a href="https://guides.rubyonrails.org/api_app.html">Official documentation</a></li></ul>&nbsp;SQL:<ul class="ul1"><li class="li3"><a href="https://searchdatamanagement.techtarget.com/definition/relational-database">What is a relational database</a></li><li class="li3"><a href="https://tutorialzine.com/2016/01/learn-sql-in-20-minutes">SQL In 20 minutes</a></li></ul>&nbsp;Testing:<ul class="ul1"><li class="li3"><a href="https://dev.to/milandhar/unit-testing-in-rails-4oke">Unit testing</a></li><li class="li3"><a href="https://culttt.com/2016/07/06/writing-integration-tests-ruby-rails">Integration testing</a></li><li class="li3"><a href="https://medium.com/@piraveenaparalogarajah/what-is-mocking-in-testing-d4b0f2dbe20a">Mocking</a></li><li class="li3"><a href="https://rspec.info/">Introduction to RSpec</a></li><li class="li3"><a href="https://medium.com/@mariacristina.simoes/my-introduction-to-factory-bot-88949467a7e9">Introduction to FactoryBot</a></li><li class="li3"><a href="https://devhints.io/rspec">RSpec cheatsheet</a></li><li class="li3"><a href="https://devhints.io/factory_bot">FactoryBot cheat sheet</a></li></ul>

<h2 class="p1">Web Engineering</h2>&nbsp;<ul class="ul1"><li class="li1">To experiment with React, you can <a href="https://jsfiddle.net/">check out here</a></li><li class="li3"><a href="https://www.codecademy.com/learn/learn-html">HTML5</a></li><li class="li1"><a href="https://www.codecademy.com/learn/learn-css">CSS</a></li><li class="li3"><a href="http://getbem.com/introduction">CSS BEM</a></li><li class="li1"><a href="https://sass-lang.com/guide">SASS - focus on SCSS syntax.</a> Make sure you nail mixins, functions, variables, partials</li><li class="li1"><a href="https://javascript.info/">JavaScript fundamentals</a> - don't spend too much time with things like proxies, Symbols. Focus on fundamentals, such as event loop, as well as ES6 features</li></ul>&nbsp;React:<ul class="ul1"><li class="li1">We prefer functional components with hooks.</li><li class="li1">If you're into <a href="https://egghead.io/courses/the-beginner-s-guide-to-react">video courses</a></li><li class="li1"><a href="https://reactwithhooks.netlify.app/tutorial/tutorial.html">React docs, rewritten with hooks</a>. Take away as much as you can. Make sure you're comfortable with refs, lifecycle, hooks, JSX<a href="https://reactwithhooks.netlify.app/tutorial/tutorial.html">&nbsp;</a></li></ul>&nbsp;Clean code:<ul class="ul1"><li class="li1">We definitely recommend the<a href="https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882"> book by Uncle Bob</a></li><li class="li3"><a href="https://github.com/ryanmcdermott/clean-code-javascript#table-of-contents">JavaScript clean code principles</a></li></ul>&nbsp;Testing:<ul class="ul1"><li class="li3"><a href="https://reactjs.org/community/testing.html">Testing overview</a></li><li class="li1"><a href="https://testing-library.com/docs/react-testing-library/intro/">We use react-testing-library and Jest.</a> Make sure you're able to write basic tests with those technologies</li><li class="li3"><a href="https://kentcdodds.com/blog/common-mistakes-with-react-testing-library">Common Mistakes with Rect Testing Library</a></li><li class="li1">Strive to understand <a href="https://jestjs.io/docs/getting-started">fundamental concepts, </a>such as mocking, spying</li></ul>&nbsp;TypeScript:<ul class="ul1"><li class="li1">Make sure you get the basics and can write React with TypeScript comfortably. TypeScript is quite big, so there's no need to go too deep.</li><li class="li3"><a href="https://github.com/typescript-cheatsheets/react">Cheatsheet</a></li><li class="li1"><a href="https://www.typescriptlang.org/docs/handbook/2/basic-types.html">Official documents</a> and the basics</li></ul>&nbsp;Redux:<ul class="ul1"><li class="li1">It’s not a given that you will use Redux throughout the Engineering Academy, but we use it at Vinted, so the fundamental understanding is important</li><li class="li3"><a href="https://redux.js.org/tutorials/essentials/part-1-overview-concepts">Redux Essentials</a></li></ul>

<h2 class="p1" style="text-align:justify;">Android Engineering</h2>&nbsp;<ul class="ul1"><li class="li3"><a href="https://www.udacity.com/course/kotlin-bootcamp-for-programmers--ud9011">Introduction to Kotlin</a></li><li class="li3"><a href="https://www.udacity.com/course/developing-android-apps-with-kotlin--ud9012">Introduction to Android development with Kotlin</a></li></ul>&nbsp;Dagger:<ul class="ul1"><li class="li1"><a href="https://codingwithmitch.com/courses/dagger22-android/">Dagger2.2+ on Android</a> on CodingWithMitch.com</li><li class="li3"><a href="https://developer.android.com/codelabs/android-dagger?index=..%2F..index#0">Using Dagger in your Android app - Kotlin&nbsp;</a></li></ul>&nbsp;Kotlin coroutines:<ul class="ul1"><li class="li3"><a href="https://codelabs.developers.google.com/codelabs/kotlin-coroutines/#0">Use Kotlin Coroutines in your Android App&nbsp;</a></li></ul>&nbsp;Kotlin StateFlow, SharedFlow and Flow:<ul class="ul1"><li class="li3"><a href="https://developer.android.com/codelabs/advanced-kotlin-coroutines#0">Learn advanced coroutines with Kotlin Flow and LiveData</a></li><li class="li3"><a href="https://developer.android.com/kotlin/flow">Kotlin flows on Android</a></li><li class="li3"><a href="https://developer.android.com/kotlin/flow/stateflow-and-sharedflow">StateFlow and SharedFlow</a></li></ul>&nbsp;Application architecture guidelines:<ul class="ul1"><li class="li3"><a href="https://developer.android.com/jetpack/guide?authuser=1">Guide to app architecture</a></li></ul>&nbsp;Additional Android learnings:<ul class="ul1"><li class="li3"><a href="https://www.udacity.com/course/advanced-android-with-kotlin--ud940">Advanced Android with Kotlin</a></li><li class="li3"><a href="https://developer.android.com/courses/kotlin-android-advanced/toc">Kotlin Andrid Advanced</a></li></ul>&nbsp;If you know most of the above technologies, you can try doing codelabs from this list:<ul class="ul1"><li class="li3"><a href="https://codelabs.developers.google.com/?cat=Android">https://codelabs.developers.google.com/?cat=Android</a></li></ul>&nbsp;If you want more challenges and you know most of the technologies above, you can try to contribute to our open source libraries on GitHub:<ul class="ul1"><li class="li3"><a href="https://github.com/vinted/coper">vinted/preferx&nbsp;</a></li><li class="li3"><a href="https://github.com/vinted/actioncable-client-kotlin">vinted/actioncable-client-kotlin</a></li><li class="li3"><a href="https://github.com/vinted/coper">vinted/coper</a></li></ul>

<h2 class="p1">iOS Engineering</h2>&nbsp;<ul class="ul1"><li class="li3"><a href="https://developer.apple.com/design/human-interface-guidelines/">Human interface guidelines</a></li><li class="li3"><a href="https://developer.apple.com/library/archive/referencelibrary/GettingStarted/DevelopiOSAppsSwift/">Start Developing iOS Apps (Swift)</a></li><li class="li3"><a href="https://www.appcoda.com/iOS-programming-course/">Learn iOS Programming</a></li><li class="li3"><a href="https://www.udemy.com/course/ios-13-app-development-bootcamp/">iOS 13 &amp; Swift 5 - The Complete iOS App Development Bootcamp</a></li><li class="li3"><a href="https://medium.com/ios-os-x-development/ios-architecture-patterns-ecba4c38de52">iOS Architecture Patterns</a></li><li class="li3"><a href="https://www.raywenderlich.com/6004856-building-an-app-with-only-code-using-auto-layout">Programmatic UI</a></li><li class="li3"><a href="https://clean-swift.com/">Get Started with Clean Swift</a></li><li class="li3"><a href="https://swift.org/documentation/#the-swift-programming-language">Swift Guide</a></li></ul>

<h2 class="p1">Site Reliability Engineering</h2>&nbsp;Tools:<ul class="ul1"><li class="li3"><a href="https://learn.chef.io/">Chef</a></li><li class="li3"><a href="https://prometheus.io/docs/introduction/overview/">Prometheus</a></li><li class="li3"><a href="https://learn.hashicorp.com/collections/terraform/aws-get-started">Terraform</a></li><li class="li3"><a href="https://terragrunt.gruntwork.io/docs/#getting-started">Terragrunt</a></li><li class="li3"><a href="https://www.runatlantis.io/guide/">Atlantis</a></li><li class="li3"><a href="https://kubernetes.io/docs/tutorials/">Kubernetes</a></li><li class="li3"><a href="https://docs.docker.com/get-started/">Docker</a></li><li class="li3"><a href="https://www.tutorialspoint.com/unix/index.htm">Linux</a></li><li class="li4"><a href="https://go.dev/doc/tutorial/getting-started">Go</a></li></ul>&nbsp;Blogs:<ul class="ul1"><li class="li3"><a href="https://sre.google/">Google Site Reliability Engineering</a></li><li class="li3"><a href="https://increment.com/">Increment</a></li><li class="li3"><a href="https://www.robustperception.io/blog">Robust Perception</a></li><li class="li3"><a href="https://blog.cloudflare.com/">Cloudflare Engineering Blog</a></li><li class="li3"><a href="https://engineering.fb.com/">Engineering at Meta / Facebook</a></li><li class="li3"><a href="https://vinted.engineering/">Vinted Engineering Blog</a></li></ul>&nbsp;Other:<ul class="ul1"><li class="li3"><a href="https://roadmap.sh/devops">DevOps Roadmap</a></li></ul>

Dominyka Mukha Vinted3050 1.jpg

List of useful resources for aspiring Engineers

Engineering

Vinted Marketplace

People Stories

Vinted Go

“Discuss your goals with your current Engineering Manager. Find ways to contribute to their tasks or daily activities… it allows you to understand what the role is really like and whether it’s a good fit for you.” – Rugilė. &nbsp;

Start exploring early

Here, there’s no shortage of Engineering Managers ready to share their knowledge and experience. Having a mentor can make the transition feel clearer and more achievable. &nbsp;

Find guidance

“A great way to see if management suits you is to try it out through the Engineering Academy or by taking something off your manager’s shoulders. You can shape the role in a million different ways.” - Audronė.

Experiment

Don’t wait for a title to start acting like a leader. Get involved, support others, and opportunities will come sooner than you expect.

Build your network

“Clear communication and honesty are key for me. I’m always open about what I know and what I don’t. If you’re willing to listen, no challenge feels too big."

Active listening and honesty

Especially in domains like Trust &amp; Safety, challenges can evolve fast. “Priorities can shift fast, and we often need to deal with unexpected changes in our roadmap. Flexibility is essential…you can’t get bored here!”

Adaptability

“This role is unique, and every day can feel different. One thing I learned early is that you need to manage your energy levels well…a solid planner really helps.”

Stay organised

&nbsp;"No day is ever boring, and you learn the most when the unexpected happens."

Openness to growth

“A great way to see if management suits you is to join the Engineering Academy or take something off your manager’s shoulders. Trust me, they’ll thank you. You can shape the role in a million different ways, so curiosity and experimentation really help.”&nbsp;

Audronė Šopauskaitė

“There will never be a ‘perfect’ time to apply. You’ll always have doubts about what you don’t know yet. I’ve been a manager for more than three years now, and those thoughts never go away…they just change. Don’t overthink it. If you’re interested, go for it.”

Rugilė Lukoševičiūtė

“Build your support network early. Peers, mentors, and senior engineers who can both challenge and assist you.&nbsp;Don’t wait for a title to start acting like a leader. Take on broader problems, look beyond your own area, and you’ll show you’re ready for the next step.”

Karolis Žilinskas

Vinted Pay

Golang, Ruby, Chef, Ansible, Terraform, Temporal, Jenkins, ArgoCD

Programming & Automation

Infrastructure

MySQL, Vitess, Redis, Memcached, Ceph, ElasticSearch

Storage

AWS, GCP, Cloudflare, SONiC, Cumulus Linux

Cloud & Networking

Prometheus, Thanos, Grafana, PagerDuty, VITA (our in-house monitoring/incident management platform)

Monitoring & Alerting

From multi-cluster Kubernetes and Istio service mesh, to beginning to explore AI-powered innovation and fully open-source network switches.

And more...

Technology never stands still, and neither do we.

Curiosity and a hunger to learn

If you enjoy the puzzle of big engineering challenges, you’ll thrive in SRE. &nbsp;

A problem-solving mindset

We work across many teams and domains – so, if you enjoy openly sharing or hearing about new ideas, you’ll fit right in.&nbsp;

Communication and collaboration

Confidence in Linux, networking, or automation go a long way, but what matters most is the drive to pick up what you don’t know yet.

Vinted blog