There's a layer underneath the actual work — the culture layer.
It quietly shapes how you spend your days, how you get paid,
and whether people see you as reliable or just available.
You pick it up as you go, and here are some of them.
1. You are the client's teammate, not their vendor
This one took me a moment to really internalize.
In a dedicated team setup, you're embedded inside the client's world. You're not sending deliverables from the outside — you're sitting (virtually) at their table, in their Jira, joining their standups, and sometimes getting pulled into their internal drama.
That means how you communicate matters a lot. No matter what's happening behind the scenes on your end, you show up polished and professional. The client doesn't need to feel your internal chaos. They just need to feel like you've got it.
And in some cases — when you're meeting the client's own clients — you represent the agency, not your home company. That's a different hat, and you wear it clean. You don't introduce yourself as an outsider. You're just part of the team.
2. Ticket updates are a form of respect
This one seems small but it's actually huge.
Every ticket you touch deserves a comment. Not an essay — just a clear, honest update on where things stand. Especially if a task is running longer than expected, or you've hit a blocker, or you're waiting on someone else.
It keeps everyone aligned without anyone having to ask. And asking "what's the status?" is low-key one of the most annoying things in collaborative work. A well-placed comment saves a whole Slack thread, a status meeting, and someone's afternoon.
Think of it this way: your ticket trail is a real-time changelog of your workday. Keep it readable.
3. Time logging is not optional — and it protects you
Time logging felt like admin overhead at first. Then I realized: this is actually how you get paid correctly, and how disputes never happen.
When your logged hours match the client's records exactly, there's nothing to argue about. When they don't, things get messy — and you're the one who has to untangle it, usually at the worst possible moment.
Log daily. Screenshot on Fridays and at the end of the month. It's a five-minute habit that saves hours of stress later. Future you will be quietly grateful.
4. No tickets ≠ free time. It's a signal to act.
One of the clearest lessons from this kind of work: if you don't have anything to do, say something immediately.
Don't wait. Don't assume the backlog will magically refill. Tell your PM or TL right away. In the meantime, look at old tickets, read through upcoming sprint items, think about edge cases you haven't tested, or review code you wrote two weeks ago with fresh eyes.
There's usually always something. And if there genuinely isn't — that's a process too. There's a ticket for idle time, your manager needs to know, and it gets logged properly. It's not embarrassing. It's just how an honest system works.
5. Holiday bonuses and overtime exist — but you have to speak up first
Want to work a national holiday for double pay? Totally possible. But you need to let the team know well in advance — not the morning of.
Same with overtime. If a client asks you to push extra hours, don't just do it and hope it shows up correctly in your paycheck. Communicate it first. Get it approved. That way the rate gets negotiated properly with the client, and you actually see it reflected in what you earn.
The system works for you when you engage with it early. Stay quiet and you're basically leaving money on the table.
6. Vacation notice is longer than you think
Two weeks notice for most of the year. Four weeks during the busy summer months and around Christmas.
That sounds like a lot until you consider that a client team is built around your availability. Sprint planning, ticket assignment, standups — your absence has a ripple effect. Giving plenty of notice isn't bureaucracy for the sake of it. It's just keeping things fair for everyone involved, including you.
Book early, tell people early, come back rested.
7. Sick days have a process too — follow it immediately
Nobody plans to get sick. But when it happens, the instinct to "just rest and deal with it tomorrow" can cause more hassle than it's worth.
The right move: inform your PM on the client's side first, then email HR as soon as possible. Not later. Not when you feel better. Right away.
Why? Because other people are rearranging their day around your absence. And your sick leave needs to be processed correctly so your paycheck isn't affected. Both of those things depend on timely communication.
8. Knowing when to ask for help is a skill
Working embedded in a client team can sometimes feel isolating — you're technically part of two organizations but not fully home in either one. It's easy to sit on a problem too long because you're not sure who to ask.
What I learned: when in doubt, ask your direct manager or department lead. Not a week later. Not after you've already gone in circles. Just ask.
Good teams have a clear escalation path for a reason. Use it. Being resourceful is great, but spinning your wheels alone isn't.
The bigger picture
Working in a dedicated team taught me that being a good developer isn't just about writing clean code.
It's about communicating clearly, logging honestly, showing up reliably, and understanding that you're part of something bigger than a single ticket. The "soft stuff" is actually load-bearing. Strip it away and even great code doesn't hold up the way it should.
If you're moving into this kind of role — or already in one — I hope something here clicked for you.
Credits: Scandiweb
Top comments (0)