Consulting

I help software teams navigate architecture, process, and the messy space between engineering and business. You book a session, bring a problem, and we think through it together. Available by the hour, for as long as it's useful — or just once, if that's all you need.

Most of my experience is in the Scala ecosystem, but good architecture, pragmatic engineering, and business alignment aren't language-specific.

Code is getting cheaper. AI tools generate it, junior developers produce more of it than ever before. What hasn't gotten cheaper is judgment — knowing what to build, what to leave out, how to structure systems that survive contact with real business needs, and how to see the bigger picture when everyone around you is deep in the details. That's what I offer.

Transparent hourly rate. The first session is free.

What I can help with​

Architecture & Design - So that technical decisions don't come back to haunt you.

• System architecture review and honest feedback
• Domain modeling and structuring business logic
• Library and technology selection (effect systems, HTTP stacks, persistence, etc.)
• Build vs. buy — and knowing when "don't build" is the right answer
• Diagnosing root causes of recurring technical issues
• Recognizing over-engineering before it costs you

Scala Adoption & Team Effectiveness - Making Scala work for a single developer, the team, and the company.

• Adoption strategy and migration planning
• Onboarding — reducing time to productivity for new hires
• Code style, conventions, and review practices
• Team structure and collaboration patterns for Scala projects
• Hiring strategy in a market where Scala talent is scarce
• Tailored training sessions or workshops — focused on your team's specific challenges, not generic curriculum

Business–Engineering Alignment - Engineers think in systems. Business thinks in outcomes. I help to translate.

• Making technical work visible and understandable to non-technical stakeholders
• Building the ROI case for technical decisions (including Scala adoption)
• Technical debt prioritization in terms management can act on
• Technology roadmapping connected to business goals
• Modeling business processes (workflows, decisions, approvals, audit trails, backoffice operations) in a way both engineers and product people can reason about

Fintech - Relevant if you're building financial services.

• External systems integration
• Accounting system design
• Security and reliability considerations

Honest boundaries​

There are areas where I'm not the right person — and I'd rather be upfront about it than waste your time.

• Deep tooling — compiler internals, macro development, sbt plugin engineering. I'm only a humble user of these tools. There are people in the Scala community who are genuinely brilliant at this, and I'm happy to point you to them.
• Specialized performance engineering — I can reason about performance at an architecture level, but if you need JVM bytecode profiling or GC tuning, you want a dedicated specialist.
• Database internals — I design distributed systems and data models, but I'm not a DBA. If your problem is about database engine internals, that's outside my depth.
• Staff augmentation — I'm here as an advisor. If you need people to build things, I can recommend companies that do staffing really well.

If your problem is in one of these areas, I'll tell you honestly — and if I know someone who's a better fit, I'll make the introduction.

Who this is for​

This tends to work well if you recognize yourself here:

• You're a CTO or VP Engineering making architecture bets or defending technology choices to the board. You want a senior second opinion that isn't trying to sell you a platform.
• You're a tech lead or architect and the most experienced Scala person on your team. You want someone to review your designs, challenge your assumptions, or confirm you're on the right track.
• You're an engineering manager dealing with slow delivery, painful onboarding, or a hiring pipeline that isn't working. You're not sure if the problem is technical, organizational, or both.
• You're a startup founder making early architecture and technology decisions. You want to get them right without hiring a full-time architect or committing to a consulting firm.

What it costs​

€250/hr

Your first introductory session (up to 1 hour) is free. Use it however works best for you — assess whether my experience is relevant to your situation, or come with a specific question and try to get an answer on the spot. If you get what you need in that first hour, walk away happy. No hard feelings, no follow-up sales pitch.

After that, sessions are billed hourly. No retainers, no minimum commitment, no hidden fees. You book time, we talk, you get an invoice.

Let's talk​

Drop me an email or a message on Discord, LinkedIn, or X. Include a brief description of what you'd like to discuss, your availability, and your timezone — I usually respond the same day (I'm based in CET).

No pitch, no pressure. If I can't help, I'll say so.

About me​

I'm Voytek — a staff software engineer with 13+ years of experience, primarily in Scala but also across the JVM ecosystem, TypeScript, and beyond.

I've worked across fintech, banking, information security, ad-tech, and telecom — building distributed systems, integrating payment providers, modernizing financial ledgers, and automating business processes. I build open-source tools and run the Business4s community — a Scala community focused on solving real business problems rather than chasing technical sophistication for its own sake.

Through years of open source work, conference speaking, and community building, I've built a broad network across companies, consultancies, and OSS projects. If I'm not the right person for your problem, I can often connect you with someone who is — whether that's a library maintainer, a domain specialist, or a team that does hands-on delivery.

I also run a free mentorship program for individual engineers. Consulting is a different thing: it's for teams and companies, with dedicated time and the ability to involve multiple people.

FAQ​