Replit job-pipeline bucket: open Staff+ infra/platform roles, eng handles, Replit Agent x Speckl artifact plan. Surface only - no contact made.
Find a file
Scott Scoble 9ee698fa68 Initial commit: surface-only Replit job-pipeline bucket
Captures:
- 9 high-priority Staff+/Principal infra/platform/agent roles verbatim from Ashby (jobs.ashbyhq.com/replit)
- 38 infra-related open roles total in the snapshot
- Leadership (Amjad Masad, Luis Hector Chavez, Michele Catasta, Scott Kennedy) + 5 public GH members with bios
- Replit Agent x Speckl artifact plan (Nix-anchored agent provenance in Replit workspace)
- Outreach log empty (do not contact)

No artifact built yet. Plan only.
2026-06-18 13:39:54 -07:00
.gitkeep Initial commit: surface-only Replit job-pipeline bucket 2026-06-18 13:39:54 -07:00
README.md Initial commit: surface-only Replit job-pipeline bucket 2026-06-18 13:39:54 -07:00

job-replit

Replit is Scott Scoble's job-pipeline bucket for agentic engineering systems, cloud-IDE platform infrastructure, and supply-chain integrity at the workspace boundary. This repo is the surface - open Staff+ infrastructure/platform roles (verbatim from Ashby), Replit's leadership + public infra handles, the Replit Agent x Speckl artifact plan, and an outreach log (currently empty - no contact made).

Source: replit.com/careers + jobs.ashbyhq.com/replit + blog.replit.com + github.com/replit + replit.com/about + docs.replit.com. Captured 2026-06-18. Ashby JSON dump fetched 2026-06-18 13:29 UTC; 99 open roles in the snapshot.


Why Replit (audience fit)

Replit is the agentic software-creation platform - a cloud IDE with a Nix-pinned development environment (replit.nix + .replit), an in-product AI coding agent (Replit Agent 4, launched 2026-03-11), first-party deployment / database / storage primitives ("Replit Cloud"), and enterprise infrastructure (single-tenant, BYOK, VPC peering). They publicly ship supply-chain hardening features (Package Firewall with Socket, 2026-06-09; Security Center 2.0, 2026-05-07) and the platform has a substantial Nix footprint - replit/nixmodules, replit/nixpkgs-replit, replit/rippkgs, replit/go2nix, plus the 2025-03-05 engineering post "Using Tvix Store to Reduce Nix Storage Costs by 90%". Three direct lines of fit with Scott's positioning:

Scott's pillar Replit surface
Nix-native reproducibility replit.nix config; Nix channel pinning; 1 TB content-addressed Nix store; Tvix reimplementation of the store backend (their own engineering blog)
Agentic engineering systems Replit Agent 4 (2026-03-11), Agent Skills + Custom Instructions (2026-06-10), Build an Agent docs, MCP connector, multi-agent "Multiplayer Computer"
Supply-chain integrity Package Firewall with Socket (2026-06-09); Security Center 2.0 with bulk CVE remediation (2026-05-07); Private Publishing + External Access Tokens (2026-05-06); SOC 2 enterprise posture

Both sides are solving the same problem from opposite ends: Replit owns the workspace substrate that an agent writes into; Speckl owns why the agent wrote what it wrote. The artifact plan in section 3 shows how a Replit Agent session - which already runs inside a Nix-pinned environment - could anchor every emitted artifact with a content-addressed SpeckDL provenance record, so "what the Agent produced" and "where it ran" are byte-attributable end-to-end.


1. Open roles (verbatim from jobs.ashbyhq.com/replit)

The full snapshot is 99 open roles across Engineering (42), GTM (31), IT (10), Support (5), People (5), Operations (3), Brand & Creative (2), Product Management (1). All roles below are public on Ashby. Workplace type is "Hybrid" (Foster City M/W/F in-office) unless otherwise noted. Descriptions below are trimmed to the role-defining body - full text including benefits boilerplate lives at the Ashby URL.

1.1 Staff Software Engineer, Replit Cloud (priority: highest)

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $265K - $390K - Equity
  • Published: 2026-01-27
  • Ashby: https://jobs.ashbyhq.com/replit/f98605a1-36d2-4b2f-b9be-f66064a02645
  • Reports to: Vice President of Engineering (named verbatim in the JD body)
  • Team surface: "Replit Cloud team builds Replit's first party cloud infrastructure so users can build, scale, and succeed entirely on Replit. They manage databases, application storage, app publishing and hosting, development/production environment splitting, custom domains, and more."
  • Snippets (verbatim): "Help power the development of Replit Agent as a technical leader for the Replit Cloud organization. You will report to the Vice President of Engineering... Leverage AI agents to proactively optimize or suggest app improvements on latency, reliability, SEO, and more."
  • Stack: TypeScript, React, CSS, Postgres, Go, Terraform.

1.2 Principal Software Engineer, Money Infrastructure

  • Dept: Engineering - Team: Product Engineering
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $250K - $340K - Equity
  • Published: 2026-01-12
  • Ashby: https://jobs.ashbyhq.com/replit/bb52f792-58c2-41ab-954d-555c821fe3fe
  • Snippets: "This is a Principal Product Engineering role focused on Money Infrastructure at Replit. You'll work on the financial backbone that powers how Replit earns money, how builders earn money, and how Agents transact... The systems you build directly impact revenue, trust, and some of the most critical user journeys on the platform."
  • Stack: Rust, TypeScript, React, Postgres, GraphQL, Node.js.

1.3 Staff Software Engineer, Enterprise Platform

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $240K - $350K - Equity
  • Published: 2026-03-24
  • Ashby: https://jobs.ashbyhq.com/replit/61cfbcb7-cd1e-49ab-82a1-e93c3962e343
  • Snippets: "Join our Enterprise Platform team and build the infrastructure foundations that enable the world's largest organizations to run Replit within their security and compliance boundaries... single-tenant architectures and private connectivity to custom policy enforcement and customer-managed encryption... Build enterprise deployment infrastructure: Design and implement single-tenant and dedicated deployment options... Implement private networking capabilities: Build VPC peering, private connectivity, and static IP configurations... Ship data protection features: Implement bring-your-own-key (BYOK) encryption, customer-managed keys, and data residency controls."
  • Stack: Go / TypeScript / Python - Kubernetes - Terraform.

1.4 Staff Software Engineer, Agent Platform (priority: highest)

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $250K - $365K - Equity
  • Published: 2026-04-14
  • Ashby: https://jobs.ashbyhq.com/replit/43bd4e63-22c3-4b80-abd2-67eaf2c89790
  • Snippets: "Design a collaborative 'Multiplayer Computer' that lets humans and AI agents work together on shared shells, filesystems, and state - conflict-free and in real time... Design and build durable, well-crafted interfaces between the Agent and internal systems, as well as external agentic systems (MCP)."
  • Preferred: "Experience with collaborative editing technologies such as Operational Transforms (OT), CRDTs, or the inner workings of Git. Experience with event sourcing systems."

1.5 Staff Infrastructure Engineer (priority: highest - the verbatim-title match)

  • Dept: Engineering - Team: SRE
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $220K - $325K - Equity
  • Published: 2026-05-29
  • Ashby: https://jobs.ashbyhq.com/replit/6481ec1e-527c-4c1f-a041-2fb5021e7bd5
  • Snippets: "Join our Infrastructure Engineering team and help ensure the reliability, scalability, and performance of Replit's infrastructure that serves millions of developers worldwide... Drive Automation and Infrastructure as Code: Architect, build, and improve automation to eliminate toil... Terraform or Pulumi... Optimize Performance and Infrastructure: Collaborate with core infrastructure and product teams to performance tune and optimize our cloud deployments (Kubernetes, Docker, GCP)... Provide Staff-Level Guidance: Review feature and system designs, acting as an owner for the security, scale, and operational integrity of those designs."
  • Required: "8-10 years of experience in Infrastructure Engineering or similar roles (DevOps, Systems Engineering, Site Reliability Engineering). Strong programming skills in languages like Python or Go."

1.6 Staff Site Reliability Engineer

  • Dept: Engineering - Team: SRE
  • Location: Remote - Europe - Workplace: Remote
  • Published: 2026-05-20
  • Ashby: https://jobs.ashbyhq.com/replit/f35042a1-b016-4811-9597-b98facf5eb4d
  • Snippets: "Join our Site Reliability Engineering (SRE) team and help ensure the reliability, scalability, and performance of Replit's infrastructure that serves millions of developers worldwide... Architect and Implement Observability... Define and Drive Reliability Standards: Work with product and engineering teams to define, implement, and track Service Level Objectives (SLOs) and Service Level Indicators (SLIs)... Deep experience with container orchestration platforms, specifically Kubernetes, and cloud-native technologies."

1.7 Engineering Manager, Enterprise Platform (priority: hiring-manager-of-record for enterprise infra)

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $250K - $350K - Equity
  • Published: 2026-01-23
  • Ashby: https://jobs.ashbyhq.com/replit/7cba072f-9490-4c80-8782-3b8d0398b1a8
  • Snippets: "We're hiring an Engineering Manager to lead the team that builds the infrastructure foundations for Replit Enterprise... You'll own the roadmap for enterprise infrastructure features including single-tenant deployments, private networking, data residency, and customer-managed encryption, partnering closely with Platform and Infrastructure Engineering, Security and Sales to unlock adoption at the world's most demanding organizations... Scale the team: Hire, coach, and retain exceptional infrastructure engineers; create a high-ownership culture with clear execution rituals, high code quality, and thoughtful on-call practices."
  • Why this role is the warm-intro target: This is the named hiring manager for the Enterprise Platform org. Every infra hire that lands on a Fortune-500 procurement deal flows through this team.

1.8 Senior Software Engineer, Agent Platform

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $180K - $260K - Equity
  • Published: 2026-01-18
  • Ashby: https://jobs.ashbyhq.com/replit/b82de6f8-aebf-47b8-8bdc-39ea33807975
  • Snippets: "In this role you will build powerful tools that help product engineers iterate rapidly on the Agent experience and directly enhance the core Agent itself. You'll bridge the gap between the AI team (working on the core Agent logic) and the UX team (crafting delightful Agent experiences)... This role blends systems engineering, developer experience and product engineering. We tackle complex challenges across the full stack, from browser-based interfaces to high-performance backends to Linux systems engineering."

1.9 Software Engineer, Compute Platform

  • Dept: Engineering - Team: Platform
  • Location: Foster City, CA - Workplace: Hybrid
  • Comp: $130K - $290K - Equity
  • Published: 2025-04-04
  • Ashby: https://jobs.ashbyhq.com/replit/659a8e1e-69ba-44c0-a632-96665051a3e8
  • Snippets: "We are seeking talented distributed systems engineers who are passionate about building innovative solutions for application deployment. Your mission will be to enhance the capabilities of Replit Infrastructure, optimize performance across global regions, and drive efficiency while delivering an exceptional user experience... Expand Replit's cloud infrastructure offerings: Launch new cloud products to be used by Replit Agent to build complex apps."
  • Stack: Golang, Rust.
  • Caveat in JD: "This role may not be a fit if... You do not enjoy diving into Linux internals." - direct signal this role touches the Nix substrate.

1.10 Senior Site Reliability Engineer (Remote - Europe)

  • Dept: Engineering - Team: SRE
  • Location: Remote - Europe
  • Published: 2026-05-20
  • Ashby: https://jobs.ashbyhq.com/replit/
  • Same body shape as 1.5 / 1.6, but IC-track (Senior not Staff) and remote-EU only.

1.11 Adjacent Staff+ roles worth knowing

  • Staff Software Engineer, Anti-Abuse and Security (75e69146 - 2026-04-23) - Security-adjacent; the Anti-Abuse org intersects with Package Firewall (Socket partnership, 2026-06-09).
  • Staff Software Engineer, Money (14b3aef3 - 2025-12-18) - monetization stack lead; less of an infra fit but explicitly named in the JD body as leading the monetization space.
  • Staff Software Engineer, Money Partnerships (93b62fcc - 2026-05-05) - partner-eng surface.
  • Staff Software Engineer, Fraud (27618f18 - 2026-05-26) / Risk (76aebfe2 - 2026-05-26) / Trust and Safety (bd27a146 - 2026-05-26) - same Anti-Abuse/Security umbrella as 1.11's first role.
  • Engineering Manager, Anti-Abuse and Security (ccab8626 - 2026-05-26) - manager track for the cluster above.
  • Staff Software Engineer, Product (47235851 - 2025-12-30) - generic senior IC; not infra.

1.12 Notable absences

  • No "Nix engineer" or "build systems engineer" by title. The Nix work is spread across Platform / SRE / Compute roles and several non-public internal teams. The closest verbatim match is "Software Engineer, Compute Platform" (1.9) which calls out Linux internals explicitly.
  • No "Supply Chain Security" role. Package Firewall and Security Center ship under the broader Anti-Abuse / Security umbrella (1.11 cluster), not as a dedicated team. A dedicated supply-chain role is plausible in the next quarter given the 2026-06-09 Socket partnership launch.
  • No recruiter handle exposed. All apply URLs route through Ashby anonymously - no named recruiter on the JD body.

2. Public surface (leadership, engineering handles, recent activity)

2.1 Leadership (from replit.com/about)

Name Role GH handle Notes
Amjad Masad Founder and CEO amasad bio: "ceo @ repl.it"; blog author of operating-principles post; TED Talk linked from every JD
Haya Odeh Co-Founder, Head of Design (private) essayist; 2026-05-10 post "Mothers who build"
Luis Hector Chavez CTO (private) not a public GH committer; named as CTO on about page
Michele Catasta President pirroh bio: "LLMs, Agents, AI for Code -> Building, Advising, Investing" - Replit listed as company
Scott Kennedy VP of Engineering (private) the line manager named explicitly in JD 1.1 (Staff SWE, Replit Cloud)
Connor Brewster Senior SWE (public) cbrewster bio: "Software Engineer @ Replit.com, Rust Enthusiast"
Jacky Zhao Engineer (public) jackyzha0 bio: "agent infra, distributed systems, and enjoying sunsets" - the closest public Replit handle to a "Staff+ infra" voice
Victor Fuentes Engineer (public) vlinkz bio: "Linux fan"; location San Francisco; @Replit - NixOS core contributor by history (nixpkgs, mobile-nixos, nixos-hardware, npkg, auxolotl-core) - the strongest signal for Replit's Nix/Tvix work
Faris Masad Engineer (public) masad-frost bio: "فارس" - no clear public signal
Emil Sayahi Engineer (public) emmyoh bio: "Professional code wizard" - San Francisco

(curl /orgs/replit/members returned 9 public members: amasad, Armster15, cbrewster, emmyoh, jackyzha0, masad-frost, pirroh, vieux, vlinkz. The other two - Armster15 and vieux - returned empty profiles via the GH API at fetch time; vieux is the GH handle of a former Docker maintainer unrelated to Replit infra by his own bio.)

2.2 GitHub org stats (github.com/replit)

  • 100+ public repos in the snapshot (paginated); verified org.
  • Flagships: replit/kaboom (2,738 star, JS game engine), replit/clui (1,236 star, TS), replit/ReplitLM (1,065 star, inference code), replit/polygott (398 star, base Docker image for eval), replit/prybar (262 star, language shim), replit/upm (1,158 star, universal package manager), replit/codemirror-vim (460 star), replit/desktop (148 star).
  • Nix footprint (the differentiator for this bucket):
    • replit/nixmodules - 45 star, Nix, last commit 2026-05-07. This is the canonical surface for Replit's internal Nix module catalog.
    • replit/nixpkgs-replit - 29 star, Nix.
    • replit/rippkgs - 166 star, CLI for indexing Nix expressions. Authored by Replit staff.
    • replit/go2nix - 1 star, Nix build system for Go; matches the JD 1.2 / 1.5 stack signals.
    • replit/codemirror-lang-nix - 18 star, Nix LSP / CodeMirror mode.
    • replit/blog - 20 star, "the code behind https://blog.replit.com/" (Next.js).
  • Agent surface:
    • replit/replit-gemini-extension - 20 star, Gemini CLI integration.
    • replit/replit-vscode - 69 star, "Replit in vscode".
    • replit/replit-ai-python - 16 star, AI library.
  • Blog author signature: Jacky Zhao (jackyzha0) co-authored the 2024-11-26 "So you suspect you have a memory leak..." post on Agent process memory.

2.3 Recent engineering blog posts that map to Scott's positioning (blog.replit.com)

  • 2026-06-09 - Package Firewall: Blocking 8,000+ malicious packages daily (Engineering). "Replit already scans your projects for vulnerable dependencies... Today we're launching Package Firewall, in partnership with Socket (a software supply-chain security company)." - direct supply-chain integrity signal. Quotes Feross Aboukhadijeh (Socket CEO).
  • 2026-06-10 - Customize Replit Agent with Skills and Custom Instructions (Engineering). "Custom Instructions are always-on guidelines injected automatically into the agent's context on every project, every session." - Scott's "judgment transport utility" framing is a custom-instructions superset.
  • 2026-05-29 - (no standalone post - the Staff Infra Engineer posting goes live same day)
  • 2026-05-07 - Security Center 2.0: Act on vulnerabilities in bulk across all your apps (Engineering). Bulk-CVE remediation across published apps.
  • 2026-04-29 - Introducing Replit App Monitoring (Engineering). Post-launch observability for published apps.
  • 2026-04-22 - Decision-Time Guidance: Keeping focus and avoiding rule explosions at key moments rather than front-loading all rules (Engineering). The closest match to Scott's "decision provenance" frame.
  • 2026-03-11 - Introducing Replit Agent 4: Built for Creativity (Featured). The current flagship Agent release.
  • 2026-01-20 - (Nix on Replit origin post, archived) - Announced "Nix on Replit" with a 1 TB content-addressed store.
  • 2025-03-05 - Using Tvix Store to Reduce Nix Storage Costs by 90% (Engineering). Replit's own Tvix reimplementation work. Direct overlap with the Flox bucket's Nix provenance story.
  • 2024-11-26 - So you suspect you have a memory leak... (Engineering). Agent-process memory debugging narrative. Co-author signature matches Jacky Zhao.

2.4 LinkedIn

  • Company slug: linkedin.com/company/replit (auth-walled; not fetched anonymously).
  • Amjad Masad's slug is amasad on GH and reachable via LinkedIn search but not by anonymous scrape.
  • No public engineering handles (jackyzha0 / cbrewster / vlinkz) are first-class LinkedIn slugs.

2.5 Hiring-manager / "who would review this resume"

  • Staff SWE, Replit Cloud (1.1) reports explicitly to the Vice President of Engineering - Scott Kennedy is the named VP of Engineering on replit.com/about. He is the hiring manager of record for the highest-priority role.
  • Engineering Manager, Enterprise Platform (1.7) is itself a hiring manager - the line manager for the cluster of Enterprise Platform SWEs (1.3) and the EM's name appears in the JD as the team lead. No public LinkedIn slug is exposed; entry is via Ashby.
  • CTO Luis Hector Chavez is the executive sponsor for the Platform org by org-chart inference (named CTO on about page, no public GH).
  • No recruiter handle is exposed on any JD; Ashby routes apply forms anonymously.

3. Artifact plan - Replit Agent x Speckl (the "agent-output provenance anchored in the workspace" story)

3.1 The pitch in one paragraph

A Replit workspace is already a content-addressed Nix environment - replit.nix pins the package set, Nix store paths are the underlying substrate, Tvix is Replit's own reimplementation of the store. A Replit Agent session is therefore already running on a byte-stable substrate; what it doesn't have is a byte-stable record of what it wrote. The artifact we ship proves the two can be linked: a Replit Agent session that produces a Speckl .speckdl file emits, in the same workspace commit, a PROV-O/CycloneDX/SPDX provenance manifest that cites the Nix store path of the running environment as the agent's substrate. The result is "the Agent wrote X" + "the Agent ran inside this exact Nix store path" + "the type-checker that compiled X is the compiler at store path Y" - all byte-attributable in a single signed artifact.

3.2 Why neither side has shipped this alone

  • Replit Agent produces code, but the provenance of what it produced (which model, which prompt, which tool calls, which workspace state) lives in Replit-internal telemetry. The developer receives a diff, not a provenance bundle.
  • Speckl produces a four-artifact provenance bundle (PROV-O JSON-LD + CycloneDX + SPDX + TS class) per .speckdl, but the runtime substrate hosting the Speckl compiler is whatever the developer brought (Docker, k8s, local Nix). Today, that substrate is not content-addressed inside the artifact.
  • The pair: Replit's Nix store is the substrate; Speckl's PROV-O is the ledger. Together: "the Agent ran inside store path /nix/store/abc... and produced a TypeScript class whose PROV-O graph says it came from model M with prompt P at time T." This is the same shape as the Flox artifact (job-flox sec 3) but anchored at the workspace layer, not the team-env layer.

3.3 Deliverable (skeleton)

A single repo (this one) with:

  1. replit.nix - pins the Speckl compiler by URL+SHA, plus nodejs, python3, jq, git. Reproducible on any Replit workspace via the existing replit.nix config model.
  2. .replit - run command: bash scripts/build.sh. Sets [env] SPECKL_REF=... and [deployment] deploymentTarget=cloudrun.
  3. specs/AgentProvenance.speckdl - a fresh .speckdl that models the Agent provenance flow itself (input event -> model call -> tool call -> emitted artifact). Audit-friendly because it's small and self-referential.
  4. scripts/build.sh - single command that runs the Speckl compiler against the spec, emits the four-artifact bundle, and signs the bundle against the Nix store path of the compiler.
  5. out/AgentProvenance.prov-o.jsonld + out/AgentProvenance.cyclonedx.json + out/AgentProvenance.spdx.json + out/AgentProvenance.ts - committed, byte-stable, hashed.
  6. docs/reproducibility.md - one-page narrative: "I imported this repo into Replit, hit Run, and got the same SHA-256 hashes Replit's CI got. Here's the chain from replit.nix -> store path -> compiler invocation -> emitted artifact."
  7. (Stretch) a Replit Agent Skill (SKILL.md at repo root) that auto-runs scripts/build.sh whenever the Agent emits a new .speckdl file. This is the Custom Instructions / Skills (2026-06-10) feature applied to provenance - direct alignment with Scott's "judgment transport utility" frame.

3.4 Mapping to Replit's actual primitives

Replit surface What it does in this artifact
replit.nix Pins the Speckl compiler by pkgs.fetchurl { url, sha256 }. Reproducible across hosts.
.replit [env] SPECKL_REF, SPECKDL_SRC, OUT_DIR - fed to scripts/build.sh
.replit [deployment] deploymentTarget=cloudrun Replit Cloud Run hosts the demo; ties to JD 1.1 (Replit Cloud)
Nix store path The pkgs.fetchurl output is the byte-stable substrate reference in PROV-O
Replit Agent Skills SKILL.md instructs the Agent to invoke scripts/build.sh on every .speckdl emit
MCP connector The Agent can fetch the Speckl compiler from a private MCP server with its own provenance
Package Firewall The build script verifies the compiler SHA matches the SHA declared in replit.nix - uses the same Socket-based scanning that Package Firewall ships

3.5 Mapping to Speckl's compiler output

The Speckl compiler (sscoble/speckl on this Forgejo) emits four artifacts per .speckdl source. The artifact just feeds it a Replit-Nix-resolved source path. The compiler is deterministic, so same input -> same four outputs, byte-identical, hash-stable.

3.6 Outreach angle (when the time comes)

Not for the apply form. For:

  • VP of Engineering Scott Kennedy - JD 1.1 (Staff SWE, Replit Cloud) explicitly names him as the hiring manager. The artifact IS a working "Replit Cloud" demo: a SpeckDL spec compiled inside a Nix-pinned Replit workspace, with provenance anchored at the Nix store path. This is the exact intersection of JD 1.1's "Replit Agent + cloud infrastructure" stack and Scott's "human-maximizer + supply-chain" frame.
  • Engineering Manager, Enterprise Platform (JD 1.7) - owns BYOK / single-tenant / data residency. Speckl's PROV-O/CycloneDX/SPDX bundle slots cleanly into the BYOK story (provenance keys managed by the customer, the artifact is attestable without Replit-side trust).
  • Staff Infrastructure Engineer (JD 1.5) - Terraform / Kubernetes / GCP focus. The artifact's replit.nix is the workspace-side analog of the Terraform module they own on the infra side - same shape, different layer.
  • Staff Software Engineer, Agent Platform (JD 1.4) - the "Multiplayer Computer" + MCP interfaces. The Speckl Agent Skill (section 3.3 item 7) is a new Agent capability (provenance emission) that fits directly into JD 1.4's "durable, well-crafted interfaces between the Agent and internal systems, as well as external agentic systems (MCP)" remit.
  • Public handles (warm, low-friction outreach surfaces):
    • jackyzha0 (Jacky Zhao) - bio is literally "agent infra, distributed systems". 55+ public repos, most active in Rust/TS, distributed-systems focus (Raft, CRDTs, Maelstrom). Authored the 2024-11-26 Replit memory-leak post. Strongest external technical voice in the Replit infra org.
    • vlinkz (Victor Fuentes) - NixOS core contributor by history. If Replit's Tvix work has a public author, this is the most likely handle. Pinging him on the Tvix post would be a low-noise way to surface the artifact's Nix-anchored provenance story.
    • cbrewster (Connor Brewster) - Rust enthusiast at Replit. Relevant if the Speckl compiler's Rust surface ever needs a Replit-side reviewer.

3.7 Status

Plan only. No artifact built yet. When built, the artifact lives at sscoble/speckl (compiler) + this repo (Replit workspace). Build sequence:

  1. Choose a .speckdl spec that's small enough to audit end-to-end (suggest: AgentProvenance.speckdl modelling the Replit Agent emission flow itself).
  2. Write the replit.nix pinning the compiler version (current Speckl compiler release).
  3. Get the SHA-256 chain to be byte-stable across two Replit workspaces on different hosts.
  4. Publish the artifact as a Replit App (template fork) - gives the demo a permanent URL.
  5. Write the reproducibility.md narrative as a blog-post-shaped artifact that doubles as the outreach asset, potentially cross-posted to the Replit community feed.

4. Outreach log (empty - do not contact)

Per directive: surface only. No contact made. This section is a placeholder; entries will be appended as the artifact matures and a single warm-intro path is identified. Most likely first touch: a thoughtful reply to jackyzha0's next public post (Raft / CRDT / Agent infra topic) once the artifact is built, not an apply-form submission.

Date Channel Target Topic Outcome
- - - - -

5. Source URLs (cited for verification)


Repo created by Marcus (job-pipeline agent) on 2026-06-18 from /home/sscoble/job-pipeline/job-replit. Surfacing only - no contact made.