DevJourney

1. Why does this project exist?#

DevJourney was initially conceived as a personal website where I could write articles, document my learning journey and showcase projects.

However, the project has evolved into something much bigger.

Its purpose is no longer simply to publish content.

Its purpose is to become the platform that helps me transform from a Backend Developer into an AI Backend Engineer while simultaneously demonstrating that evolution publicly.

Every technical decision, every article, every feature and every architectural choice should support that objective.

The website itself becomes proof of my skills.

2. Personal Mission#

Between September 2026 and February 2027 I want to intentionally reinvent my professional profile.

The goal is not simply learning AI.

The goal is becoming capable of:

• Designing backend systems that integrate modern AI technologies.
• Deploying production-ready AI features.
• Understanding the trade-offs behind architectural decisions.
• Explaining complex technical concepts confidently in English.
• Demonstrating all of that through real products instead of certificates.

The project itself is the learning process.

3. Professional Goal#

By February 2027 I want to be able to apply confidently for positions such as:

• AI Backend Engineer
• Backend Engineer (LLM Platforms)
• AI Platform Engineer
• Staff Backend Engineer (AI-enabled products)

Target companies include international product companies where English is the working language and AI is part of the product.

Success is defined as being able to:

• Pass technical interviews in English.
• Explain architecture decisions fluently.
• Discuss AI systems from a backend engineering perspective.
• Present DevJourney as evidence of real engineering experience.

4. The Main Problem#

Today I identify several gaps between my current profile and the profile required by the market.

Technical#

I know backend engineering well.

However, I still need practical experience building complete AI-powered applications, including:

• LLM integrations
• RAG systems
• Vector databases
• Embeddings
• Prompt Engineering
• AI evaluation
• AI observability
• Production deployment

English#

I can read technical documentation.

I can understand many technical talks.

But I still lack confidence explaining technical concepts naturally in English.

The language itself should become part of the learning journey.

Visibility#

Many developers know more than they can demonstrate.

I want every new skill to become public evidence.

Instead of saying

"I know RAG"

I want to show

"I built it."

5. Product Vision#

DevJourney is not a blog.

It is not a portfolio.

It is not an online CV.

DevJourney is an AI-powered learning platform built by someone becoming the exact audience of the product.

I am building the mentor I wish I had.

6. Product Philosophy#

Several principles should guide every future decision.

Learn publicly#

Learning is not hidden.

Progress is visible.

Mistakes are documented.

Architecture decisions are explained.

Build while learning#

I will never wait until I "know enough".

Learning happens because the product forces me to solve real problems.

The product is the curriculum.

English by immersion#

Whenever possible:

• Documentation
• Blog posts
• Commit messages
• Architecture documents

will be written in English.

Spanish may exist as support during the learning phase but English is the destination.

Real engineering over tutorials#

I do not want tutorial projects.

Every feature should solve a real product problem.