For employers & project teams
A developer who connects the product to the work behind it.
I’m Issam El Bani, founder of VELTEIN. I build web applications, backend integrations and automation tools. This page connects the work in my portfolio to the skills your team may need.
What VELTEIN represents
VELTEIN brings together product development, website work delivered for clients and the tools I develop. Client websites belong to their respective owners; the case studies describe my development contribution. The common thread is practical software: understand the process, organize the data, build an interface people can use and connect the systems behind it.
My background includes more than eleven years in accounting, billing, financial reporting and business operations. That is business experience, alongside the software work shown here. It helps me ask useful questions about inputs, exceptions, reporting and the people who rely on a workflow.
Find the relevant work
Skills connected to actual projects.
Choose an area, then open the case studies for the product idea, public experience and my contribution.
Full-stack product development
Develop useful web products around a clear audience, practical tasks and a coherent experience.
Useful interview topics
Understanding the product need, defining scope, shaping user journeys and delivering the experience.
Services and product integrations
Connect a product’s capabilities with the tasks its customers and operators need to complete.
Useful interview topics
Product responsibilities, reliable service experiences, operator needs and delivery priorities.
Interfaces and visual consistency
Create clear interfaces and consistent presentation across different pages and user tasks.
Useful interview topics
Usability, visual identity, responsive presentation, interaction quality and bilingual experiences.
Automation and developer tools
Make repetitive tasks easier to manage through focused tools and visible user choices.
Useful interview topics
Understanding a manual process, designing useful controls and keeping actions reviewable.
Technical conversations
Walk through a project with me.
Pick the case study closest to your team’s work. I can explain the choices behind it, discuss its current limits and connect that experience to the problem you are hiring for.
- Start with the task. Who uses the product, what they are trying to do and the process the software supports.
- Understand the experience. The information a user needs to make a useful decision and complete a task.
- Discuss the decisions. The product priorities, responsibilities and delivery choices behind the public experience.
- Review the next step. What needs verification, what could improve and how I would approach the work.
How I approach delivery
I prefer a clear problem, a written scope and visible progress. Early working previews make it easier to test the assumptions behind a feature. I treat data, edge cases, hosting and handover as part of the work rather than leaving them until the end.
The case studies give a practical basis for assessing my experience: public interfaces, product demonstrations and specific contribution descriptions. Further discussion can focus on the experience relevant to your team while respecting the confidentiality of each product.
What to include in a hiring inquiry
Send the role or project brief, the responsibilities you need help with, your preferred working arrangement and any timeline. If one of these projects is especially relevant, mention it so we can start the conversation from concrete work.