We’re operating in a competitive space dominated by legacy incumbents.
Large banking and card institutions like Chase and Wells Fargo are slow-moving, which gives us an advantage as a small team to iterate and ship new products much faster. For example, while debit cards typically take 12 months to go live, we can do it in 3.5 months. Our agility as a small startup allows us to push code to production several times a day and make decisions without bureaucracy and red tape.
Our identity is tied with what we build.
Our primary goal is to make products that bring real benefits to the lives of our customers. While most finance-related products bring dread to consumers, we’re actively working to break that stigma and put our users’ experiences first. If you’d be interested in a better spending experience, we’re happy to share an invitation to check out our invite-only product! (Email [email protected] for access to Point.)
As we build our team, we’re seeking detail-oriented engineers who go out of their way to not only ensure that our products’ UI matches designs in Zeplin pixel-for-pixel, but also that our backend processes are crafted in a beautiful and elegant manner that optimizes user experience.
Each member of our founding team comes from a product-focused background:
- Patrick (Co-Founder and CEO) was previously a director of product at Metal Pay and founder/CEO of Crumbs.
- Sid (Co-Founder and Chief Designer) was previously a senior interface designer at Apple and Mercedes Benz.
- Kenan (Co-Founder and CTO) was previously a lead full-stack engineer at Metal Pay, Swipe Labs, Motiv, and the first mobile engineer at The RealReal.
- Clio (first Backend Engineer) was previously an engineer and data scientist at Acorns.
- Pete (Senior Backend Engineer) was previously a senior engineer at Merkle Data and Sunsama.
- Andrew (Director of BD & Ops) was previously building partnerships at American Express and HotelTonight.
Engineers (specifically mobile devs) work very closely with design.
Our Chief Designer, Sid, co-founded Point after working at Apple as an interface designer. Sid works alongside our engineers to brainstorm solutions to different user experience problems and ensure our app always matches up with mockups.
Banking and payment cards don’t have a reputation of providing great user experiences. We believe that in this regulated and commoditized space, design has the potential to be a key differentiator.
The physical debit cards serve as a canvas for us to lean into thoughtful design. As a result, our customers can express themselves with a more creative way to pay. This is why we collaborated with a talented Chicago-based artist, Laura Berger, to develop two of our unique card designs that stand out from the crowd (or on any restaurant table when the bill arrives) and spark conversation.
Candid feedback and criticism is always useful.
Since we are still a small team, we hold one another accountable for the responsibilities we’ve been assigned. We encourage 1:1s to be a safe space to discuss anything that might be bothering you, and we all sync up each morning at 9:45 am for a 10-minute standup where we share our progress from the prior day, today’s goal, and any blockers we are facing.
Communication across departments is an open dialogue – since our team is small, engineers directly reach out to Sid, our Chief Designer, or Andrew, our Director of Ops, if there are questions. Similarly, other team members feel comfortable reaching out to engineers whenever they need details about an integration or want to request a feature. We all work collaboratively and information flows fluidly in all directions.
We’re building secure, robust, and scalable infrastructure while rapidly delivering features.
Our CTO, Kenan, has spent his entire career building early stage startups from the ground up. He has a strong focus on building infrastructure to scale and support an amazing user experience without compromising on security and speed. Kenan now brings this expertise to Point. As we build our engineering team, we’re committed to leveraging newer technologies to rapidly iterate and scale while solving complex problems. This gives us a competitive advantage over incumbents, since traditional financial services companies are known to run on mainframes and take many months and millions of dollars to build a single feature. For example, Wells Fargo spent $500M to develop their mobile app, while we have been able to build similar functionality in a third of the time for less than 1 percent of the cost.
When we think about solving problems, we consider more than just the technical implications of the implementation. We think deeply about how engineering can make the product deliver the best user experience by designing best in class APIs to correspond to our UX design. While there are certainly confines in which we need to operate, our team finds clever solutions to build around potential bottlenecks. Since we are in the financial services space, it’s very important for us to also maintain high availability and reliability. We are methodical in our approach to choosing the technology we want to leverage when we need to make major changes to the infrastructure.
In order to focus on our core competencies, we are deliberate about future proofing our technology throughout each iteration. For example, we leverage GraphQL as it enables us to create APIs at a much faster pace, has a self-documented API, is supported by large organizations who require reliability, enables us to test out the API in a “Playground” without having to set up a client, and allows for extensibility as we build out more functionality. These are the kinds of considerations we take into account when deciding which technology to adopt. We also evaluate the feasibility of maintaining the infrastructure with the small and nimble team we currently have.
Actively Practices Inclusion
Diverse backgrounds build better products.
We welcome everybody and do not discriminate based on gender, race, what school you attended, or what big company you worked at previously. We are actively seeking diversity of experience in all facets to enhance our company so we’re able to emphatically serve our users. We are currently a team of mostly men and fully acknowledge this must change in order to build the strongest culture and best products for our customers.
What matters most to us is that you are the right person for the job and can take ownership for the product you’re working on. Your GitHub contributions, previous work, and ability to contribute a ton of value to Point is what’s most important.
If you’re interested in meeting us or learning more about our vision for the future, we’d love to meet you. You can view our open roles here!
Committed to Personal Growth
It’s important that we’re all continuously improving.
As a small team in a high-growth business environment, it’s important that everyone on the team is bettering themselves both in and out of the office. A mentally intense workday should be complemented by recharging outside the office, too. That’s why we provide a monthly wellness stipend ($50) to be spent however you’d like (e.g. gym, fitness classes, meditation). We also provide a monthly education stipend ($25) for continuous learning to be used on books or courses. And if there is a conference or seminar that’s relevant to what you’re working on – we’ll cover the cost! To round it out, we don’t want getting to and from work to be stressful, which is why we provide monthly commuting benefits ($100) so you only start sweating once you get to that fitness class ;)
We want what we build to be scalable and ensure that our tech is future proof and deliver best results by not using brittle approaches.
An example of how we leverage cutting-edge tech is by leveraging distributed messaging queues and our team is vertically integrated.
We build highly available and scalable backend infrastructure with a focus on performance in order to provide the best possible user experience to our products. In order to achieve this, we’re leveraging the latest and greatest technologies of a modern tech stack. Some examples of these technologies include: AWS Lambda, Apollo GraphQL, AWS Kinesis Streams, Prisma ORM, and AWS Aurora Postgres. We have a distributed architecture using a mix of point-to-point API requests between different lambda instances as well as using Kinesis Streams as our distributed messaging queue with resilient retry mechanisms from our integrations.
Some exciting projects that we’ll be working on in the future are building out infrastructure to become a featured bank for 3rd-party integrations, building a more flexible rewards pipeline, implementing systems which will allow us to offer a full suite of banking-related products and breaking out our services into a true microservice infrastructure.