For hiring teams
Junior developer, with experience owning the whole project.
I have run a client project from first brief to handover, and I did it with a team behind me: a senior mentor from Studio Agnis, who worked through the big decisions with me.
Talk about a role or download the CV for more details: CV (EN) (PDF, 164.1 KB)I have worked inside a larger team through Studio Agnis. Now I want a bigger, more structured one, where I write things down, ask early and welcome review.
- Rebuilt a ten-year-old online store end to end, with a custom WordPress theme and WooCommerce.
- Moved the whole catalogue by CSV import, checked category by category before it went live.
- Kept the live store online when the old host forced a deadline.
- Client projects as part of the Studio Agnis team, with a senior colleague as mentor.
- Architecture and migration decisions made together with the mentor and the client.
- I write things down: specs, task logs, handover notes.
- I ask early and welcome review.
- I keep the client informed, in plain language.
One person, every stage.
On Excellence.rs I was the only developer and the client's point of contact. This is what that looked like, and what each stage means for your team.
-
Client brief
I talk to the client first, in plain language, and write down what is wanted, what is not, and what done looks like. For your team: understanding, writing down and acting around project requirements, not just around task descriptions.
-
Structure and build
A custom WordPress theme in ACF and PHP, with one universal page template, so every page type can be edited from the backend. For your team: work editors can use without calling a developer.
-
Data migration
The whole catalogue moved by CSV import, with one master schema, checked category by category against known value ranges before every import. For your team: understanding of how data works in the real world, not just inside code.
-
Launch
The old host set a deadline the rebuild was not ready for. I patched the legacy site to run on PHP 8 and kept the live store online, and redirects were set up with an SEO specialist so the existing search rankings carried over. For your team: a calm launch, not a scramble. Experience working with live sites, not just projects.
-
Handover and after
Specs, task logs and notes, so someone else can take over. After launch I improved the admin from the client's real daily use: key fields in Quick Edit, scheduled sales for a whole category, and a soft-hide for products. For your team: work that does not depend on me staying.
WHO I AM?
I am Jovan Rudić Vranić, a full-stack developer studying Information Technology in Novi Sad. I started in an agency team at Studio Agnis, then took a whole store rebuild on alone. I like work I can follow from the first conversation to the handover, and I like it more with a team around it.
- Based in
- Novi Sad and Subotica, Serbia
- Studying
- BSc Information Technology (in progress), Faculty of Sciences, University of Novi Sad
- Works in
- WordPress, WooCommerce, custom themes, ACF, PHP, React
- Experience
- Frontend developer in the Studio Agnis agency team, and sole developer on a full store rebuild
-
Before building, I read the client's funnel, user types and conversion goals, then shape the structure and the pacing of the copy around them. I did this on a short single-sprint project, working as consultant and developer at once.
-
Custom WordPress themes without a page builder. On Excellence.rs one universal page template made every page, category and collection editable by the client. At the agency, I built blocks from Figma designs that held up when non-technical editors filled them with real content.
-
WooCommerce has no good category page by default. I built a custom archive template that shows only the blocks that have data, so there are no empty or broken-looking sections.
-
Product details such as unit and dimensions were buried in free text. I turned them into real attributes, created only where a value exists, and gave each product three linked post types: FAQ, technical specs and user manual.
-
The whole catalogue moved from an unstructured legacy database through one master import schema, with linked IDs and image galleries in the same pass, checked category by category before every import.
Able to understand, communicate, guide and deliver
I was the single point of contact from first brief to handover, and I planned the work myself.
-
Plain language
I explain technical choices in words the client understands, and big decisions are made together with the client and a senior mentor.
-
Written down
Specs, task logs and decisions are kept in writing, so anyone can pick the work up.
-
Early and honest
I set expectations before work starts, raise issues early and in writing, and say so when something is unrealistic, including the limits of my own work.
-
Steady rhythm
Work is planned in time blocks on a Trello board. In the agency team I worked in weekly sprints and presented sprint work to the client's own team.
What I avoid:
- Disappearing after the brief and showing the client something finished weeks later.
- Technical jargon where a clear answer was needed.
- Problems found late and reported late.
- Work that only its author can continue.
My take:
- A client who is kept informed rarely needs reassuring.
- Documentation is part of the work, not a favour after it.
- Someone who owns the conversation with the client saves a team more time than an extra pair of hands.
A project I delivered end to end:
Excellence.rs — online store
October 2025 – March 2026From migrating 700+ products without a single error to an admin panel the client uses every day with no technical knowledge — full ownership of the project, from the first line of code to launch.
Read more!: Excellence.rs — online storeQuestions you may have
- I build and maintain WordPress sites and WooCommerce stores: custom themes, custom post types and editor-friendly blocks. I build content blocks that stay stable when non-technical editors fill them with real content. I move large amounts of messy data safely and check it category by category before it goes live. I read a conversion funnel first, then build the structure and pacing of a page around it.
- I have worked inside a larger development team at Studio Agnis, next to content strategists and designers, with a senior colleague as mentor. We worked in weekly sprints, and I presented the sprint work to the client's own team. I write things down: specs, task logs and handover notes. I raise problems early and say so when something is unrealistic, including the limits of my own work.
- Languages: PHP, JavaScript, Python, HTML, CSS, SASS, Liquid. WordPress and e-commerce: custom themes, block themes, the block editor, the Interactivity API, ACF, WooCommerce and Shopify. Frontend and build: React, Tailwind CSS, Vite. Tools: Git, GitHub Actions, Figma, Trello. I also keep project knowledge bases in Obsidian and use AI-assisted development with Claude Code.
- I am looking for a role in a bigger, more structured tech team, part-time or full-time, as an employee or a freelancer. I want to work beside senior developers, own real pieces of work from start to finish, and keep learning.
- You can expect me to be reachable and to answer regularly. The work is documented, so anyone can take it over. If something is unrealistic, I tell you early, and I do not leave you stuck.
Talk about a role.
A 30-minute call, no preparation needed.
I would like to hear what the role needs, and tell you plainly what I can do now and what I would still be learning.
Prefer to write first? info@jovanrudic.com
What you get from the call
- A direct walk-through of the Excellence.rs project, with room for technical questions.
- A feel for how I explain my work, before you take me to your team.
- Clear answers about my stack, my experience and the kind of role I am looking for.
- Anything your process needs from me, such as the CV or a project write-up.
The calendar is provided by Calendly. Booking shares your name, email and answers with Calendly. Privacy Policy
Not ready to talk yet?
Leave your email and I send you a short overview. Easy to read, easy to forward.
What I believe.
The standards I hold myself to, and the thinking behind them.
-
Build for real content
A layout has to hold when real, messy content goes in. If it only works with perfect text, it is not finished.
-
Blocks over page builders
Block-based WordPress lets editors change their content freely while the design stays intact.
-
Speed and SEO from the first sketch
They are decided at the start, not patched on at the end.
-
Every page needs a next step
A page with no path for the visitor is a brochure, not a tool.
-
Check before it goes live
Large imports and launches are checked in small parts, because a mistake found after launch costs the client more.
Need it in print? Get print friendly version here: Work with me: overview for hiring teams (print version) (PDF, 1.9 MB)