A draft, then the role it's for

One application at a time, in your own words. Here's the shape of the work from first draft to finished resume.

01

The work

Three movements, in order

A case isn't built in one sitting and it isn't built by a button. The work moves through a draft, a tailoring, and a finish, each one earns the next.

  1. 01

    Draft

    Write the case once, in your own words. The resume holds your full record so you aren't starting from a blank screen for every role.

  2. 02

    Tailor

    Point a draft at one role. reecv reads the role with you and suggests where the case can lean closer to the fit; you decide what stays.

  3. 03

    Finish

    Sit with the resume until it reads the way you want it to. Export when it's finished, not before.

Theo Marchetti

Staff platform engineer · reliability and infrastructure

theo@marchetti.devBoston, MAmarchetti.devgithub.com/tmarchetti

Summary

Eleven years on platform teams at small-to-mid-sized companies. Last four years split between incident response and the infrastructure work that prevents repeat incidents. Looking for a staff or principal role where the platform is the product.

Experience

  • Staff Platform Engineer

    Rivermark • Boston, MA

    Jan 2023 — Present

    • Cut p99 API latency from 940ms to 280ms by replacing a synchronous billing webhook fanout with a queued retry layer; landed inside one quarter against an original two-quarter estimate.
    • Owned the on-call rotation rebuild, wrote the runbooks, ran the post-incident reviews, and cut average mean-time-to-resolve from 47 minutes to 12 over six months.
    • Led the migration of a 240-instance fleet from EC2 to ECS Fargate, retiring two pager-rotation roles in the process.
    • Mentored the two senior engineers who took over the on-call captaincy; both promoted to staff within a year.
  • Senior Site Reliability Engineer

    Honeycomb • Remote

    Mar 2020 — Dec 2022

    • Built the internal observability layer the customer-facing product team now uses; reduced time-to-detection on customer-impacting issues from 22 minutes to under 4.
    • Authored the team's incident review template; still in use, picked up by two acquirers during the M&A diligence cycle.
    • Ran the reliability hiring pipeline through 2021, interviewed 90+ candidates, made eight hires, two still on the team today.
  • Software Engineer

    Stitch Fix • San Francisco, CA

    Aug 2016 — Feb 2020

    • Shipped the inventory-allocation service that replaced a nightly Spark job with a sub-second API; the service is still in production seven years later.
    • Co-led the platform team's adoption of Kubernetes, wrote the migration playbook, ran the workshops, kept the rollout to a single quarter.

Education

  • Carnegie Mellon University

    BS • Computer Science

    2014

03

Stances

Authorship, in plain terms

The writing is yours. The decisions are yours. reecv suggests; you keep or refuse. Nothing leaves the resume until you say it's finished, and nothing about your record is reused outside the case you're making.

Join the list and draft in your own words

Join the waitlist

Free to draft once you're in. No card on file.