{"id":18355,"date":"2025-05-23T17:41:34","date_gmt":"2025-05-23T14:41:34","guid":{"rendered":"https:\/\/railsware.com\/blog\/?p=18355"},"modified":"2025-05-23T17:41:35","modified_gmt":"2025-05-23T14:41:35","slug":"coffeewithrw-from-tech-writer-to-analytics-engineer","status":"publish","type":"post","link":"https:\/\/railsware.com\/blog\/coffeewithrw-from-tech-writer-to-analytics-engineer\/","title":{"rendered":"#CoffeeWithRW: from Tech Writer to Analytics Engineer"},"content":{"rendered":"\n

Switching careers is never easy . It often starts as a quiet thought, but turning it into reality takes courage.<\/p>\n\n\n\n

At Railsware, we believe that being part of a mature, supportive team can help you challenge your growth limits and make bold moves. That\u2019s the idea behind our Career Switch series \u2014 to share first-hand stories of changing roles, the thinking behind those decisions, and practical takeaways.<\/p>\n\n\n\n

In the previous article, our Talent & Career Lead Daryna Kuzmyk shared<\/a> how she moved from Head of Sales to a junior recruiter.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This time, Piotr Ma\u0142ek walks us through his journey from writing technical content to working as an Analytics Engineer \u2014 a shift that involved constant questioning, learning, and adapting to change.<\/p>\n\n\n\n

Grab a coffee, tea or smoothie, and let\u2019s enjoy the story:<\/p>\n\n\n\n

Math geek, founder of travel agency and 2 career switches<\/h2>\n\n\n\n

Let me share a bit of my story, just to give some context behind my decisions.<\/p>\n\n\n\n

Technology has always been part of my world. My dad was a programmer \u2014 a pretty big deal back in the ’80s \u2014 and by the ’90s, we had a computer at home. That was rare at the time and turned our place into the unofficial neighbourhood museum:) <\/p>\n\n\n\n

In high school, we were supposed to have programming classes. And technically, we did. But thanks to some rather laid-back teachers, we mostly played Quake 3 instead. So I began learning algorithms and basic C++ on my own.<\/p>\n\n\n\n

I genuinely enjoyed it, and math too. I was a total math geek throughout elementary and high school, usually near the top of the class. However, over time, I started to drift away from both.<\/p>\n\n\n\n

\n
\n

We were diving into increasingly complex math problems, but I struggled to connect them to any career paths that actually excited me. My interests were starting to pull me in another direction.<\/p>\n <\/div>\n

\n
\n \n \n <\/div>\n <\/div>\n<\/section>\n\n\n
<\/blockquote>\n\n\n\n

Eventually, I switched gears and pursued a degree in tourism. Later, I launched my own travel agency \u2014 organising trips, booking flights, and helping clients discover new places. It gave me the flexibility I wanted and let me do something I genuinely loved (and still do).<\/p>\n\n\n\n

However, building a stable team was harder than I expected. Without a technical co-founder or the right expertise, the project eventually ran out of steam.<\/p>\n\n\n\n

At the same time, I started noticing a pattern in my tourism jobs: the work often felt repetitive, with few clear opportunities for growth or long-term development. And while my curiosity about technology and innovation kept growing, that world felt far removed from the one I was in.<\/p>\n\n\n\n

That gap pushed me to explore the startup and product space \u2014 environments that offered exactly what I was looking for: constant learning, a fast pace, and room for creativity. I took a step back to reflect on what I was good at and where I could really make an impact. That led me to technical content writing \u2014 something I both enjoyed and excelled at.<\/p>\n\n\n\n

Hunger games<\/h2>\n\n\n\n

For a few years, I was growing as a content specialist in startups. But the real acceleration started when I joined the Railsware team \u2014 a move that eventually led to my next pivot.<\/p>\n\n\n\n

I came on board as a technical content writer, working on products like Coupler.io and Mailtrap. What really hooked me wasn\u2019t just the writing \u2014 it was the technical depth behind it. Every article, landing page, or piece of documentation was a chance to dive into something unfamiliar. I loved unpacking complex topics and making them understandable \u2014 both for myself and for others.<\/p>\n\n\n\n

Yet, after a few years (and hundreds of articles), the learning curve started to level out.<\/p>\n\n\n\n

Because the audience for my content was mostly marketers, I had to keep things fairly high-level, avoiding deep technical dives. That meant I wasn’t gaining much beyond what I already knew. Over time, the topics became repetitive, and I began to feel that my growth had stalled.<\/p>\n\n\n\n

\n
\n

To keep developing \u2014 and to reignite my original excitement for tech and innovation \u2014 I knew I needed hands-on technical experience.<\/p>\n <\/div>\n

\n
\n \n \n <\/div>\n <\/div>\n<\/section>\n\n\n

So I took matters into my own hands. I began exploring data, a field I\u2019d long been curious about and had already written a lot on. With some time on my side, I started learning Python, SQL, and the fundamentals of data analysis.<\/p>\n\n\n\n

Then life threw me a beautiful curveball: my daughter was born. Suddenly, those imagined long evening study sessions turned into 30-minute sprints, once or twice a week, squeezed between everything else, on a good week.<\/p>\n\n\n\n

It wasn\u2019t easy. What I planned as a few-month course stretched into nearly two years. However, I kept going \u2014 and I got there.<\/p>\n\n\n\n

Eventually, I approached our product director to review my individual development plan. I wanted more \u2014 a new challenge aligned with my growing skill set. He suggested I try hands-on work: data extraction, dashboards, internal reporting.<\/p>\n\n\n\n

I jumped at the opportunity, and it was exactly what I needed.<\/p>\n\n\n\n

As I got involved in real projects, worked with actual data, and delivered insights that mattered, I gradually gained the confidence and skills to take on more responsibility. I began taking ownership of all sorts of projects\u2014something I could have only dreamt of a year or two back.<\/p>\n\n\n\n

Lessons learned<\/h2>\n\n\n\n

From my story, you can notice that questioning your goals and motivations is important. It\u2019s not always easy, but I\u2019ve learned a few lessons along the way that might help when facing similar decisions:<\/p>\n\n\n\n

    \n
  1. Don\u2019t waste time researching, start learning<\/li>\n<\/ol>\n\n\n\n
    \n
    \n

    When you\u2019re entering a new field, it\u2019s tempting to spend weeks comparing courses, reviews, and platforms. However, the truth is that most beginner resources cover similar material. The time you spend researching could be better used in actually learning.<\/p>\n <\/div>\n

    \n
    \n \n \n <\/div>\n <\/div>\n<\/section>\n\n\n

    Tip: I started with Dataquest and found it great for beginners, especially if you prefer structured, text-based learning. If you like video content, DataCamp might be more your style. I also tried Google\u2019s data analytics course \u2014 the one that promises job offers after certification. Two years later, I\u2019m still waiting :) So take course marketing with a grain of salt. Use them to build the basics \u2014 then move to step two.<\/p>\n\n\n\n

      \n
    1. Focus on practical experience<\/li>\n<\/ol>\n\n\n\n
      \n

      Once you\u2019ve reached a decent level, the best way to grow is by doing practical projects: writing simple scripts, analysing datasets from Kaggle, or automating tasks for your use. <\/p>\n<\/blockquote>\n\n\n\n

      Doing real projects matters even more if you can\u2019t yet switch roles within your company. It helps build your confidence, expand your portfolio, and prove your skills to future employers. And if you get the chance, contribute to NGOs or open-source initiatives. That kind of impact is not only rewarding but also a valuable experience.<\/p>\n\n\n\n

        \n
      1. Seek guidance from people already working in roles you aspire to<\/li>\n<\/ol>\n\n\n\n

        Their insights can save you time, help you focus your efforts, and give you a clearer sense of direction. And by \u201chelp,\u201d I don\u2019t just mean a quick chat \u2014 I mean, ask them to:<\/p>\n\n\n\n

        \u2013 Sharing useful materials and courses<\/p>\n\n\n\n

        \u2013 Reviewing your work <\/p>\n\n\n\n

        \u2013 Offering mentorship and support as you grow<\/p>\n\n\n\n

        At first, I knew I wanted to be involved in data, but I didn’t have a clear plan for how to approach it. Yet, our Head of Data, Elvira, guided me along the way \u2014 she suggested a few potential paths and helped me figure out what actually interests me. She also pointed out which skills would be most relevant for the role, so I started focusing on those, potentially saving many hours.<\/p>\n\n\n\n

          \n
        1. Be ready to give up professional confidence<\/li>\n<\/ol>\n\n\n\n
          \n
          \n

          One of the hardest shifts was letting go of the professional confidence I\u2019d built in my previous role.<\/p>\n <\/div>\n

          \n
          \n \n \n <\/div>\n <\/div>\n<\/section>\n\n\n

          Starting from scratch felt uncomfortable \u2014 sometimes it still does. There are days I think I should be moving faster or know more, even when the feedback is positive.<\/p>\n\n\n\n

          But I\u2019ve learned to accept being a beginner again. I\u2019m lucky to be surrounded by a supportive team that understands where I am in the journey. Regular syncs with teammates help me track progress, spot growth areas, and stay motivated.<\/p>\n\n\n\n

          Don\u2019t overthink – act<\/h2>\n\n\n\n

          The key is to start. Identify what you want to achieve and how to get there through reading, networking or research. And then take consistent, manageable steps. It\u2019s normal to encounter challenges or uncertainties, but progress comes from steady action. <\/p>\n\n\n\n

          Focus on practical steps rather than overthinking, surround yourself with the right people, and you will gradually move towards your goal.<\/p>\n\n\n\n

          \n
          \n Piotr Ma\u0142ek <\/div>\n\n
          \n Article by<\/span>\n \n Piotr Ma\u0142ek <\/span>\n
          \n Piotr Ma\u0142ek is a self-taught analytics engineer, analyst, and also a technical content writer with a strong focus on working with data and building automations. His work combines technical know-how with the ability to explain complex ideas simply. <\/div>\n \n <\/div>\n<\/section>\n\n\n
          \n Additional sources<\/span>\n \n