Procter & Gamble · Primly Community

Procter & Gamble software engineer interview process, full loop: what I went through in early 2026

corp_refugee · 6 replies

Finished the P&G SWE loop about six weeks ago and wanted to write up the full picture because when I was prepping I could barely find anything recent.

For context: mid-level role, 6 YOE, applied through LinkedIn for a position on their digital platforms team in Cincinnati. Not remote.

Timeline: Application to recruiter call: 12 days. Recruiter call to online assessment: about a week. OA results to interviews: two weeks. Total: roughly five weeks start to finish, which felt faster than I expected.

The stages: Recruiter phone screen (30 min). Standard background stuff, nothing technical. Online assessment. HackerRank platform, two coding problems, 75 minutes. Details in another post. Two back-to-back video interviews. Each was 45 minutes and had a mix of coding and behavioral. Not what I expected, honestly. I thought it'd be either/or. Final virtual onsite: four rounds, all on the same day, spread across morning/afternoon. One was purely behavioral, one had a system design component, two were behavioral/technical combos.

The interviewers were all friendly. P&G has a reputation for being a bit stiff corporate-wise but the people I talked to were genuine. One of them was a manager who'd been there 11 years and actually seemed to like it.

What tripped me up: I underestimated how much behavioral weight they put on everything. Even the coding rounds had a 15-minute behavioral tail. If you go in just grinding LeetCode you'll get caught off guard.

I prepped my STAR stories pretty carefully because someone online mentioned they ask a lot of "tell me about a time" questions specifically around cross-functional collaboration. That was real. Three of the four final rounds touched it.

Outcome: Got an offer. Negotiated up a bit from initial. If anyone wants specifics on comp, separate post coming.

6 replies

ops_omar

This is super helpful, thank you. Did they give you any coding problem hints during the technical rounds or was it strictly no help from the interviewer?

backend_bekah

Interviewers were pretty hands-off on the live coding. One asked a clarifying question to prompt me when I got stuck, more like a nudge than actual help. I'd say: ask your own clarifying questions upfront, that tends to open a dialogue.

market_realist

The behavioral-in-every-round thing is real across most CPG tech orgs. P&G especially seems to weight culture fit heavily. Good to know it hasn't changed.

veteran_vance

Is P&G a realistic target for someone coming from a non-traditional background? I have 5 years in systems administration in the military and I'm transitioning now.

backend_bekah

I'd say worth a shot, especially for ops-adjacent SWE roles. Your reliability and systems ops background could actually resonate well with their infrastructure teams. Tailor your resume to highlight any automation or scripting work.

sre_sol

Five weeks is honestly pretty reasonable for a big CPG company. I've seen slower at pure tech startups somehow. The behavioral-plus-technical combo format is a bit unusual. Thanks for the warning.