# Speakers (4): Ingrid_Example, Walter_Example, Nadia_Example, Joon_Example
[00:00:05] Walter_Example: Okay, let's start. Same format as always, status round first, then budget, then team stuff. Nadia, you're up.
[00:00:14] Nadia_Example: Thanks. So the mobile wallet work is on track. I finished the sandbox testing for the first wallet provider on Monday, and this week I'm going to finish the second provider integration and hand it to QA by Thursday. I'll also update the runbook for the provisioning errors, since support keeps escalating those to us.
[00:00:40] Walter_Example: Good. Is QA staffed for that?
[00:00:44] Nadia_Example: Mostly, Joon's covering some of it.
[00:00:47] Joon_Example: Yeah, I can take the regression pass, it's maybe a day of work.
[00:00:52] Walter_Example: Great. Ingrid, go ahead.
[00:00:55] Ingrid_Example: Okay, so a lot happened this week, bear with me. The big one is that the card tokenization service went live on Tuesday, and so far the error rate has stayed under the threshold we agreed, so that part is done and I'm not going to talk about it more. We also closed out the accessibility audit findings from last month, all eleven of them, and Joon did most of the heavy lifting there. Going forward, the first thing on my plate is the refund flow: I will write the design doc for partial refunds by next Wednesday and circulate it to this group before the review. Second, I'm going to schedule the threat modeling session with the security team for the week after, because we can't launch the new checkout without their sign-off. Third, and this one is overdue, I'll migrate the remaining merchant webhooks off the legacy queue before the end of the month, there are about forty of them left. And finally I will set up the weekly metrics email for Walter's staff meeting, so he doesn't have to chase me for numbers every Monday. That's it from me for now, the money questions can wait for the budget section.
[00:02:05] Walter_Example: That's a lot. On the webhooks, is forty realistic by the end of the month?
[00:02:12] Ingrid_Example: I think so, the last batch took about a week and it was bigger.
[00:02:20] Joon_Example: I can help there if it slips, I know that queue pretty well.
[00:02:27] Walter_Example: Okay, good. Quick one on Thursday's incident before we move on.
[00:02:31] Ingrid_Example: Right, so on Thursday's incident, we already rolled back the bad config, wrote up the postmortem, and closed the ticket with support, so there's nothing left to do on that one.
[00:02:48] Walter_Example: Perfect. Nadia, can you make sure the postmortem gets shared in the engineering newsletter?
[00:02:55] Nadia_Example: Yep, I'll send it to the newsletter folks today.
[00:03:00] Walter_Example: Okay, budget. Ingrid, I think this one's yours too.
[00:03:04] Ingrid_Example: Right, the budget stuff. So last quarter we came in about six percent under on infrastructure, mostly because the reserved instances finally kicked in, and finance already signed off on carrying that over, so no action there. The fraud vendor contract is the open question. I talked to their account team on Monday and they confirmed the price increase is real, twelve percent at renewal. So here's what I'm going to do. I'll put together a comparison of the two alternative fraud vendors, cost and false positive rates, and have it to Walter by the fifteenth. I'm also going to ask procurement to extend the current contract by one quarter, so we aren't negotiating with a gun to our head, and I'll send that request today. And I'll book a demo with the second vendor, the one Nadia recommended, sometime in the next two weeks. If none of them work out we might end up building the rules engine ourselves someday, but honestly that's not a real plan yet, just a thought.
[00:04:05] Walter_Example: Twelve percent is a lot. Do we know what the other two charge?
[00:04:10] Nadia_Example: Roughly. The one I recommended was cheaper last year, but that was at a smaller volume.
[00:04:18] Walter_Example: Okay. We could also consider moving fraud scoring in house at some point, but let's not go there today.
[00:04:26] Joon_Example: Agreed, that's a whole team's worth of work.
[00:04:30] Walter_Example: Alright, team stuff. Before we get to hiring, I'll send out the updated on-call rotation this afternoon, it changes starting next week.
[00:04:40] Joon_Example: Does that include the holiday weeks?
[00:04:43] Walter_Example: Not yet, I'll do the holidays separately.
[00:04:46] Ingrid_Example: Last thing from me, on the team side. We finished the interview loop for the senior backend role, we made an offer on Friday and she accepted, so she starts on the third. To get ready for that, I will pull together an onboarding plan for her first two weeks, including who she shadows on which days. I'm also going to set her up with Joon as her mentor for the first month, he already said yes when I asked, so I'll let her know before her start date. Separately, I'll run the quarterly career conversations with each of you before the end of the month, so expect a calendar invite from me this week. Oh, and we were talking about maybe doing an offsite in the spring, that's just an idea for now, nothing's booked.
[00:05:35] Walter_Example: Great news on the hire. Joon, thanks for taking that on.
[00:05:40] Joon_Example: Happy to.
[00:05:42] Nadia_Example: Should we do a welcome lunch her first week?
[00:05:46] Walter_Example: Sure, let's figure out a day later. Okay, that's time, thanks everyone.
[00:05:53] Ingrid_Example: Thanks, all.
