🎯 Back-End Engineer focused on building reliable, scalable, and maintainable systems.

I’m a Back-End Engineer based in Porto, Portugal, currently working at CEiiA. I specialize in API design, backend architecture, and data-driven systems, with a strong focus on clean code, performance, and reliability.

I’m comfortable working across the full lifecycle of backend services — from design and implementation to deployment and monitoring.

• 🔭 Current project: Teltonika Go Package
• 🌱 Currently deepening: Go (concurrency, performance, tooling)
• 💬 Core strengths: REST APIs, backend architecture, databases, integration services
• 🌍 Portfolio: danieljvsa.vercel.app

• ✅ Design and implement scalable REST APIs used in production environments
• ✅ Translate business requirements into robust backend solutions
• ✅ Write clean, testable, and maintainable code with a long-term mindset
• ✅ Work confidently with relational and NoSQL databases
• ✅ Collaborate in cross-functional teams (product, frontend, DevOps)
• ✅ Strong sense of ownership, reliability, and delivery

Typical responsibilities I handle:

• API design and versioning
• Backend service integration (third-party & internal)
• Data modeling and persistence
• Debugging, performance analysis, and bug fixing
• Technical documentation and knowledge sharing

Open-source Go library for Teltonika GPS devices

• Designed and implemented a Go-based package to parse and handle Teltonika device protocols
• Focused on performance, correctness, and extensibility
• Structured for real-world backend integrations (tracking, IoT pipelines)
• Emphasizes clean APIs, documentation, and testability

🔗 https://github.com/danieljvsa/teltonika-go

Backend development in a professional, multi-disciplinary environment

• Contribute to backend services and APIs supporting internal and external platforms
• Work with databases and integrations in production systems
• Collaborate closely with engineers, product, and stakeholders
• Apply best practices around code quality, documentation, and maintainability

Engineering practices I follow:

• API-first and contract-driven design
• Clear documentation and readable code
• Code reviews and constructive feedback
• Incremental delivery and continuous improvement
• Pragmatic problem-solving over over-engineering

What this reflects:

• Consistent activity on GitHub
• Open-source contributions and maintained repositories
• Focus on practical, production-oriented code

Reliable systems are built with clarity, discipline, and care.