cbzehner

Fazeshift | Senior Software Engineer | San Francisco, CA | Onsite 5 days | Full-time | $200k–$235k + equity

I’m Chris, VP Engineering at Fazeshift. We build AI agents that do accounts-receivable work: billing, collections, payments, and cash application. We're nine engineers plus our Founder/CTO and me, and I'm hiring someone who can help us do more, better: increase both our production capacity and the quality and sophistication of the software we build.

We think AI changes what’s possible here. Instead of giving finance teams another dashboard to stare at, we’re building agents that actually do the work across billing, collections, payments, cash application, and the workflows connecting those systems.

The interesting engineering constraint: we’re intentionally not the system of record. We act across customers’ ERPs, banks, and billing systems. A situation where a timeout doesn’t necessarily mean a write failed, and retrying blindly can be the wrong answer.

A few of the questions we get to work on: * How do you let agents take real actions safely? Permissions, auditability, retries, idempotency, durable execution, and knowing when a human needs to stay in the loop. * How do you build a coherent product when you’re intentionally not the system of record? APIs are inconsistent, webhooks arrive late or twice, and a timeout doesn’t necessarily mean a write failed. * How should an engineering team work when coding agents can take on meaningful chunks of implementation, debugging, testing, and exploration?

We’re especially interested in engineers who have already changed how they work because of AI. If you delegate meaningful work to agents, keep independent tasks moving in parallel, debug where they get stuck, and shave the occasional yak to get things working properly, you’ll feel at home here. We’re still figuring this out too (and updating our priors regularly).

At the same time, generated code is still your code. We care about judgment, debugging, systems thinking, taste, and understanding what you’re shipping.

Our approach is roughly: design enough to find the shape of the problem, then build to learn. There’s a short distance here between noticing a problem, building the fix, and seeing the result.

We’re looking for 5+ years of professional experience, strong TypeScript/full-stack skills, and production ownership. No fintech background needed.

Stack: TypeScript/Next.js, tRPC, Prisma/MySQL/PlanetScale, Inngest, AWS.

I’m Chris, VP Engineering, and I read these applications myself. Email [email protected] with HN in the subject, your LinkedIn/GitHub/résumé, and a few sentences about something you’ve built and how you knew it worked or how AI has changed your approach. No public code needed; please leave out confidential details.

I find Rust and Typescript have a lot of helpful surface similarities that make them an easy pair of languages to switch between.

The fundamentals are very different but it’s a case of convergent evolution - and I’m happy to liberally sprinkle clone’s around my rust code

I used Fish for several years before switching over to nushell a few weeks ago.

Nushell takes the ideas behind Fish even further by incorporating types other than strings and adding more built-in functionality that’s useful for your average command-line user.

I doubt I’ll go back but both are great! Highly recommend Fish and Nushell!

Incredible!

What was the hardest part?

What did you learn that you weren’t expecting?

"What I really need is a droid that understands the binary language of moisture vaporators."

"Vaporators? Sir, my first job was programming binary loadlifters—very similar to your vaporators in most respects."

―Owen Lars and C-3PO

Please do. This has been a consistent pain point in my Rust web dev experience and even seeing some examples of how others structure solutions really helps!

If this isn't an ironic commentary on current events...

200 OK { errors: “This way lies madness” }

My understanding was that darcs fixed the model but had fundamental performance problems at _some scale_. I think pijul took the same concepts and tried to streamline them. And this rewrite does that...again?

I moved back to Austin, Texas when this all started. Family, breakfast tacos and more living space were all factors.

You've just invented shipping containers.

tl;dr

Suggested alternatives to the terminology master-slave:

Primary-secondary, Leader-follower, Active-standby, Primary-replica, Writer-reader, Coordinator-worker, Parent-helper

Suggested alternatives to the terminology whitelist-blacklist:

Blocklist-allowlist, Block-permit

I worked at a company with an engineer who had a Perl script that prompted them to record what they were doing at random intervals through out the day.

When it came time for performance reviews, not only did it make for entertaining reading but it was easy to find all the small improvements they made that normally slip through the cracks.

Thanks for sharing what you've been building. Very cool!

> For maintaining eye contact during video call we need to look at camera rather than screen.

I solve this problem in most meetings by positioning the main view as a smaller window directly under my webcam. This helps put my focal point close to the speaker from their perspective.

Seems similar in aim to Gitless

[0] https://gitless.com/

Even if the target market fails, they’ve got a fallback. These things are going to be on Hollywood sci-fi sets for years to come!

Just took a look at your landing page, cool idea -- one element of your service that really stood out was down at the bottom "Free concierge onboarding".

Really interesting offer. Do you find new subscribers take you up on this a lot? Seems like a great way to improve your migration tooling!

Although it's not a "codebase" per se, Architecture of OpenSource Applications is a great way to see how lots of major applications are structured. http://aosabook.org/en/index.html

What makes this approach "modern"? What is this approach the alternative to?

As someone broadly unfamiliar with text rendering it's not clear to me. An introduction to these points would be very helpful