This is a hybrid role, and we expect that you work from our Scottsdale, AZ office 1-2 times per week. We value the flexibility of remote work, but believe some of our best collaboration happens in person.

About Uplinq

We are an Arizona-based startup building software to automate bookkeeping and accounting for small businesses. This wasn’t always our plan. When we started Uplinq, we wanted to help small businesses work with acquirers/investors, survive loan due diligence, and use their financial data to make timely business decisions. We tried solving these problems directly to no avail and quickly realized they are all symptoms of a bigger problem: bookkeeping is hard, and SMBs hate doing it.

Since then we’ve been hard at work reinventing bookkeeping as a SaaS product. What we’ve built to date allows us to offer high-quality, real-time, and affordable bookkeeping to hundreds of small businesses. 

Our customers are dentists, restaurant owners, insurance agents, realtors - real people from all walks of life.

• Some tried to manage their books in QBO themselves and couldn’t keep up.
• Some paid a CPA firm too much for bookkeeping that only gets updated once a quarter.
• Some switched from companies like Bench and Pilot looking for better service.

We are a tight-knit team of about 35 CPAs, engineers, accounting specialists, tax preparers, product designers, and marketers. We support each other, communicate openly, have fun at work, and all believe in Uplinq’s mission to help real people run their businesses better.

About the Role

The engineering team is looking for a mid to senior level full-stack software engineer to build customer-facing and internal features with an emphasis on improving the scalability of our bookkeeping and tax products. An engineer in this role will solve high-impact business problems by directly communicating with stakeholders, writing quality software, and monitoring their work for impact once deployed. Our ideal candidate:

• has a proven track record of shipping high quality software
• has experience working with non-technical stakeholders
• is an excellent communicator
• is naturally curious
• (ideally) has experience with technologies in our stack (see below)

Here are some examples of projects that you could own in this role:

• build an invoice automation app for a large enterprise customer
• use LLMs to streamline the monthly review/close process for a customer’s books
• design tools to help our tax team track/request data from customers
• refactor our customer app home screen with updated designs

And here are some things we’ve recently shipped that we’re proud of:

• An auto-reconciliation tool consisting of
  • an algorithm for detecting account reconciliation issues
  • a view in our customer app that prompts users to upload PDF bank statements
  • an integration with a document processing vendor that extracts transactions from bank statements and deduplicates them to solve reconciliation issues
• tools for our onboarding team to track what customer data is missing after an onboarding and automatically request it from the customer.
• a refactor of our QBO integration that allows us to leverage our categorization AI for customers who still use Quickbooks.

Here are some designs we’ve built recently: https://www.figma.com/file/5SutmVaPpVd1PkE1ox8qPG/Uplinq-Public-Design-Samples?type=design&mode=design&t=EoIsg90ZMAgZCc5k-0

About Uplinq Engineering

Uplinq’s tech stack is built and maintained by three engineers:

• myself (CTO), a recovering EE PhD student with a previously exited startup
• a SWE and CS undergrad dropout who previously founded and exited a startup
• a SWE w/ a UCSD physics degree who jokes about rewriting our stack in Rust (is he joking?)

We’ve had help from other engineers for brief stints, but the three of us have been developing Uplinq since the beginning. Because of our size, we each own large portions of the system and routinely ship very impactful features. Our next team member will get to do the same.

Most of our development takes place in a typescript monorepo managed with pnpm workspaces. We call it updog. Here are some of the things you can find in updog:

• a customer-facing and internal web app both written in react with Next.js and tailwind CSS
• APIs with trpc
• AWS Lambda running Node for backend functionality / SSR
• an AWS Step Function or two
• a postgres database or two
• deployments & local dev with sst
• CICD with Bitbucket Pipelines
• unit tests with vitest
• APM with Datadog

Some earlier (but still well-loved) services use the following technologies:

• EC2s managed with AWS CDK
• AWS Lambdas running Python deployed via the Serverless Framework

About the Compensation

• 105k - 130k salary
• Generous ISO stock options
• Generous paid time off
• Medical, Vision, and Dental