giw-gen5 console

Q. What's pulling you toward this role — what caught your eye about it?

That's a solid fit — knowing the stack well but wanting the bigger stage.

A. Honestly, it’s the mix of scale and ownership. I’ve spent a lot of time on payments and data pipelines, but the idea of building something that handles that kind of traffic, and having real ownership over it, really appeals to me. Plus, the team’s focus on Go — that’s my bread and butter. I’ve been doing it for a while, and I like that I’d be working with a stack I already know well, but on a much bigger stage.

Q. What's one thing you're actively trying to get better at in your work, and what have you done about it lately?

I hear you—leadership's a whole different muscle than coding.

A. I’ve been trying to get better at leading — not just technically, but really guiding people. Like, I used to focus on just getting the code right, but now I’m more conscious of helping the team move in the same direction. Lately, I’ve been taking on more mentorship, doing code reviews with a focus on explaining the why, not just the what. And I’ve been reading up on team dynamics, trying to be more deliberate about how I communicate. It’s a work in progress, honestly.

Q. You mentioned taking on more mentorship—can you walk me through a specific moment when you gave someone feedback and then saw them actually change what they did?

That's a nice moment to witness.

A. Yeah, there was this one junior engineer — let me think. We were working on a Go service, and they kept writing really long functions. I gave them feedback a few times, but it wasn't until I sat down and walked through a specific function with them, showing how breaking it up would make testing easier, that it clicked. Next sprint, they came back with a refactor that was actually pretty clean. I mean, they still had a ways to go, but the shift was real. It felt good to see that.

Q. On the payments migration, I imagine you hit some friction with the legacy provider or internally — tell me about one disagreement you had with a teammate during that project and what you personally did.

That's a really thoughtful way to handle it—showing the scenarios instead of just pushing back.

A. Oh, yeah. There was this one disagreement about how much we should batch transactions during the cutover. My teammate — I think he was on the data team — wanted this massive batch to save time, but I was worried about the risk if something failed mid-way, because rolling back would be a nightmare. I pushed back, but I didn't just say no. I actually sketched out the failure scenarios and walked him through them. We ended up going with smaller batches, which was slower, but way safer. It was more convincing than just arguing, I guess.

Q. Where do you want your work to take you in the next couple years — what's something you want to be doing that you can't do today?

That's a clear direction to be aiming at.

A. I want to get to a point where I'm not just owning a service, but really shaping the architecture and roadmap for a whole platform. Right now, I'm still pretty deep in the weeds — which I like — but I want to be the person who's thinking about trade-offs across systems, not just within a single codebase. Ultimately, I'd love to be a staff-level engineer, someone the team looks to for direction on big technical bets. That's the path I'm aiming for.

Q. You mentioned shaping architecture and roadmap—what's a specific skill or kind of work you feel you need to develop to get there, and how does this role help you build that?

That makes sense — strategic thinking is a tough thing to build without the right exposure.

A. I think the biggest gap for me is strategic thinking — being able to look at the whole system and understand how a decision in one service ripples through others. I've done it on a smaller scale, but not at the level of a complex platform. This role would help because I'd be working on a large-scale system where those trade-offs actually matter daily. I’d get exposure to how decisions are made at a higher level, and hopefully learn from the senior folks here. That’s something I can’t really get where I am now.

Q. Before we wrap up, what would you like to ask me about the role or the team?

Those are great questions — they show you're thinking about the real work.

A. I’d love to know more about the team’s current biggest technical challenge — is it scaling, or are you dealing with legacy systems you’re trying to move away from? Also, how does the team handle code review and mentorship, since that’s something I’m trying to get better at? And, I guess, what’s the onboarding like — how quickly would someone like me be expected to contribute meaningfully?