NAPA Auto Parts is seeking a fully remote Ruby on Rails developer. You’ll be working on a smaller team that is rapidly building a new division within NAPA Auto Parts - think startup inside BigCo. We are seeking someone who will take equal pride in our streamlined workflow, agile development, creative approaches, and entrepreneurial spirit.
This position calls for a self-motivated person capable of independent work (though code review and pairing will happen regularly, you'll be on your own most days). The role involves back-end automation of workflows & data exchanges using various APIs and file formats - JSON, XML, SOAP, EDI, CSV, etc. You’ll also assist in building and enhancing many of our consumer-facing & support system Rails apps.
Genuine Parts Company (NAPA Auto Parts) is seeking a fully remote Ruby on Rails developer. You’ll be working on a smaller team that is rapidly building a new division within NAPA Auto Parts - think startup inside BigCo. We are seeking someone who will take equal pride in our streamlined workflow, agile development, creative approaches, and entrepreneurial spirit.
This position calls for a self-motivated person capable of independent work (though code review and pairing will happen regularly, you'll be on your own most days). The role involves back-end automation of workflows & data exchanges using various APIs and file formats - JSON, XML, SOAP, EDI, CSV, etc. You’ll also assist in building and enhancing many of our consumer-facing & support system Rails apps.
Ah, OK; well that paints a bit of a different picture: driving through some construction site which might have been in who knows what sort of disarray at the time, without proper roads and hazards/obstacles and whatnot.
Your comment reminded me of a Doug DeMuro article where he did just that! "In other words: the Range Rover is a highly capable, brilliant off-roading vehicle with a lot of highly capable, brilliant off-roading components, assuming that you have a comprehensive CarMax warranty to keep these components working properly."
This may work nicely for a subscription business where you have 2 weeks to identify problematic orders. But what about everyone else? Should we silently fail on orders where a customer accidentally mistyped their CC#? Imagine all the extra work involved when you could have had them fix it on the spot.
Mistyped card numbers can be identified client-side (CC numbers have a checksum digit). If the number is valid, but the transaction is declined, then fail silently (and possibly send a failure email after manual review of the transaction)
It could also be declined because of mistyped expiry date or address or name. Or simply declined because the customer is over their credit limit. In all of these cases, timely feedback is useful for genuine customers.
Which is why it says in the article that these countermeasures almost always come at a cost to customers as well. It is a trade off.
In some instances it is worth it to make the experience marginally worse for customers because the savings by preventing a percentage of fraud are so large.
Nonetheless, this doesn't contradict the "failing silently" for chargebacks. It's not fraud if they enter the data poorly or there's no credit left so the charge is never made.
Completely agree with fweespee_ch. Major CC processors such as Authorize.net, Braintree, etc. offer fraud protection measures but in our experience they do very little to prevent even a remotely-capable fraudster. Typical features offered are IP Velocity & regional IP (useless when the fraudsters spin up thousands of amazon servers), # of transactions per hour (not too helpful when your business already does hundreds/thousands of transactions a day), CVV and AVS credit-card response codes (ends up blocking more legitimate orders than fakes and the fraudsters typically already have this information anyway), etc.
There seems to be a huge conflict of interest here: as card processors slap you with an extra chargeback fee for the fraudulent transactions (in addition to the amount they take back anyway) it's difficult to believe that they would work very hard to help you avoid this.
NAPA Auto Parts is seeking a fully remote Ruby on Rails developer. You’ll be working on a smaller team that is rapidly building a new division within NAPA Auto Parts - think startup inside BigCo. We are seeking someone who will take equal pride in our streamlined workflow, agile development, creative approaches, and entrepreneurial spirit.
This position calls for a self-motivated person capable of independent work (though code review and pairing will happen regularly, you'll be on your own most days). The role involves back-end automation of workflows & data exchanges using various APIs and file formats - JSON, XML, SOAP, EDI, CSV, etc. You’ll also assist in building and enhancing many of our consumer-facing & support system Rails apps.
Tech Stack: Rails, React, Redux, Postgres, Redis, Ubuntu, Gitlab, Chef, Sendgrid, Klaviyo, Twilio, Braintree
Apply here: https://jobs.jobvite.com/careers/gpc/job/oi6Ghfw5