Jesse Spivak

At the point that we were like, you know, we can just do this in Java and Camel, we had wrapped our heads around the problem enough that we really felt like it wasn't hard anymore. And maybe that's what it takes.

At the point that we were like, you know, we can just do this in Java and Camel, we had wrapped our heads around the problem enough that we really felt like it wasn't hard anymore. And maybe that's what it takes.

Those are the proudest days.

Those are the proudest days.

That's interesting. The person who taught me how to code... one of the first pieces of advice that he gave me was that you should write a lot of code and throw a lot of code out. And that's how you'll get better at coding.

That's interesting. The person who taught me how to code... one of the first pieces of advice that he gave me was that you should write a lot of code and throw a lot of code out. And that's how you'll get better at coding.

Thankfully. Yeah, so we did a couple of things I think that helped us. So the first is, as John said, we were open about these things. We didn't try to hide that things weren't going as well as we had wanted them to. And I think that Ibotta has a pretty strong culture in the sense that We're not trying to throw people under the bus in engineering.

Thankfully. Yeah, so we did a couple of things I think that helped us. So the first is, as John said, we were open about these things. We didn't try to hide that things weren't going as well as we had wanted them to. And I think that Ibotta has a pretty strong culture in the sense that We're not trying to throw people under the bus in engineering.

If something crashes, it's not who's going to get fired. It's like, okay, how do we learn from this? This is a mistake that cost us some money. How do we make sure that that money is actually teaching us something? So that was part of it. And then I think also we did a good job of communicating to external stakeholders.

If something crashes, it's not who's going to get fired. It's like, okay, how do we learn from this? This is a mistake that cost us some money. How do we make sure that that money is actually teaching us something? So that was part of it. And then I think also we did a good job of communicating to external stakeholders.

We communicated to the finance team who were kind of one of the main consumers of the data that we were producing. and really went through in detail. Here's where we're at. Here's the timeline, like updating them. We were checking in with them all the time and just keeping expectations in line, I think really helped us out.

We communicated to the finance team who were kind of one of the main consumers of the data that we were producing. and really went through in detail. Here's where we're at. Here's the timeline, like updating them. We were checking in with them all the time and just keeping expectations in line, I think really helped us out.

So even though we delivered a little bit later than I think we thought we would at the onset of the project, because we were able to communicate that, we were not fired. And yeah, I mean, not only that, We've hired more people. We're still hiring.

So even though we delivered a little bit later than I think we thought we would at the onset of the project, because we were able to communicate that, we were not fired. And yeah, I mean, not only that, We've hired more people. We're still hiring.

And if you're thinking about getting into the mobile coupon space, there's a ton of really cool problems, even if you're not passionate about mobile coupons. And you might get to talk to me in the interview process, which will be fun.

And if you're thinking about getting into the mobile coupon space, there's a ton of really cool problems, even if you're not passionate about mobile coupons. And you might get to talk to me in the interview process, which will be fun.

Yeah, so maybe everybody has experience or a lot of folks have an experience in, let's just say, a not-mean-us-one interview, an interview that maybe is a little more hostile than we'd like.

Yeah, so maybe everybody has experience or a lot of folks have an experience in, let's just say, a not-mean-us-one interview, an interview that maybe is a little more hostile than we'd like.

And I think a lot of us have experienced kind of broken interviews where it feels more like the person on the other side of the table is trying to prove how much smarter they are or how much better they are at coding than I am. And that's not nice.

And I think a lot of us have experienced kind of broken interviews where it feels more like the person on the other side of the table is trying to prove how much smarter they are or how much better they are at coding than I am. And that's not nice.