DEV Community

Cover image for Nevertheless, Feli Coded - ChooseToChallenge Yourself
Feli (she/her) for Studio M - Song

Posted on

30 11

Nevertheless, Feli Coded - ChooseToChallenge Yourself

My journey to become an Executive Principal Engineer working in Developer Relations (fancy buzzwords title) was not easy. Here is my story and why I believe we need to challenge ourselves.

A journey with obstacles...

In 2005, I finished my apprenticeship. Since then I have worked as a Developer. Most of the time as a Frontend Developer - or what I love to call it, UI Developer. But this specialization was not my first choice. In my apprenticeship, I loved Database Development and wanted to get a job in this area. It was 2005 you know, I was 19, blond, and couldnโ€™t land a job - even though I had an excellent certificate.

Back then, companies told me that they canโ€™t hire a 19-year-old woman for a team of twenty men with an average age of 30. In Germany, I could have sued them for it, at that time I didnโ€™t have the courage to do so. Nowadays I would do it, trust me.

Days went by and I was very frustrated but also didnโ€™t want to accept that I canโ€™t land a job in tech as a developer, only because Iโ€™m a woman and too young. So I applied for every Developer job I was able to findโ€ฆ nothing. All my fellow students already had a job - all men. So I did the last thing left to me - looking for an unpaid traineeship (wouldnโ€™t recommend it to anyone - you should get paid for what you are doing). Of course, I found something where I worked as a developer without getting paid for it. It was in a company that did web development (sadly no database stuff).
The traineeship ended after 6 months and they hired me for the minimum amount of wage. I didnโ€™t care, I was just happy to have my first paid job - finally.


Even if I wanted to, I never gave up...

What should I say? I proved every Database company, every other company that didnโ€™t hire me because Iโ€™m a woman wrong.

At 21 I was self-employed. At 23 I moved to a big city (Hamburg) for a job, which by the way was one of my best decisions ever. At 26 I started to work as a Freelance Developer - where I had to reject most of the projects I got offered because I had too much to do. With 29 the company I'm still working at hired me as a so-called Free Radical. With 30 I became part of CSSconfEU & JSConfEU. With 31 I built Developer Relations for a non-product company. With 34 I got promoted to Executive Principal Engineer and I'm the Tech Lead of a project which is fighting Covid 19.

Yes, the journey was not easy, but if I made it, you can make it, too!


Nevertheless...

My biggest achievement is that I accepted that it is hard as a woman in Tech BUT Iโ€™m still privileged. I'm white, I had a proper education, I earn enough money and I'm in a cis relationship. The moment I realized that, I started to fight for inclusion. I still call out every sexism case I witness. I donโ€™t get tired of saying that we still have a huge way to go in the tech community, at my job, at my friend's. But if you are a white cis woman, ask yourself:
If it is hard for me, how is it for non-gender people? women of color? for LGBTQ+ people?

The theme of International Women's Day 2021 is #ChooseToChallenge. So, I call every white cis woman in tech - choose to challenge yourself.
Get aware of your privilege, read and learn about it and your unconscious bias. Think about how you can be an ally for non-white-cis-women. Call out every discrimination.
Take actions on every day's business - example: Often people ask me โ€œFeli, how do we get more diverse, how do we get more women into techโ€. My answer? โ€œLetโ€™s talk about how we get more people from under-represented groups into tech. Diversity is not only about women in techโ€.

Be the change! Choose to Challenge!


Top comments (2)

Collapse
 
_moodybones profile image
Mel Jones โœŒ๏ธ๐ŸŒž๐Ÿคš โ€ข

Thanks for sharing Feli! I'm glad you didn't give up, tech needs more folks like you ๐Ÿ’–

Collapse
 
kotzendekrabbe profile image
Feli (she/her) โ€ข

I'm glad as well. Thanks a bunch Mel ๐Ÿ’–

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed: Zero in on just the tests that failed in your previous run
  • 2:34 --only-changed: Test only the spec files you've modified in git
  • 4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
  • 5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
  • 5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video ๐Ÿ“น๏ธ

๐Ÿ‘‹ Kindness is contagious

Engage with a wealth of insights in this thoughtful article, valued within the supportive DEV Community. Coders of every background are welcome to join in and add to our collective wisdom.

A sincere "thank you" often brightens someoneโ€™s day. Share your gratitude in the comments below!

On DEV, the act of sharing knowledge eases our journey and fortifies our community ties. Found value in this? A quick thank you to the author can make a significant impact.

Okay