Founder Associate

About Alguna

AI-Native CPQ & Billing for Modern Pricing Models

Tech description:

## Engineering Principles ##

**Build as simply as possible:** Simple is fast, and allows us to rapidly iterate and deliver business value. For every hour we spend on complex solutions, that’s an hour we’ve lost of iteration.

**Be efficient:** If there’s a reasonably priced SaaS that delivers something we need for not much money, let’s not waste development hours re-implementing solved problems.

**Be opinionated:** We don’t want to have several ways of solving non-novel problems, let’s use opinionated frameworks and technologies that allow us to move quickly.

**Expect to iterate:** The architecture will need to evolve over time, so don’t make choices that build us into a corner.

* **Account for cost.** We should assess for cost from day one rather than address it in 1-2 years.

## Stack ##

**Frontend:** Our customer dashboard and website are built with NextJS, using Tailwind and React, and deployed on Vercel.
**Backend:** is built using Golang and hosted on AWS

Job description:

### **Who you are**

**You're allergic to chaos — and weirdly good in it.** Messy, half-defined problems are your favorite kind. You take them, untangle them, and hand back something clean, repeatable, and boring (in the best way).

**You hunt for leverage.** You don't just do the task. You ask: how do we do this in half the time next week? And automate it the week after? "I did it" is fine. "I did it and it'll never need doing again" is the goal.

**You're calm, sharp, and reliable.** You catch the thing nobody else caught. Especially when stakes are high and a missed detail costs us real money or real trust.

**You move before you have permission to.** Perfect instructions aren't coming. You figure out what "good" looks like, write the plan, ship it, and tell us after.

**You write like an adult.** Crisp updates. Docs people actually read. The right context for the right audience — not a wall of text, not a cryptic one-liner.

**Ambiguity doesn't rattle you.** Early-stage means priorities shift weekly and half the processes don't exist. That's not a bug. That's the job.

**You think in systems.** Workflows, owners, edge cases, "what breaks if this input changes." You see the pipes, not just the water.

**You treat AI as a force multiplier.** Drafting, summarizing, analyzing, templating, automating the repetitive grind — all fair game. Judgment stays yours.

### What you'll actually do

\- **Keep the business running.** Own the day-to-day across the company. Nothing important falls through the cracks on your watch.

\- **Build the rails.** Turn recurring chaos into playbooks, checklists, and systems. Then make them better.

\- **Kill bottlenecks.** Find the slow handoff, the broken approval, the dumb manual step. Fix it. Move on.

\- **Be the connective tissue.** Product, eng, sales, CS, finance — keep the threads connected and the work moving.

\- **Own operational hygiene.** Docs, workflows, dashboards, visibility. If anyone's confused about status, you've got a problem to solve.

\- **Use tools creatively.** Automations, lightweight internal tooling, sharper CRMs and spreadsheets. Whatever cuts friction.

\- **Do the unglamorous stuff with pride.** Some days it's strategy. Some days it's chasing an invoice. You do both well — and make it easier next time.

### What success looks like

\- The team moves faster because you remove friction

\- Important work doesn't get dropped — because you bring structure and follow-through

\- Recurring tasks quietly disappear into automation

\- We scale without bolting on process we don't need