u/dsbsoni

Had this conversation three times this week so figured I'd just post it here.

I talk to people in this space regularly and I notice a pattern. Someone gets their first Guidewire project, works hard, gets comfortable and then just stops. Not because they are lazy. Just because the project keeps them busy enough that upskilling feels like extra work on top of already full days.

And I get it. After a long sprint you just want to breathe.

But the insurance market outside this community is rough right now. 54,000 jobs cut since January 2025. UnitedHealthcare, Cigna, Aetna, BCBS all laying off people with solid experience. Bureau of Labor Statistics numbers, go look it up. These are not junior people getting cut. Some of them have 10, 15 years in the industry.

And Guidewire demand has not slowed down once through all of it.

The people getting laid off have the same insurance knowledge most of us have. The domain experience is the same. They just do not have Guidewire on their resume. That one thing is the difference right now.

So if you are already in this space you are sitting in a genuinely good position. But it is easy to underuse that by just staying in your lane on the current project and not pushing further.

Are you going deeper into configuration? Picking up a center you have not worked in yet? Exploring integrations or Guidewire cloud? Or honestly just heads down on current project work and nothing beyond that right now?

No right or wrong answer. Just curious to know where people are at.

Stop applying on job portals for Guidewire roles. Do this instead.

If you have solid Guidewire experience and still not getting callbacks, the problem is not your resume.

The problem is where you are looking.

Job portals are a black hole for niche skills like ours. You are sitting in a pile with 800 other applicants and hoping an algorithm picks you. That is not a strategy.

Here is what actually works.

Open LinkedIn. Search your exact role. Guidewire QA, Guidewire BA, whatever it is. Now hit the Posts tab at the top. Not jobs. Posts.

Recruiters who are actively hiring right now post there. Many of them drop their email directly in the post. Some ask for resumes in DMs. These are live, warm opportunities that most people completely miss because they are stuck refreshing job portals.

Reach out directly. Email them. No reply in 3 days, follow up. Then follow up again. Sounds simple but almost nobody does this and it is the whole game.

Calling works too if they leave a number. WhatsApp if no answer.

On LinkedIn, connection request first, then message. Never cold DM out of nowhere.

You are not competing with 800 people anymore. You are the one person who actually reached out.

30 minutes today. 10 recruiters. Just try it.

Curious what is working for people here right now. Try this method, and share your experience. Also, comment below about your strategy, always good to know what is actually working across different markets.

Guidewire jobs in 2026 - am I wrong to think this domain is more layoff proof than the rest of tech? Genuine question.

I have been seeing the layoff anxiety building everywhere. So I actually pulled the numbers.

78,557 tech workers laid off from January to April 2026. 48% of those cuts directly because of AI. Meta, Microsoft, Oracle all cutting thousands right now.

But when I looked at Guidewire specifically the picture looks completely different.

India - 8 to 9 LPA average. Bangalore seniors at 20 to 30 LPA. 100+ active openings on Glassdoor right now.

USA - senior certified roles at $110,000 to $145,000. Companies paying for your certification after hiring because they simply cannot find enough people.

Canada - CAD 40 to 60 per hour mid level. Toronto and Ontario actively hiring right now.

And I think I know why.

Nobody cancels health insurance during a recession. Car insurance is legally mandatory. Home insurance is required by every mortgage lender. The premiums keep coming into insurance companies regardless of what the economy does.

On top of that every major insurer right now is in the middle of migrating to Guidewire Cloud. That is years of project work that cannot be paused.

While 2026 layoffs are hitting even specialized senior roles in other domains, Guidewire seems to be holding because the work needs deep insurance domain knowledge that AI cannot replicate quickly.

That is my read of the data anyway.

Am I missing something? Would love to hear from people actually in the market right now. Drop your thoughts in the comments.

Been thinking about this for a while and wanted to get some thoughts from people here.

You have been testing PolicyCenter for months or years. You know every screen. You know which fields break and why. You know the workflows better than half the devs on the project honestly.

And yet most QA folks I see are still just raising defects in Jira and waiting for someone else to fix them. Same sprint. Same cycle. Same salary.

Now I am not saying QA is bad at all. I am just saying there is something most of us are not seeing.

Fresh developers join a Guidewire project and spend the first two or three months just trying to figure out what PolicyCenter even does. What a submission is. How coverages work. Why changing one field breaks three other things.

You already know all of that. You lived it.

The only thing standing between a QA role and a developer role in Guidewire is Gosu. That is genuinely it. And Gosu is not scary. You are not doing data structures. You are not cracking leetcode. You are reading simple rules, understanding how a validation is written, maybe changing a few lines here and there.

30 minutes a day for a few weeks and you can read and write basic Gosu. That is the whole jump.

PolicyCenter devs who actually understand the insurance domain are very hard to find right now. That combination pays 40 to 60 percent more than QA in most cases.

You already have the hard part covered. Gosu is just the last piece.

Wanted to hear what people here think. Has anyone here made this move or considered it? And if any QA folks want to know where to start with Gosu just DM me or drop a comment, happy to share what I know.

Been noticing this question come up a lot here, specially from Guidewire Manual QA's, how to upskill further? I say go for Guidewire Dev skill instead of automation (selenium, playwright) one, for better n safe future.

So for this I recently connected with a trainer who works in Guidewire professionally, not someone who put together a course from documentation, someone actually working in the domain. He is opening a new batch next week and doing a free Guidewire Dev Training demo first so people can decide if it is worth it before committing.

Demo is this Saturday 26th April, 8 PM IST / 10:30 AM EST.

Good for people coming from Java, Selenium, Manual QA or any IT background. Also relevant if you are already in Guidewire QA and want to move into development.

Small batch, limited seats.

If you are interested or want the demo link, drop a comment or DM me. If you cannot make the 26th, DM me anyway and I will try to arrange a separate slot.

Okay I need to get this off my chest because I have never posted about this before.

My heart still jumps when a manager calls me for an unexpected meeting. Even now. Even after spending years working in Guidewire.

Took me a long time to figure out why.

Early in my career I had a manager who would shout at me in front of the whole team. Not once or twice. It was just... regular. Normal Tuesday behaviour for him.

5pm. New task appears from nowhere. No context. No discussion. Just "this needs to be done before you leave."

He knew where I was at every moment. Who I was talking to. How long I had been away from my desk. I used to plan my bathroom breaks around his schedule. I am not even joking.

And I never said anything.

Because honestly? I thought it was my fault.

I convinced myself I was lazy. Unproductive. Not cut out for this kind of work. I thought Guidewire projects are just like this. High pressure. Demanding clients. Crazy timelines. Everyone else is managing it so why can't I.

I carried that thought for years without questioning it.

Eventually I moved to a better project. Good team. Decent manager. Completely different environment.

First week. Manager sends me a message. "Hey can we catch up quickly?"

My stomach dropped. Hands got a little cold. I spent the next ten minutes convincing myself I had done something wrong.

It was a general check in. Literally nothing.

That is when it clicked for me.

What that manager did in my early years was not normal. I just had no reference point back then so I assumed it was me.

It was not me. It was just a person who had authority and no idea how to use it without making someone feel small.

Anyway. If anyone here is currently in a toxic Guidewire engagement or a bad team situation, a few things that actually helped me:

Write stuff down. Dates, what happened, exact words if you remember them. Not to escalate immediately. Just so your own head stays clear when they start making you doubt yourself.

Find one person on the project you can be honest with. Just one. It makes a bigger difference than you think.

And please quietly keep your options open. The Guidewire talent market is genuinely active right now. You do not have to stay in a place that is grinding you down. Update your profile. Reply to recruiters. Just keep a window open.

No go-live is worth your mental health. I promise you the client will survive.

One more thing for anyone who already left but still carries that anxiety into new roles.

Before your next manager call, try this. Breathe in for 4 counts. Hold for 4. Out for 4. Hold for 4. Three rounds.

Box breathing. Special forces use it before high stress situations. Sounds simple. Works embarrassingly well. Took me way too long to find this.

That feeling you get before meetings, the need to over explain everything, the guilt when you log off on time. That is not your personality.

It is just a scar from something that should never have happened to you.

It gets better. Genuinely.

Has anyone else been through something like this in a Guidewire project or consulting role? Would be good to know I am not the only one because this industry does not talk about it nearly enough.

No bad earnings. No product failure. No internal crisis.

Just one announcement from Anthropic, a completely different company, and Guidewire bled.

Anthropic launched something called Managed Agents. Simple way to understand it: imagine an AI that can handle long, complex tasks completely on its own. No human checking in. It runs, pauses, restarts, and finishes the job independently.

Investors saw that and had one thought. Why would insurance companies pay expensive software subscriptions if AI can just do the work directly?

That fear wiped 5% one day. Then 8% the next.

Two days. Two drops. Zero mistakes from Guidewire.

---

Here is the thing though. Guidewire itself is nowhere near dead.

570 insurance companies across 43 countries run on it. They just crossed $1.1 billion in recurring revenue, growing 22% year over year. The platform is not going anywhere.

But the way people work inside it is changing fast.

The people who only know HOW to follow a Guidewire process will feel this pressure. The people who understand WHY the platform works the way it does, the business logic, the insurance reasoning behind it, will become harder to replace, not easier.

AI is not the threat here. Staying comfortable is.

---

Curious, for those of you working in Guidewire, what is one thing you are actively doing this year to stay sharp in this ecosystem?

Genuinely asking. Drop it below.