Workshops by an engineer who still ships production code.
Hands-on technical training for engineering teams, built around your team’s actual stack: 1,000+ hours delivered, a trainer licensed by Romania’s Ministry of Education, and participants writing working code from session one. Half-day corporate workshops, quoted per scope.
Training that still gets used the week after
I run these sessions myself, and I write production code the rest of the week, so the exercises come from work that actually shipped.
Also: Zend Certified Engineer and 150+ professionals trained so far.
What I teach
These are the areas teams ask for most, and the list moves with the industry. The level is set by what your team can already do.
- Full-Stack Development: Node.js, React, MySQL, Firebase, Git, HTML5/CSS3
- Java and Android: fundamentals through mid-level, including native module development
- Python: from first scripts to automation and working with data, for people coming from another language or from none
- Design patterns and clean architecture: for working engineering teams that ship together
- AI/ML fundamentals to applied integration: supervised and unsupervised learning, decision trees, what weights actually do; pitched for software engineers, no data-science background assumed
What happens around the sessions
A call about what your team should be able to do afterward that it can’t today: stack, current level, and group size. The curriculum comes out of that answer.
Participants write working code from session one: exercises built around your stack, reviewed as they go. Half-day, full-day, or multi-day group formats, in person or live online.
Half-day workshops and longer, multi-day programs. Each is quoted after the scoping call, once the curriculum and group size are agreed in writing.
What teams ask before they book
Do you deliver remote or on-site?
Both. In person in Timisoara or at your office in Romania, and live online for teams elsewhere; the format stays hands-on either way. For teams in the US, an online session lands in your morning.
How large can the group be?
Hands-on groups work best at up to 12 participants: small enough that everyone gets their own code looked at during the session. Larger groups are possible by arrangement, usually by splitting them across sessions.
Can I book this as an individual rather than for a team?
Not through the studio. This page covers company training. Individual 1:1 sessions and personal upskilling plans run under my own practice at elvisclaudio.com.
Have a skills gap to close?
Tell me the stack, the team size, and what they should be able to do afterward. Scoping call first, then a curriculum built around your team.