ERIK
FILIPOV
Software developer working across web applications, backend systems, automation, IoT and digital products.
- Role
- Software Developer
- Location
- Riga / Latvia
- Focus
- Software / Web / Systems
- Experience
- 10+ Years (JavaScript)
Riga / Latvia · Software / Systems
The developer behind the systems
I am a JavaScript developer with over 10 years of experience creating reliable and efficient systems. Most of my work has been in the blockchain space and fast-paced startup environments, building software tools, mobile apps and web platforms from the ground up.
My work does not stop at the visible interface. I am interested in the whole system — frontend, backend, APIs, databases, automation and the infrastructure the software runs on. Understanding how the layers connect is what makes a system reliable rather than just presentable.
I work primarily with React, Node.js and modern web technologies, and my interests extend into artificial intelligence, industrial robotics, financial technology and connected devices.
Unfinished IT degree, RTK.
Self-taught, through documentation, experimentation, building projects and running systems in production.
Where it started
The scope of the work expanded over time — from self-directed learning into complete, running systems.
Self-taught start
Development began as self-directed learning — documentation, experimentation and building rather than a formal curriculum.
Web development
Work moved into web development: interfaces and applications for the browser.
Full applications
Projects grew from single interfaces into complete applications with their own logic, state and data.
Backend & systems
Work in the blockchain space and fast-paced startup environments expanded into backend services, internal tools, mobile apps and web platforms built from the ground up.
Production & scale
One central project grew to at least 30 independently operating services across five platforms, bringing deployment, process management and cost-efficiency responsibilities.
IoT, automation & AI
Current interests extend the same systems thinking to connected devices, automation, artificial intelligence and financial technology.
Exact dates for these stages are not listed. The sequence describes increasing scope, not a strict chronology.
From code to systems
Interface
Web interfaces and application behaviour in the browser.
Application
Interfaces grew into complete applications with their own state, interaction and logic.
Backend
Projects requiring application logic and APIs moved the work beyond browser-only interfaces.
Data
Persistent data introduced databases, queries and data processing.
Infrastructure
Running applications in production introduced deployment, Linux and process-management responsibilities.
Integration
Systems were connected to external services — authentication and transaction monitoring among them.
Complete system
The scope became whole systems: interface, logic, data, infrastructure and integrations together.
Engineering principles
Understand the system
Before changing or building something, understand the problem, the users, the data, the dependencies, the constraints and the existing architecture.
Build beyond the screen
An interface is often only one layer. Implementation has to consider how the layers below it interact.
Make work visible
Development should not disappear into a black box. Progress is shown through concrete deliverables rather than vague percentage-complete claims.
Solve the actual problem
Technology selection follows the requirement. The architecture comes before the stack, not the other way around.
Where my work connects
- Web
- Mobile / Desktop
- AI / Automation
- IoT / Hardware
- Finance
- Enterprise
- E-commerce
- Community
These are development areas, not claims of employment in each sector.
Not only the frontend
The layers I can work across, from the interface down to the infrastructure the system runs on.
What I'm building toward
- Application architecture
- Automation
- AI systems
- Infrastructure
- Product development
These directions come from current interests and existing work — they are areas of focus, not commitments.