Balancing Finance Work and Salary Raise | Generated by AI
Question: I just talked with my lead about putting 80% effort into the daily Finance platform work (Java + Angular). I also have a big personal todo list. How do I balance this, meet expectations, and approach my vendor lead about a salary increase?
Answer:
Let me be direct, grounded in your actual situation (contractor at the bank, 900K mortgage, AI-engineering trajectory, family wants stability).
The 80% reality
Your lead just told you 80% goes to Finance platform (Java + Angular). Decode what that actually means: they want you reliable and present on this project. That’s the “tax to pay for the salary” line from your own playbook. Pay it cleanly — don’t fight it, don’t half-ass it, because your leverage for a salary increase depends on being visibly dependable right now.
But 80% of work-hours ≠ 80% of your brain. The Java/Angular work is largely execution you’ve done for 12 years. The move is to compress it with AI leverage so the 80% costs you less actual cognitive energy:
- Angular component scaffolding, Java boilerplate, test generation, ticket triage → automate with your agents (you build
ww,iclaw,zz— point them at this). - Goal: deliver the 80% in ~50% of your focus budget. The recovered margin is yours.
This is the only honest way to “balance.” You don’t balance by negotiating fewer Finance hours — you balance by making those hours cheaper to produce.
Your todo-en list
I can’t see the contents of lzwjava.github.io/todo-en — it’s not in my context. But based on your preferences the categories are: job interview prep, large Excel project, and the Finance daily work. Triage them by your playbook’s compounding test:
- Finance daily work → tax. Minimize effort-per-output via automation.
- Large Excel project → which bucket? If it’s bank work, it’s also tax. If it’s a personal/revenue experiment, it’s compounding — protect it.
- Interview prep → this is leverage. Even if you’re not leaving, interviewing sharpens you and creates the option + the number you’ll quote your lead. Keep it warm, low-intensity (a few hours/week), not a full sprint.
Everything that doesn’t compound toward AI engineering or startup optionality gets the minimum viable effort.
Meeting expectations
Expectations management at a vendor arrangement is concrete, not vibes:
- Make your output visible. Ship, comment on tickets, update status before being asked. Perceived reliability is what your lead reports upward — and it’s the entire basis of your raise ask.
- Define “done” with your lead explicitly for the 80%. Ambiguous scope is where contractors silently lose. Pin it.
- Don’t volunteer for scope creep. 80% is the ceiling, not the floor that grows.
The salary increase conversation
You’re going to your vendor lead (not the bank directly — right channel, since you’re a contract arrangement). Frame it around leverage and market, not need:
Don’t say: “I have a mortgage / cost of living.” Banks and vendors don’t price on your expenses.
Do say, in order:
- Anchor on contribution. “I’m now carrying 80% on the Finance platform — here’s what I’ve delivered [specific shipped things].” Tie the raise to the expanded responsibility your lead just handed you. The 80% ask is your strongest lever — they increased your load; that’s the natural moment to reprice.
- Anchor on market. This is where interview prep pays off. “Comparable AI/full-stack contractors are at [X].” Have a real number from actual market signal (interviews, recruiter pings, your top-6%-AI-usage profile is a genuine differentiator — use it).
- Make it easy to say yes. Give a specific number or range, not “a raise.” Vendors counter-anchor; you set the anchor first.
- Quiet BATNA. You don’t threaten to leave. But your calm comes from having alternatives (interviews in flight). That energy is felt without being stated.
One more thing specific to you: an increase here directly accelerates the “quit number” math in your playbook (burn × 12 + mortgage to 500K). Every CNY of raise is runway. So this conversation isn’t just income — it’s startup-timeline compression. Treat it with that weight.
Concrete this week
- Tell your lead clear, confident yes to the 80%, and pin down the scope/”done” definition in the same conversation.
- Point your agents at the repetitive Java/Angular work to reclaim focus margin.
- Keep interview prep at low simmer — it’s both your raise leverage and your BATNA.
- Walk into the salary talk with: a contribution list, a market number, and a specific ask.
If you paste the contents of your todo-en list, I’ll triage each item into tax / leverage / compounding and tell you exactly what to drop.