diff --git a/content/roles.md b/content/roles.md deleted file mode 100644 index 4a22614..0000000 --- a/content/roles.md +++ /dev/null @@ -1,5 +0,0 @@ -+++ -title = "number 0: open roles" -description = "Build on the edge with the team that lives there" -template="roles.html" -+++ diff --git a/content/roles/_index.md b/content/roles/_index.md new file mode 100644 index 0000000..fe8f3d7 --- /dev/null +++ b/content/roles/_index.md @@ -0,0 +1,53 @@ ++++ +title = "number 0: open roles" +description = "Build on the edge with the team that lives there" + +# Template to use to render this section page. +template = "roles/index.html" + +# The given template is applied to ALL pages below the section, recursively. +# If you have several nested sections, each with a page_template set, the page +# will always use the closest to itself. +# However, a page's own `template` variable will always have priority. +# Not set by default. +# page_template = + +# The date of the post. +# Two formats are allowed: YYYY-MM-DD (2012-10-02) and RFC3339 (2002-10-02T15:00:00Z). +# Do not wrap dates in quotes; the line below only indicates that there is no default date. +# If the section variable `sort_by` is set to `date`, then any page that lacks a `date` +# will not be rendered. +# Setting this overrides a date set in the filename. +# date = + +# The last updated date of the post, if different from the date. +# Same format as `date`. +# updated = + +# The weight as defined on the Section page of the documentation. +# If the section variable `sort_by` is set to `weight`, then any page that lacks a `weight` +# will not be rendered. +weight = 0 + +# A draft page is only loaded if the `--drafts` flag is passed to `zola build`, `zola serve` or `zola check`. +draft = false + +# If set, this slug will be used instead of the filename to make the URL. +# The section path will still be used. +# slug = "" + +# The path the content will appear at. +# If set, it cannot be an empty string and will override both `slug` and the filename. +# The sections' path won't be used. +# It should not start with a `/` and the slash will be removed if it does. +# path = "" + +# Use aliases if you are moving content but want to redirect previous URLs to the +# current one. This takes an array of paths, not URLs. +aliases = [] + +# When set to "true", the page will be in the search index. This is only used if +# `build_search_index` is set to "true" in the Zola configuration and the parent section +# hasn't set `in_search_index` to "false" in its front matter. +in_search_index = true ++++ diff --git a/content/roles/biz-dev-lead.md b/content/roles/biz-dev-lead.md new file mode 100644 index 0000000..40324e5 --- /dev/null +++ b/content/roles/biz-dev-lead.md @@ -0,0 +1,30 @@ ++++ +title = "Biz Dev Lead" +description = "Full Time, Remote" +template = "roles/page.html" ++++ + +### Full-time + +We're looking for someone to keep our relationships with leads cooking. n0 is building genuinely new technology, and the people who want it are often technical themselves — so the person in this seat has to be able to hold a real conversation about what Iroh is and why it matters, then keep that conversation warm over weeks and months until it's ready to close. + +This is a relationship role first: staying in touch, following up, and making sure no promising lead goes cold because we forgot to reach back out. + +## What you'll do + +- Own the health of our lead relationships — keep them warm, moving, and never neglected +- Be technical enough to explain what Iroh is, who it's for, and what problems it solves, without needing an engineer in the room for every call +- Run disciplined follow-up: track every conversation, know what each lead needs next, and make sure it happens +- Keep our pipeline and CRM honest and up to date, so we always know where each relationship stands +- Feed what you hear from leads back to product and leadership so we get sharper over time + +## You might be a fit if + +- You're the kind of person who never lets a thread drop — follow-up is second nature +- You can get technical enough to earn the trust of an engineering audience +- You genuinely like people and are energized by keeping relationships alive over the long haul +- You're organized enough to keep dozens of conversations straight without dropping any + +We have the technology and the momentum; what we need is someone who keeps the human side of our pipeline warm and moving. If that sounds like you, come hang out. + +If that's you, reach out and send along something we can read to get to know your work — a deal you nurtured, a relationship you built, or anything that shows how you operate. diff --git a/content/roles/dev-ops.md b/content/roles/dev-ops.md new file mode 100644 index 0000000..293fbf1 --- /dev/null +++ b/content/roles/dev-ops.md @@ -0,0 +1,31 @@ ++++ +title = "Dev Ops" +description = "Full Time, Remote" +template = "roles/page.html" ++++ + +This is the classic job, done well: keep the servers running. As Iroh Services grows into enterprise deployments, the reliability of our infrastructure becomes a promise we make to customers — and we're looking for the person who helps us keep that promise. You'll work directly with our head of measurement & operations, and receive support from the engineering team to drive a smooth experience marked by a quality of care & craft that we aim to bring to all of our work. + +## What you'll do + +- Keep production running: monitor, respond, and steadily raise the floor on reliability +- Keep CI fast and green so the team ships with confidence +- Help define and deliver SLAs to enterprise customers — and build the observability and alerting that let us stand behind them +- Own incident response: reduce how often things break, and how long they stay broken +- Automate the repetitive parts of operations so the team spends its time on hard problems +- Work async with a remote-first team operating around the world + +## Our stack + +Rust · Postgres · ClickHouse · Prometheus · Ansible + +## You might be a fit if + +- You've kept real production systems healthy and have the on-call scars to show for it +- You treat CI, deploys, and monitoring as products with users, not chores +- You've worked against real SLAs and understand what it takes to actually hit them +- You'd rather write the automation once than answer the same page twice + +We have the engineering skills to ship genuinely new technology; what we need is someone who makes sure it's always up when customers reach for it. If that's the kind of ownership you enjoy, come talk to us. + +If that's you, reach out and send along something we can read to get to know your work — a system you've kept alive, a postmortem you're proud of, or a repo that shows how you think. diff --git a/content/roles/iroh-services-lead-maintainer.md b/content/roles/iroh-services-lead-maintainer.md new file mode 100644 index 0000000..d0519c9 --- /dev/null +++ b/content/roles/iroh-services-lead-maintainer.md @@ -0,0 +1,35 @@ ++++ +title = "Lead Maintainer: Iroh Services" +description = "Full Time, Remote" +template = "roles/page.html" ++++ + +### Full-time · Senior Engineer + +We're looking for a senior engineer to own services.iroh.computer — the hosted infrastructure that turns Iroh from a library into a product. This is a high-trust role for someone who loves growing production systems and then factoring them to be equally reliable & boring. You'll work directly with our Head of Product and CTO to stake out a long-term architecture and guide it into existence, with support from our core engineering team. + +Iroh gives applications direct, peer-to-peer connections. Iroh Services is how we deliver that at scale to customers who don't want to run the plumbing themselves. You'll be the person who owns that plumbing end to end. + +## What you'll do + +- Own the architecture, roadmap, and day-to-day health of services.iroh.computer +- Ship and maintain production services in Rust, with a React front end where customers touch the product +- Design for the long term: make the calls now that keep us fast in a year, and write them down so the team can move with you +- Tackle a steady stream of automation challenges — provisioning, deploys, observability, and the glue that keeps user-provisioned infrastructure humming +- Partner with Head of Product and CTO to turn customer needs into a system that can carry them + +## Our stack + +Rust · React · Postgres · ClickHouse · Prometheus · Ansible + +## You might be a fit if + +- You've shipped and operated a production SaaS backend written in Rust +- You think in terms of long-term architecture, not just the next PR — and you can bring other engineers along with you +- You strongly believe in insulating from external dependencies with code we control +- You're comfortable owning a service outright: the code, the infra, the uptime that results from it +- You like automating away toil more than you like doing it twice + +The n0 team has the engineering skills to ship genuinely new technology, and we're building the hosted layer that puts it in customers' hands. If owning that layer sounds like your kind of problem, we'd love to talk. + +If that's you, reach out and send along something we can read to get to know your work, ideally your open source profile on github/gitlab/git tea, whatever. If not that, send us a repo, a system you've built, a write-up you're proud of. diff --git a/content/roles/marketing-lead.md b/content/roles/marketing-lead.md new file mode 100644 index 0000000..1dd8f71 --- /dev/null +++ b/content/roles/marketing-lead.md @@ -0,0 +1,31 @@ ++++ +title = "Marketing Lead" +description = "Full Time, Remote" +template = "roles/page.html" ++++ + +### Full-time · Early-to-mid-career + +We're looking for a marketing professional to own how n0 reaches the people who want what we're building. This is a hands-on growth role, and we want to be clear about its shape: our voice and our sharpest ideas originate with the technical team, and they should stay there. Your job isn't to reinvent the messaging — it's to take that voice to market, measure what happens, keep pointing us at what's working, and drive progress through consistency. + +Think of this as a build-your-craft seat. You'll get your hands on launches, channels, the funnel, and experiments from day one, and grow into the GTM operator this company needs as it scales. + +## What you'll do + +- Take the technical team's voice and ideas to market — consistently, across channels, without flattening them +- Own the mechanics of our launches: keep the schedule on track, sequence releases for impact, and make each one land harder than it would alone +- Measure everything — stand up the tracking, close the loop, and tell the team plainly what worked and what didn't +- Run growth experiments, read the results honestly, and double down on the repeatable wins +- Keep our go-to-market motion organized and improving as it grows + +## You might be a fit if + +- You're early in your career but already an operator — you make things happen and follow through without being chased +- You're hungry to learn go-to-market from the ground up and want to grow into owning it +- You're rigorous about measurement; you let the numbers, not vibes, decide where your effort goes +- You can amplify a technical team's authentic voice rather than trying to replace it +- You move fast, stay organized, and don't need the vision handed to you to make real progress + +The best marketing for a company like ours sounds like the engineers who build the thing. We want someone hungry to carry that voice to the right people, measure the impact, and compound the wins over time. If that's the craft you want to build, let's talk. + +If that's you, reach out and send along something we can read to get to know you — a project you ran, results you're proud of, or anything that shows how you operate. diff --git a/templates/roles.html b/templates/roles.html deleted file mode 100644 index a645ace..0000000 --- a/templates/roles.html +++ /dev/null @@ -1,83 +0,0 @@ -{% extends "layout.html" %} {% block content %} -
-
-

open roles

-
-

- Contract Business Development Lead — n0 -

-

- Part-time contract position -

- -
-

- We're looking for an experienced business development - professional to help us price & ship two product lines - built on Iroh. This is a hands-on, strategic role working - directly with the CEO and Head of Product to validate - pricing, refine ideal customer profiles, and drive sales - conversations. -

- -

- Scope of Work -

-
    -
  • - Schedule and coordinate willingness-to-pay interviews - with target customers -
    • -
  • - Synthesize feedback from customer conversations into - actionable pricing insights -
    • -
  • - Work with CEO and Head of Product to develop and iterate - on pricing models -
    • -
  • - Expand our existing market research to define ideal - customer profiles for each of our product lines -
    • -
  • - Audit and organize existing prospect data against - refined ICPs -
    • -
  • - Prioritize outreach targets based on fit -
    • -
- -

- If you have deep experience defining & refining the price of - a product, come hang out. The n0 team has the engineering - skills to ship truly new technology, growing revenue, and a - hunger to find more open doors to push on. -

- -

- If that sounds interesting, - schedule a call - with a link to something we can read to learn more about - you. -

-
- Let's chat -
-
-
-
-
-{% endblock %} {% block pagination %} {% if page.earlier or page.later or -page.lighter or page.heavier %} - -{% endif %} {% endblock %} diff --git a/templates/roles/index.html b/templates/roles/index.html new file mode 100644 index 0000000..2f1b223 --- /dev/null +++ b/templates/roles/index.html @@ -0,0 +1,17 @@ +{% extends "layout.html" %} {% block content %} +
+
+

open roles

+ + {% for role in section.pages %} + +
+

{{ role.title }}

+

{{ role.description | safe }}

+
+ + {% endfor %} +
+
+{% endblock %} +{% block pagination %}{% endblock %} diff --git a/templates/roles/layout.html b/templates/roles/layout.html new file mode 100644 index 0000000..97f0914 --- /dev/null +++ b/templates/roles/layout.html @@ -0,0 +1,86 @@ + + + + + + + + + + + + + + + + + + + + {% if config.extra.favicon.webmanifest %} + + {% endif %} + {% if config.extra.favicon.favicon_16x16 %} + + {% endif %} + {% if config.extra.favicon.favicon_32x32 %} + + {% endif %} + {% if config.extra.favicon.android_chrome_512 %} + + {% endif %} + {% if config.extra.favicon.android_chrome_192 %} + + {% endif %} + {% if config.extra.favicon.apple_touch_icon %} + + {% endif %} + {% if config.extra.favicon.apple_touch_icon %} + + {% endif %} + + + + + {% block title %} + {{ config.title }} + {% endblock title %} + + + +{% block navbar %} + +{% endblock navbar %} + + +
+ {% block content %} + {% endblock content %} +
+ + {% block pagination %} + {% endblock pagination %} + + {% block footer %} + {% endblock footer %} + + + + + {% block extra_js %} + {% endblock extra_js %} + + diff --git a/templates/roles/page.html b/templates/roles/page.html new file mode 100644 index 0000000..5237ae8 --- /dev/null +++ b/templates/roles/page.html @@ -0,0 +1,38 @@ +{% extends "layout.html" %} +{% block content %} +
+
+
+

open role

+

+ {{ page.title }} +

+

+ {{ page.description }} +

+ +
+ {{ page.content | safe }} +

+ If that sounds interesting, + schedule a call + with a link to something we can read to learn more about + you. +

+
+ Let's chat +
+
+
+
+
+{% endblock %} +{% block pagination %}{% endblock %}