Title: Digital Marketer — Paid Ads, Creative, and Viral Growth
Company: ORE Software (portfolio: Fiducia, Sonus Auris, zed-pkg, Daedalus Fab, Quaestor Ledger)
Location: Remote (US preferred, overlap with US Eastern)
Type: Part-time to full-time / contractor — 15–30 hrs/week to start, room to grow
Compensation: Modest cash + meaningful equity / revenue share (discussed in interview)
Reports to: Founder
ORE Software is a small, remote-first studio shipping several products from the same engineering baseline: Rust services, Flutter/Dart clients, TypeScript where it earns its keep, Kubernetes on AWS and Hetzner, Postgres, Cloudflare, and shared auth/sync/telemetry. We do not build internal product UI in React.
Products this hire will touch:
- Fiducia (github.com/fiducia-cloud) — distributed coordination: fenced locks/leases, routing, payments, operator desktop + Flutter
- Sonus Auris (github.com/sonus-auris) — privacy-first audio capture, indexing, transcription, evidence preservation
- zed-pkg (github.com/zed-pkg) — universal multi-language package manager (git/hg-backed) — not the Zed editor
- Daedalus Fab (github.com/daedalus-fab) — fabrication plans, designs, released instructions, and runs
- Quaestor Ledger (github.com/quaestor-ledger) — multi-tenant AR/AP ledger that observes, records, and proves — it never moves money
- ORESoftware (github.com/oresoftware) — shared infra: k8s clusters, auth, observability, the deployment spine
We have several real products and almost no public demand engine. This is not a “post three times a week” social job. You will own paid acquisition, creative, and campaigns that can actually travel — ads that convert, stunts and content that get shared, and a measurement loop so we know what worked.
You will market to very different buyers: developers (zed-pkg), operators and infra people (Fiducia), privacy-conscious professionals (Sonus Auris), fabrication / manufacturing (Daedalus), finance/ops (Quaestor). One brand voice will not work. Channel and creative have to match the product.
You will also be in rooms with people. Conferences, meetups, dinners, DMs, booths. The job is not only ads dashboards.
- Build and run paid campaigns on Meta, Google, LinkedIn, X, YouTube, Reddit, and whatever new channel is actually converting
- Write and ship creative: hooks, scripts, short-form video, landing-page copy, carousels, founder clips — not just “brief an agency”
- Design viral / shareable campaigns: launches, challenges, developer-week drops, waitlists, referral loops, community seeding
- Stand up tracking: pixels, UTMs, landing pages, attribution that is good enough to spend against
- Run a weekly experiment cadence: hypothesis → creative → spend → kill or double down
- Own CAC, ROAS, waitlist → signup, and “did this campaign actually move a product” — not vanity follower counts
- Guesstimate before you spend: TAM-ish sketches, “if 2% click and 8% convert, do we even run this?”, back-of-envelope budget vs payoff. You do not need to be a data scientist. You do need to be numerate.
- Show up in person when it counts: conferences, meetups, hallway conversations. Be someone people want to talk to. Be creative in how you start those conversations, not only in ad copy.
- Sales and bizdev in a pinch: warm a lead, take a first call, follow up after a conference, explain the product in human terms. You understand why people buy, hesitate, refer, or ignore.
- Collaborate with the founder on positioning per product; you will often be the first marketing hire touching that product
- Ship work through GitHub: landing-page copy, campaign snippets, small site edits. You write with AI, open a branch, push, and open a pull request. You do not need to merge, review architecture, or be a software engineer. You do need to not be afraid of a repo.
- You’ve spent real money on ads and can talk about what broke, what scaled, and why
- You can make or direct creative, not only media-buy
- You like people. Networking is not a chore you outsource
- You like developer tools or consumer-adjacent products enough to learn both
- You are comfortable with early-stage mess: no brand book, no 8-person marketing org, no infinite budget
- 3+ years in digital marketing, performance ads, or growth with shipped campaigns you can show
- Hands-on in at least two of: Meta Ads, Google Ads, LinkedIn Ads, TikTok/YouTube ads
- Strong copy and creative taste; portfolio of ads, landing pages, or campaigns
- Comfort with analytics (GA4, ads managers, basic funnel math)
- Comfortable with people: conferences, networking, being in a booth or a hallway and starting conversations. Creative in person, not only on a laptop.
- Numerate: good enough at math and Fermi-style guesstimates to sanity-check spend, conversion, and “is this even worth doing”
- Can sell a little: bizdev and first-call sales when needed. You read motivations — status, fear, curiosity, convenience — and you don’t talk past them
- AI + GitHub: you write copy/code/assets with AI assistance, push to GitHub, and open pull requests. Merging is optional; getting the change into review is not
- Can work async, write clearly, and ship without a committee
- Developer-tool, infra, fintech, privacy, or hardware/manufacturing marketing
- Short-form video editing (CapCut, Premiere, DaVinci)
- Community / Reddit / HN / indie-hacker launches
- Landing pages (Webflow, Framer, or PRs against our marketing sites)
- Prior startup or agency work where you owned the number, not a slide
Send a short note + 2–3 campaigns you’re proud of (links, spend, result) to [APPLY_EMAIL] or Easy Apply on LinkedIn. If you’ve opened a GitHub PR, include the link.
Hashtags: #DigitalMarketing #PerformanceMarketing #GrowthMarketing #PaidAds #StartupJobs #RemoteWork #DeveloperTools
Title: QA Engineer & Product Tester (Web, App, API)
Company: ORE Software
Location: Remote
Type: Part-time to full-time — we will hire more than one person if the fit is right
Compensation: Cash + equity (discussed)
Reports to: Founder / technical lead
ORE Software is a small, remote-first studio shipping several products from the same engineering baseline: Rust services, Flutter/Dart clients, TypeScript where it earns its keep, Kubernetes on AWS and Hetzner, Postgres, Cloudflare, and shared auth/sync/telemetry. We do not build internal product UI in React.
Products this hire will touch:
- Fiducia (github.com/fiducia-cloud) — distributed coordination: fenced locks/leases, routing, payments, operator desktop + Flutter
- Sonus Auris (github.com/sonus-auris) — privacy-first audio capture, indexing, transcription, evidence preservation
- zed-pkg (github.com/zed-pkg) — universal multi-language package manager (git/hg-backed) — not the Zed editor
- Daedalus Fab (github.com/daedalus-fab) — fabrication plans, designs, released instructions, and runs
- Quaestor Ledger (github.com/quaestor-ledger) — multi-tenant AR/AP ledger that observes, records, and proves — it never moves money
- ORESoftware (github.com/oresoftware) — shared infra: k8s clusters, auth, observability, the deployment spine
We ship Flutter apps, Rust web UIs (server-rendered HTML / HTMX, not React), JSON APIs, CLIs, and desktop apps. Quality is currently founder-bottlenecked. You will be the person who breaks things on purpose, writes it down so it can be fixed, and uses AI to multiply coverage — not to skip thinking.
This is hands-on testing of live products: browsers, phones, tablets, desktop, APIs, and installable apps. Automation is welcome. Clear bugs are required. “It felt off” without steps is not a report.
You are not locked in a test cave. You will talk to people, sit in rooms at conferences when useful, and sometimes explain the product to a stranger well enough that they want to try it.
- Exploratory and regression testing across web, Flutter (iOS/Android/desktop), and desktop Rust apps
- Test critical flows: auth, onboarding, payments/ledger views, audio capture (Sonus), package install (zed-pkg), fabrication plan/run flows (Daedalus)
- File bugs with: environment, exact steps, expected vs actual, screenshots/recordings, and severity
- Maintain smoke and regression checklists per product; run them before releases
- Light automation: Playwright (we prefer Playwright/Puppeteer over Cypress), API checks, device farms / emulators when useful
- Use AI to draft test cases, generate edge cases, and summarize failing traces — you still verify
- Write test helpers and small fixes with AI, then push a branch and open a PR. You do not need merge rights or to land production deploys. You do need to get your work onto GitHub so someone else can review it.
- Guesstimate risk: “if we skip this path, what’s the blast radius?”, rough counts of cases, time-to-cover vs severity. Good enough math to prioritize, not a statistics thesis.
- Work with our observability stack (structured logs, traces) to distinguish “UI glitch” from “backend fault”
- Retest fixes; don’t close tickets you haven’t actually re-run
- People, not only tickets: when we’re at a conference or on a call, you can talk to users, watch them use the product, and notice what they actually do. In a pinch you can help with a demo, a booth, or a follow-up that is basically sales/bizdev.
- You understand why a user rage-taps, abandons checkout, or never finds the button — human motivation, not only assertion failures
- Web: marketing sites + authenticated apps (HTMX/Maud, some TypeScript clients)
- Mobile & desktop: Flutter
- APIs: REST/JSON, auth sessions, sync/offline behavior
- CLI / package manager flows (zed-pkg)
- Privacy-sensitive paths (Sonus recordings, Quaestor ledger proofs, Fiducia locks)
- Detail-obsessed testers, QA engineers, or strong manual testers ready to level into automation
- People who like being the last line before users see a mess
- Comfortable asking “what should happen?” when the spec is thin
- Social enough to network and sit with users, not only file tickets from home
- Clear written English and a habit of reproducing issues before reporting them
- Experience testing websites and/or native/mobile apps
- Familiarity with Chrome/Safari/Firefox, iOS and Android, and browser DevTools
- Can follow a checklist and go off-script when something smells wrong
- Comfortable with people: conferences, meetups, hallway conversations, being creative about how you get signal from humans (not only from test runs)
- Numerate: decent math and guesstimating — coverage, risk, “how many devices is enough,” time vs severity
- Sales/bizdev in a pinch: you can demo, listen, and talk to a prospective user or partner without freezing. You get human psychology: why people click, quit, trust, or complain
- AI + GitHub: comfortable writing tests/code with AI, pushing to GitHub, and opening pull requests. Merging is not required
- Willingness to learn Playwright, Postman/HTTPie, and our issue tracker (GitHub + Linear)
- Playwright, Appium, Maestro, or Flutter integration tests
- API testing, SQL, or reading JSON error payloads
- PWA / offline / IndexedDB testing
- Accessibility, localization, or performance smoke testing
- ISTQB or similar — optional, not a filter
- Comfort around privacy/security products (you will not get production secrets; you will treat test data as sensitive)
Send a resume + 5–10 sentence note on a product you tested (what you found, how you reported it) to [APPLY_EMAIL] or Easy Apply. A GitHub PR you’ve opened (even a tiny one) is a strong plus.
Hashtags: #QA #QualityAssurance #SoftwareTesting #Playwright #Flutter #RemoteJobs #StartupJobs
Title: Technical Cofounder (Engineering + Infrastructure)
Company: ORE Software
Location: Remote; strong overlap with US Eastern. Occasional infra work on real machines (AWS EC2 k8s, Hetzner k8s), not “Vercel-only.”
Type: Cofounder — this is not a 10-hour fractional CTO gig
Compensation: Significant equity (to be negotiated; this is ownership, not a contractor rate). Cash as the companies can support it.
Reports to: Partnership with the founder (Alex)
ORE Software is a small, remote-first studio shipping several products from the same engineering baseline: Rust services, Flutter/Dart clients, TypeScript where it earns its keep, Kubernetes on AWS and Hetzner, Postgres, Cloudflare, and shared auth/sync/telemetry. We do not build internal product UI in React.
Products this hire will touch:
- Fiducia (github.com/fiducia-cloud) — distributed coordination: fenced locks/leases, routing, payments, operator desktop + Flutter
- Sonus Auris (github.com/sonus-auris) — privacy-first audio capture, indexing, transcription, evidence preservation
- zed-pkg (github.com/zed-pkg) — universal multi-language package manager (git/hg-backed) — not the Zed editor
- Daedalus Fab (github.com/daedalus-fab) — fabrication plans, designs, released instructions, and runs
- Quaestor Ledger (github.com/quaestor-ledger) — multi-tenant AR/AP ledger that observes, records, and proves — it never moves money
- ORESoftware (github.com/oresoftware) — shared infra: k8s clusters, auth, observability, the deployment spine
I need a partner who can ship product and keep it running. That means application code and clusters: Rust API/web servers, Flutter or TypeScript clients, Kubernetes, Postgres, Cloudflare, CI, and the boring reliability work that makes the rest possible.
You will not be siloed on one repo. The studio pattern is consistent across orgs (interfaces, clients, API server, web server, infra, e2e, Flutter), but the domains are different — coordination (Fiducia), audio (Sonus), packages (zed-pkg), fabrication (Daedalus), ledgers (Quaestor), plus shared auth, sync, and telemetry.
Internal UI is not React. Front-end here means Flutter/Dart, TypeScript (non-React), and server-rendered HTML (Maud + HTMX, sometimes Leptos/Dioxus). If React is your only frontend, this is the wrong seat.
You also have to be a person other people want to work with in a hallway. Conferences, customer conversations, a first sales call when that’s what’s in front of us. Cofounder means the company, not only the compiler.
- Architecture and delivery across multiple GitHub orgs, not a single greenfield app
- Hands-on: Rust services (Axum, SeaORM), Flutter apps, TypeScript clients, CLIs
- Infra: Kubernetes (AWS + Hetzner), Cloudflare (Workers/R2/DNS), Postgres / Cockroach, Redis, NATS, observability (OpenTelemetry → our stack)
- The four ways our web and API tiers talk: direct DB reads, stateless HTTP, stateful TCP, and async via NATS
- CI, releases, secrets hygiene, incident response, and “it works on the cluster, not only on my laptop”
- Front-end enough to ship operator UIs and client apps — you don’t need to be a visual designer
- AI-native coding: you write and review with AI every day. You still understand the diff. You push branches and open PRs as the default way work moves; merge rights can wait, hiding work in a local folder cannot
- Fermi math: capacity, cost, latency, “can we even?” estimates before we spend a week building. Pretty good at math and guesstimating — you smell a 10x error
- Hiring bar and review culture as we add QA and later engineers
- Product judgment: what to build, what to defer, what to kill
- People and rooms: conferences, meetups, partner dinners, being creative about how we show up. Not a pure back-room engineer
- Sales and bizdev when needed: first conversations, technical sales, reading what the other person actually wants (fear, status, deadline, curiosity) and answering that, not a feature dump
- You’ve been the person who both wrote the service and deployed it
- You like systems that have to be correct (ledgers, locks, recordings, package provenance) more than you like slide decks
- You can context-switch across repos without losing the plot
- You want equity and responsibility, not a staff-engineer ladder at a 5,000-person company
- You can talk to humans without wishing you were SSH’d into a box instead
- Strong in at least two of: Rust, Dart/Flutter, TypeScript; willing to work in all three
- Real production DevOps: Kubernetes, Linux, CI, networking, TLS, backups, not only Docker Compose on a laptop
- Postgres (schema, migrations, operational care); bonus for Cockroach or similar
- Can debug across the stack: browser → API → DB → cluster
- Excellent written communication; we run on GitHub + Linear
- Comfortable with people: conferences, networking, being creative in how you meet and work a room — not only how you write a service
- Numerate: pretty good at math and guesstimating (cost, load, timelines, “does this even pay off”)
- Can do sales/bizdev in a pinch: you understand human psychology and motivations; you can take a conversation from “what is this?” to “when can we try it?”
- AI + GitHub workflow: you code with AI, push to GitHub, and open pull requests as normal practice. You do not need to be the person who merges everything, but work lives in PRs, not in private branches forever
- High integrity. You will see infra and product internals. No cowboy production changes, no secret leakage, no “I’ll rewrite history to make the branch look clean”
- SeaORM, Axum, Maud/HTMX, Nix
- Cloudflare R2, Supabase/GoTrue, NATS
- Formal/spec-oriented work, JSON Schema contracts, polyglot SDKs
- Audio, packaging, distributed locking, or double-entry/ledger domain experience
- You’ve cofounded or been employee #1–5 before
- Not a React/Next.js product-company CTO role
- Not “advise 5 hours a week and we have contractors do the work”
- Not a pure platform SRE who never touches product or customers
- Not a pure product engineer who has never been paged for a cluster
- Not “brilliant jerk who cannot talk to a stranger at a conference”
This is a conversation, not an ATS funnel. Email [APPLY_EMAIL] with:
- Links to systems you’ve built and operated (repos, posts, architecture notes — public is fine)
- The stack you’re strongest in, and the one you’d need to ramp
- A conference, community, or customer moment you’re proud of (even a small one)
- What you want out of a cofounder split (time, equity range, which products excite you)
Link a GitHub PR that is yours.
Hashtags: #TechnicalCofounder #FoundingEngineer #Rust #Kubernetes #DevOps #Flutter #Startup #Remote