Growing as a Developer at Addepto: A Real-World Perspective

When developers talk about company culture and values, we often roll our eyes at corporate buzzwords. What matters is how these translate into our daily work and professional growth. Let me share my concrete experience at Addepto, focusing on what actually happens rather than what’s promised.

Technical Growth in Practice

My journey from Python Development to Data Engineering shows how technical growth works here. It started with a clear personal goal: to deepen my skills in handling data and designing data architectures. I expressed this during a conversation with my manager, openly acknowledging that I felt uncertain about databases and data processing. Instead of getting a generic response, this led to:

• Direct access to colleagues with expertise in these areas
• Encouragement to explore new tools (like Airflow and Benthos) on my own time
• Opportunities to discuss what I was learning and eventually apply it on real project

A turning point came when my colleague Mateusz Kijewski helped me develop a practical learning plan. Instead of diving into lengthy theory, we focused on getting a broad overview and testing tools in small, self-driven projects. This allowed me to learn at my own pace and make tangible progress outside my usual work tasks.

Real Project Experience

After learning on my own, I eventually got to work on an event mesh data platform for an aviation client. This isn’t a side project or a training exercise – it’s a real system that needs to work. Here’s what this means in practice:

• I get to work with tools like dltHub, Databricks, and other modern data stack technologies
• There’s room to experiment with different approaches (like trying out Databricks Apps with Streamlit)
• Mistakes are viewed as learning opportunities, not failures

Day-to-Day Reality

One of the most significant benefits at Addepto is being trusted to structure my day in a way that fits my productivity style. For instance:

• I can take a 20-minute power nap between afternoon sessions when I need to reset
• Deep work sessions are respected – no random meeting interruptions
• Documentation and learning time are considered real work, not something to do “when you have time”

Professional Development That Actually Happens

What makes professional development real here isn’t formal training programs but practical opportunities:

1. Direct Client Interaction
   • I work directly with stakeholders to understand the requirements
   • Technical discussions aren’t filtered by layers of management, so there’s less chance for miscommunication
   • I can propose and discuss technical solutions directly
2. Tool Selection Freedom
   • When I needed to visualize data, I could propose and try out tools like Streamlit
   • Decisions are driven by technical merit rather than “this is how we’ve always done it”
3. Knowledge Exchange
   • Colleagues like Paweł Żak share their expertise through knowledge-sharing sessions
   • These sessions spark fresh ideas to experiment with new solutions
   • Questions are welcome, no matter how basic

Career Acceleration in Practice

My transition from Python Developer to Data Engineer wasn’t just a title change. Here’s how it actually happened:

1. Skill Gap Identification
   • I had open conversations with more experienced team members about technical challenges
   • Freedom to admit what I didn’t know without fear of judgment
2. Learning Implementation
   • Could immediately apply new knowledge to real projects
   • Had access to both tools and expertise when needed
   • Could structure learning around actual project needs
3. Growth Opportunities
   • Started with smaller data components in existing projects
   • Gradually take on more complex data engineering tasks
   • Now leading data platform development for a major client

The Reality Check

Not everything is perfect – we face real challenges like any technical team. But what matters is how these challenges become growth opportunities:

• When projects get complex, we can take the time to plan properly
• If something isn’t working, we can change our approach
• Technical debt is acknowledged and addressed, not ignored

This isn’t about company values written on a wall – it’s about how work actually gets done and how developers can grow their careers in practice. The key is that professional growth isn’t just encouraged; it’s built into how we work every day.