This job post is closed and the position is probably filled. Please do not apply. Work for Spreedly and want to re-open this job? Use the edit link in the email when you posted the job!
\nSpreedly is a small startup (25ish people... for now) that's growing. Our list of 'awesome functionality that real customers will pay us for if only we can get it implemented' is growing faster than we can check things off, and we need to immediately grow our team with an experienced engineer that can hop into a high-functioning, experienced team and start learning and contributing quickly.\n\nWhen you start at Spreedly (think first 6-12 months), you'll be spending 90%+ of your time working right on the product team building functionality for customers. Building product at Spreedly is somewhat unique in that our main product is a payments API used by other developers. So 'designing a UI' often means thinking through how you would want a given API to work if you were using it and 'adding a feature for a customer' often means working through how to securely enable a developer to do something interesting with a credit card number.\n\nOh, did we forget to mention that? We work with credit card data. Constantly. It's basically what we get paid to do, so that others don't have to. So thinking about security is a way of life at Spreedly, as is building sustainable processes to keep things safe, and our auditors happy.\n\nWhat we're looking for in a senior engineer is somebody who's not afraid to jump into a pretty complex technical problem and make sense of them. We regularly deal with the dark underbelly of software – think encryption, encoding, and security, all within the context of a distributed system. You don't have to be an expert in any of those aspects, but you shouldn't be intimidated by the thought of learning about them either.\n\nOnce you've gotten your feet under you and understand the domain well enough, we envision you being the technical lead for one aspect of our service. That means you can work with junior engineers and help them tackle the task at hand using pragmatic software practices. We don't want rockstars or ninjas. We need people that are good at their job while also elevating the people around them.\n\nWe are open to remote candidates, but with a few caveats. Currently our whole technical team is in the RDU area and works out of our office in downtown Durham two days a week, and from wherever we fancy the other three days a week. So while we are already operating in a remote-friendly way, and definitely see ourselves expanding our remote presence in the future, you would be the first engineer operating in a distributed fashion and we realize this involves additional burden. So, if you're remote, we would want to see previous experience operating as part of, and leading, a remote team, and a willingness to help us flesh out the nuances of having a hybrid working arrangement. If that sounds like you, please apply! \n\n#Salary and compensation\n
No salary data published by company so we estimated salary based on similar jobs related to Senior, Engineer, Developer, Digital Nomad, API and Junior jobs that are similar:\n\n
$65,000 — $125,000/year\n
\n\n#Benefits\n
๐ฐ 401(k)\n\n๐ Distributed team\n\nโฐ Async\n\n๐ค Vision insurance\n\n๐ฆท Dental insurance\n\n๐ Medical insurance\n\n๐ Unlimited vacation\n\n๐ Paid time off\n\n๐ 4 day workweek\n\n๐ฐ 401k matching\n\n๐ Company retreats\n\n๐ฌ Coworking budget\n\n๐ Learning budget\n\n๐ช Free gym membership\n\n๐ง Mental wellness budget\n\n๐ฅ Home office budget\n\n๐ฅง Pay in crypto\n\n๐ฅธ Pseudonymous\n\n๐ฐ Profit sharing\n\n๐ฐ Equity compensation\n\nโฌ๏ธ No whiteboard interview\n\n๐ No monitoring system\n\n๐ซ No politics at work\n\n๐ We hire old (and young)\n\n
# How do you apply?\n\nThis job post has been closed by the poster, which means they probably have enough applicants now. Please do not apply.