How to Ask for a Raise as a Junior Developer in the Philippines

Short answer: Philippine labor law does not require a private employer to give you an annual raise; salary increases beyond the minimum wage are "management prerogative" unless your contract, a CBA, or established company practice says otherwise. The strongest time to ask is right after regularization (six months in) or at your scheduled performance review, backed by a short list of shipped work and a market-rate number from a real source. Ask for a specific figure, not a vague "more," and get any agreement in writing.

Nobody teaches you this part. You get hired, you ship your first few tickets, six months pass, and you're still on your starting offer while your Slack notifications fill up with"AI is changing everything" think-pieces. At some point you have to actually ask, and for a junior developer in the Philippines, that conversation carries extra confusion: is there a law that covers this? Is six months too early? What number do you even say?

This post covers what Philippine labor law actually requires (less than most people assume), when the ask lands best, how much to ask for, and word-for-word scripts you can adapt.

#Is there a law that says I should get a raise every year?

No. Outside a handful of specific triggers, Philippine labor law treats salary increases above the minimum wage as management prerogative, meaning the employer can grant, delay, or deny them unless something else legally binds them to it. The legal triggers that do exist are narrower than most people expect:

If you're a junior developer at a regular local company, the most common trigger you'll actually run into is the minimum wage floor, not a merit review. As of September 26, 2026, the non-agricultural minimum wage in the National Capital Region is ₱755 per day under Wage Order No. NCR-28, following a ₱60 increase from the prior ₱695 rate. Most developer salaries sit well above this floor, so the minimum wage itself rarely forces a raise for you directly, but it's useful to know the mechanism exists, because it's one of the very few places where "you're legally owed this" actually applies. (DOLE)

Wage distortion is the more interesting one for tech workplaces. If a new wage order pushes your company to raise pay at the bottom of the ladder and that compresses the gap between, say, a new hire and someone two years senior, the law requires the employer to negotiate a fix, not ignore it. You probably won't invoke this yourself as a junior employee, but it's worth knowing it exists if your company just gave a big minimum-wage-driven bump to new hires and you're the one who got quietly left at the old rate.

#When is the right time to ask?

Three natural windows exist, and they're not mutually exclusive:

1. Right after regularization. Under the Labor Code, probationary employment cannot legally exceed six months from your start date; if you're kept on past that point, you become a regular employee automatically, even without a formal notice. Regularization is a real, visible milestone, and companies that don't automatically bump probationary pay to a regular rate are a reasonable point to ask.
2. Your scheduled performance review, if your company runs one. This is the easiest conversation to start because compensation is already an expected topic; you're not springing something on your manager.
3. After a specific, attributable win: you shipped a feature that shaped user-facing behavior, you fixed something that was actively costing the company money or customers, or you took on responsibilities clearly above your job description. Waiting for the "right" calendar date matters less than being able to point at something concrete.

What doesn't work as a reason, even though it's real: rent went up, cost of living is higher, a co-worker makes more than you. None of these are wrong to feel, but framing the ask around the company's benefit, not your personal budget, is what actually moves a manager, according to career-advice guidance from both Indeed's and LeanIn.org's negotiation guides.

Timing matters at the company level too. Asking right after a round of layoffs, a missed quarter, or a hiring freeze announcement is asking to be told no for reasons that have nothing to do with your work.

#How much should I ask for?

Two different numbers are useful here, and they answer different questions.

What's the market actually paying for your role right now? That's the number that tells you whether you're underpaid relative to peers, and our companion post on junior developer salaries in the Philippines breaks down the documented ranges (local company, BPO/outsourcing, and direct remote-foreign employer markets pay very differently, so know which one you're in before you anchor to a number).

What's a typical annual increase budget in the Philippines right now? According to WTW's 2026 Salary Budget Planning Report, a survey of 344 Philippine organizations conducted between April and June 2025, Philippine employers projected a median salary increase budget of 5.5% for 2026, slightly up from the 5.3% actual average increase companies gave in 2025. Nearly half of those surveyed employers (47.8%) said they'd lowered their 2026 salary budgets due to anticipated economic pressure. That 5.5% figure is a useful sanity check for what a routine, no-drama annual adjustment looks like across a typical company; it is not a ceiling if you're making a case based on a market-rate gap or a clear scope increase, and it's a survey average across all roles and seniority levels, not a developer-specific or junior-specific number.

Those two numbers can conflict, and that's fine. If market data says similar roles pay 20% more than you're making, a request anchored to the market gap, not a routine 5.5% bump, is the more honest ask, and you should say so explicitly rather than let your manager assume you're asking for a standard increase.

#What should I bring to the conversation?

Come with specifics, not a general sense that you've been working hard:

• A short list of shipped work, turned into a measurable claim. The pattern is action → result: not "worked on the signup form," but "rebuilt the signup form, which cut drop-off from X% to Y%" or "this is now handling every new signup, about N a week." If you don't have a number for something you shipped, a before/after (page load time, error rate, manual steps removed) usually works even without a formal metrics dashboard. Two or three of these beat a long list of vague tasks. If you don't have a portfolio of this yet, our guide on building a developer portfolio with no experience covers how to document work like this as you go, before you need it for a conversation like this one.
• One market-data number, sourced, not guessed. Name where it came from.
• A specific target figure or range, not "more" or "market rate." Vague asks get vague answers.
• A written note of any responsibilities you picked up that weren't in your original job description, since scope creep without a pay adjustment is one of the more legitimate individual cases for a raise outside of a scheduled review.

Skip the parts that don't actually help your case: tenure alone ("I've been here a year"), other people's salaries, and personal financial pressure. They're not disqualifying to mention once in passing, but they shouldn't be the argument.

#What exactly do I say?

Here's a script you can adapt for an in-person or video conversation. Say it in your own words rather than reading it verbatim, a memorized script reads as stiff in person.

I'd like to talk about my compensation. Since [starting date / last
adjustment], I've [shipped feature X, fixed Y, taken on Z responsibility].
Based on what I'm seeing for [role] at [type of company] in the
Philippines, I think a fair adjustment is closer to [specific number
or range]. Is there room to move toward that?

If your workplace culture leans more indirect, and many PH offices do, you can soften the opening without losing the substance:

Do you have a few minutes this week to talk about my role and
compensation? I've taken on [specifics] since [date], and I'd like
to understand where there's room to revisit my current pay.

Both versions do the same job: name the timeframe, name the specific contribution, name a number or ask to discuss one. The soft version buys you a scheduling conversation; you still need the specifics and the number when the actual conversation happens.

If email is your only practical channel (remote-first company, manager in a different time zone), keep it to three short paragraphs: what you've done, what you're asking for, and a request to talk live if they want more context. Don't negotiate the actual number over email if you can help it; get a call scheduled instead.

#What if my manager says no?

A "no" isn't the end of the conversation if you handle it right:

• Ask what would need to be true for a "yes" next time, and get it specific: a metric, a milestone, a timeframe. "Let's revisit in Q2" without a specific bar attached is easy for both of you to forget.
• It's reasonable to counter once, professionally, if the number offered is well below what you researched. Pushing a second or third time on the same conversation usually costs more goodwill than it's worth.
• Ask about non-salary compensation if the budget genuinely isn't there: a training budget, better equipment, a flexible schedule, or a title change that helps your next job search, even if the peso number doesn't move this cycle.
• If the gap is large and structural (you're being paid well under documented market rate with no real path to close it), that's a legitimate reason to start interviewing elsewhere rather than keep re-asking the same employer. Changing employers is, in practice, one of the fastest ways to correct an underpaid starting offer, since a new employer sets your pay against current market data rather than your history at the old one.

Whatever the outcome, get it in writing, even if it's just a follow-up email summarizing what was agreed. Verbal commitments about "we'll revisit this" have a way of quietly not happening without a paper trail.

#Frequently asked questions

#Can my employer legally refuse to give me any raise, ever?

Yes, as long as you're being paid at or above the applicable minimum wage and there's no contract, CBA, or established company practice obligating an increase. Raises above the statutory minimum are discretionary for private employers in the Philippines; there is no general law requiring annual increases.

#I'm still on probation. Should I wait to ask?

Generally yes. Probationary status is capped at six months under the Labor Code, and asking for a raise before you've been evaluated against the standards your employer set at hiring is unlikely to land well. Regularization itself, becoming a permanent employee at or after the six-month mark, is a more natural first checkpoint to raise the topic, especially if your pay doesn't already reflect regular status.

#What if I'm a freelancer or independent contractor instead of an employee?

Different playbook. None of the employee-specific protections here (minimum wage, wage distortion correction, regularization) apply to independent contractor arrangements. Our guide on freelance developer rates in the Philippines covers how to reset your rate with a client instead, which is a pricing conversation, not a labor-law one.

#Does DOLE get involved in individual raise requests?

Not in the sense of ordering your employer to give you a personal raise. DOLE's involvement centers on minimum wage compliance and wage distortion disputes, not case-by-case merit increases. If you believe your employer is violating actual wage law (paying under minimum wage, withholding statutory benefits), you can call the DOLE hotline at 1349 or file through DOLE's online compliance portal; that's a different track from a normal negotiation conversation with your manager.

#Is it better to ask in person or over chat/email?

In person or on a video call, when you can manage it. A written request is fine as an opener to get the conversation scheduled, but the actual negotiation, where you can read the room and respond to pushback in real time, goes better live than over async text.

#How much of a raise is realistic to ask for as a junior developer?

There's no single right number; it depends on whether you're correcting a below-market starting offer (which can reasonably justify asking for significantly more than a routine annual bump) or asking for a standard yearly adjustment (where a Philippine-wide 2026 survey found employers budgeting a median 5.5% increase). Bring your own market-rate research, from documented junior developer salary ranges or a source specific to your city and market, rather than picking a percentage out of the air.

#Before you ask, make sure you have something to point to

A raise conversation goes better when you can point at real, shipped work instead of a general sense that you've been busy. If you're early enough in your career that you don't have that list yet, our Ship Your First Project challenge (disclosure: that's our own program) is built specifically to get you a deployed, demoable project in a short, structured sprint, exactly the kind of concrete evidence this whole conversation runs on.

#Sources

• Tolentino: P60 NCR wage hike in full effect today, Department of Labor and Employment, accessed September 2026
• Salary Increase Rights for Non-Union Employees in the Philippines, Respicio & Co.
• Mandatory Salary Increase Laws for Employees in the Philippines, Respicio & Co.
• Regularization After Six Months of Employment and Contract Renewals, Respicio & Co.
• Book Three, Labor Code of the Philippines (Presidential Decree No. 442, as amended), Article 124 on wage distortion, ChanRobles Law Library
• Salary increases in Philippines expected to remain stable amidst global uncertainties at 5.5% in 2026, WTW, July 2025
• Contact Us, Department of Labor and Employment (1349 hotline)
• How To Ask for a Raise (A Guide With Script Examples), Indeed Career Guide
• How to Negotiate for Raises and Promotions, LeanIn.org