JobsFlow

See the output before you sign up.

Here's what JobsFlow produces for one fictional candidate, Maya, a platform engineer in Bengaluru applying for roles in Amsterdam. The people and companies are made up. The formats, limits and checks are the real ones.

A resume tailored to one posting.

The one-page A4 PDF JobsFlow generates, next to the check the app shows for it. Same layout as the master resume; only the Skills, Experience and Projects text is rewritten for the posting.

Sample · fictional candidateGenerated resume for Platform Engineer, Ledgerline
Maya Kapoor

maya.kapoor@example.com | linkedin.com/in/example | github.com/example | Bengaluru, India

Skills

Infrastructure: Kubernetes (EKS), Terraform, AWS (EC2, RDS, IAM, VPC), Docker, Argo CD
Languages: Go, Python, SQL, Bash
Delivery and reliability: CI/CD with GitHub Actions, Prometheus, Grafana, OpenTelemetry, on-call, incident response, SLOs
Data: Postgres, Redis, Kafka

Experience

Platform Engineer, Infrawise, Bengaluru | Mar 2022 – Present

  • Run 40 services on Kubernetes (EKS) across two AWS regions for a 60-person engineering team; moved the last 12 services off EC2 with no customer-facing downtime.
  • Rebuilt all deployments as Terraform modules across three AWS accounts, replacing hand-written scripts and cutting new-environment setup from two days to under an hour.
  • Set up Prometheus, Grafana and OpenTelemetry, and the SLO dashboards product teams now use to debug their own services.
  • Share the platform on-call rotation and take part in incident response, writing postmortems and tracking their follow-up actions to closure.
  • Built a Go CLI that creates a preview environment for every pull request, now used by 9 teams.
  • Moved CI/CD from Jenkins to GitHub Actions and Argo CD, taking the median deploy from 25 minutes to 6.
  • Wrote the Kubernetes upgrade runbook and ran four EKS version upgrades without a failed rollout.
  • Added per-team AWS cost alerts, which flagged idle RDS instances worth $4,000 a month that were then removed.
  • Standardised service templates with health checks, Prometheus metrics and Terraform-managed IAM roles, so a new service ships with them by default.
  • Mentor two junior engineers and run fortnightly platform office hours for product teams.

Backend Engineer, Corvid Labs, Pune | Jul 2019 – Feb 2022

  • Wrote the billing service in Go on Postgres, handling payouts for 3,000 merchants.
  • Partitioned the largest Postgres tables and added read replicas, taking p95 report queries from 9s to 800ms.
  • Moved the test suite into a CI/CD pipeline on GitHub Actions, cutting release time from a day to an hour.
  • Added structured logging and Prometheus alerts on the payments path, which caught two failed-payout incidents before merchants reported them.
  • Containerised the four core services with Docker ahead of the company's move to Kubernetes.
  • Designed idempotent retries for the payouts queue on Redis, which ended duplicate payouts.
  • Moved the main database from a self-managed Postgres instance to AWS RDS with point-in-time recovery.
  • Shared the backend on-call rotation and wrote the first incident response checklist for the payments team.

Software Engineer, Tessellate Systems, Bengaluru | Jun 2018 – Jun 2019

  • Built internal REST APIs in Python and Postgres for the operations team's order tooling, used daily by 40 staff.
  • Joined the support on-call rotation and fixed the order-sync bug behind most weekend incidents.
  • Wrote the runbooks for the support rotation, documenting the five most common fixes and cutting repeat tickets.
  • Automated nightly database backups and restore checks with Bash and cron.
  • Wrote a Python job that reconciled orders against the payment provider each night and flagged mismatches.
Projects

kube-cost-report | Open source, 600 GitHub stars

  • Go CLI that breaks a Kubernetes bill down by team and namespace from AWS cost and usage reports.

terraform-aws-baseline | Internal, Infrawise

  • Reusable Terraform modules for VPC, IAM and RDS defaults, used across every Infrawise AWS account.

pg-migrate-check | Open source

  • Go linter that flags Postgres migrations likely to lock large tables, run in CI/CD before merge. Adopted by two other startups.
Education

B.Tech, Computer Science | 2014 – 2018
Final-year project: a distributed log collector written in Go.

Certifications

Certified Kubernetes Administrator (CKA), 2023 | HashiCorp Certified: Terraform Associate, 2022
AWS Certified SysOps Administrator – Associate, 2021

  • Your resume, reworded. Employers, titles and dates come straight from the master resume. Nothing is invented.
  • Missing isn't the same as a gap. Linux and Ansible are on Maya's master resume but didn't make this page. GCP isn't on it at all, so it isn't added and doesn't count against her.
  • One page, checked. The page count is read from the rendered PDF, and every employer has to survive.

A tracker with the next step on every row.

Six applications, one follow-up due today. Status, next step and date, nothing else.

Sample · fictional search6 applications · 1 follow-up due today
RoleStatusNext stepFollow up
Platform EngineerLedgerlineReferral sentFollow up with DaanToday
Site Reliability EngineerNorthwindAppliedNudge the recruiterThu
Infrastructure EngineerKestrelInterviewingSend a thank-you noteFri
DevOps EngineerTripwellResume generatedFind someone to askMon
Cloud EngineerRelaybirdSavedTailor the resumeNo date
Platform EngineerDunecartRejectedClosed
  • Due dates lead. What needs you today is at the top, and shows up on your Today page too.
  • Statuses move on their own. Generating a resume or drafting a referral moves the application forward.

Outreach to one named person.

A connection note, the follow-up once they accept, and an email to the recruiter. Each one is a draft you edit and send yourself.

Sample · fictional peopleDrafts only. Nothing is sent until you send it
Connection note164 / 200

To Daan de Vries · Staff Engineer, Ledgerline

Hi Daan, I saw Ledgerline is hiring a Platform Engineer. I run Kubernetes and Terraform at Infrawise and would love to hear how your team works. Open to connecting?

Follow-up322 / 600

To Daan de Vries · accepted 3 days ago

Thanks for connecting, Daan. I've applied for the Platform Engineer role. The part that caught my eye is the move to infrastructure as code, which is most of what I've done at Infrawise over the last two years. If you think I'd be a fit, would you be open to referring me? Happy to send my resume or answer anything first.

Email to a recruiter

To Ines Moreau · Technical Recruiter, Ledgerline

Subject: Platform Engineer application: Maya Kapoor

Hi Ines, I've applied for the Platform Engineer role at Ledgerline: ledgerline.example/jobs/platform-engineer The move to infrastructure as code in the posting is most of what I've done at Infrawise over the last two years, across 40 services on Kubernetes. My resume for this role is here: drive.example/maya-kapoor-ledgerline.pdf Happy to answer anything. Thanks, Maya

  • Inside LinkedIn's limit. Connection notes are held to 200 characters in code, not left to the model.
  • Specific, not templated. Each draft names the role and one concrete reason it's worth their time.
  • Links included. The email carries the posting and the resume tailored for it.

Get these for your own search.

Paste your resume once. The search, fit scores and tracker are free.

Start freeSee pricing