Portfolio

What I accomplished in my career

After 8 years of continuous path in software development I can say I’ve accomplished:

• Built professional English skills.
• Received a “Employee of the year” award in a multinational company.
• Lead teams:
  • 2018, 3D virtual tour project: 1 designer, 2 jr devs.
  • 2021-2022, Payment Gateway: Scala team of 6 ssr devs.
  • 2026, Edtech Game server: 2 sr devs.
• Read a bunch of books about engineering.
• Gave talks:
  • 2023: AI engineering with ChatGPT 3.5
  • 2026: Harness engineering with Claude.
  • 2026: Managing a team.
• Lead internal workshops:
  • 2021: Functional programming with Scala.
  • 2021: Functional programming with Cats.
  • 2022: Learning concurrent programming in Scala.
• Got certifications that no one cares today:
  • Tensor flow, Pandas, ML in Python, Architect of SOA applications.
• Tried to compete in Kaggle and failed spectacularly.
• Participated in a couple of hackatons:
  • 2019: 3rd place for AI-powered WhatsApp chatbot for credit loan.
  • 2020: lost in NASA apps challenge.
• Worked with multiple cultures and remote teams:
  • Europe, America and Asia countries
• Built a record of diligence and reliability with my peers:
  • All my managers could, and most did, refer me as a very responsible person.
• Had a failed entrepreneur attempt with a partner.
• Learned niche technologies just because I like:
  • vim
  • nix
  • fp and tagless-final
• Wrote a lot of code at work and side-projects that no-one cares, before AI:
  • interaction-driven-design
  • dotfiles
  • order-management-system
  • type-driven-katas
  • more

I was not very good until late 2022, when my constant learning started to pay off and got exposed to (well-designed) high-throughput architectures.

I was very lucky to start working side-by-side with a principal engineer. This experience exposed me to better practices,

• I learned about applied DSA:
  • sliding window for anomaly detection in metrics.
  • inverted index for quick matching in ad campaigns.
• How to measure before taking decisions: data driven decisions.
• I learned about observability, done right: cardinality, product and application metrics, profiling, alerts.
• How to build real scalable components: price calculations, napkin maths in cloud architectures.
• How to approach and design when a codebase is pretty complex: domain-driven-design in practice.
• How to design and make explicit trade-offs: RFCs and ADRs
• Being pragmatic on a code-base: use the paradigm (Imperative, OOP, FP) based on the need.
• Incident management: damage-control, troubleshooting, analysis, post-mortems.

Overall, I became more thoughtful and resourceful by getting exposed to what a real, good, software engineering is.

Where am I now?

I work at Boddle, an Edtech startup for kids, I started as Sr backend and 3 months later got promoted as the tech-leader of 2 developers. We support around 60K CCU in a system with at least 3 applications maintained by us.

I always considered myself a IC, yet I took this role to sharp my soft-skills. Dealing with meetings and sprint plannings is not something I enjoy but something I want to prove myself I can do.

In my free time I read engineering books, learn maths and play with my personal agent (Hermes). I’m currently reading The Staff engineer path and previously read The Manager Path.

Where I want to head in my career

At 27yo I wanted to become an Architect. Now I am 31yo now and my goal is to become a better developer and leader. I enjoy reading and getting less stressed by taking better decisions. Hopefully, someday I’ll become a as good as the role-model I had. I don’t rush it anymore.