Engineering Intern: Build Real Tools, Own a Workflow

String; New York (NY); Hybrid; USD 34,000 - 44,000; Full time

Job summary

String builds infrastructure that lets software agents access and collect public web data. As an engineering intern, you will work with Logan and the team on real systems from day one, starting with running existing tooling, identifying inefficiencies, and shipping a small fix.

You will take ownership of a tool or workflow, improve it end-to-end, and build a process that a teammate still does by hand. Most work is TypeScript and shell, with some Go and Python, and you will collaborate via

Qualifications

• Comfort with Git and at least one programming language.
• Most work is TypeScript and shell; some Go and Python.
• No specific degree, GPA, or prior internship required; ability to work with us in New York City part of the week.

Responsibilities

• Use our tools on real tasks and document surprises.
• Ship a small pull request early on.
• Take one existing agent workflow apart, understand how it works, and make it better.
• Build a tool for a process a teammate still does by hand.
• Investigate failures, write tests, review code, and explain decisions behind changes.
• Work directly with Logan and other engineers through tickets and PRs.

Skills

TypeScript

Shell scripting

Go

Python

Tools

Git

Job description

Location New York City, in person for part of the week

I'm Logan, String's CTO. I'm looking for an engineering intern to work with me on the tools our engineers and coding agents use every day.

You will work on real systems from the start: agent workflows, the command-line tools we use to coordinate work, and the web access infrastructure behind our product. You will begin by running what already exists, finding where it wastes time or behaves unexpectedly, and shipping a small fix. From there, you will take ownership of a tool or workflow and improve it end to end.

What String does

String builds infrastructure that lets software agents access and collect public web data. We process more than 200 million pages each week. The hard part is handling the web that comes back: bot defenses, changing sites, unreliable data, and the operational work required to keep all of it running.

Our engineering team uses coding agents heavily. We build our own workflows and tools to make several agents useful at once without letting them collide, repeat work, or quietly make the wrong call.

What you will do

• Use our tools on real tasks and write down what surprises you.
• Ship a small pull request early on. It might fix a broken skill, improve a script, add a missing test, or remove a rough edge you found firsthand.
• Take one existing agent workflow apart, understand how it works, and make it better.
• Build a tool for a process a teammate still does by hand.
• Investigate failures, write tests, review code, and explain the decisions behind your changes.
• Work directly with Logan and other engineers. Your work will go through the same tickets, reviews, and pull requests as everyone else's.

By the end of your first month, you should have shipped several changes and owned one workflow yourself.

Who should apply

You have built something you care about and can explain the choices you made. It does not need to be a startup or a polished app. A useful script, an open source contribution, a research tool, a game, or a strange personal project all count.

You should be comfortable with Git and at least one programming language. Most of this work is TypeScript and shell, with some Go and Python nearby. We care more about how you work through an unfamiliar system than whether you already know our stack.

You probably use coding agents already. Using them is not the skill we are hiring for. We care whether you can tell when the output is wrong, design a test that would catch it, and make a good call when the tool cannot make one for you.

You do not need a particular degree, school year, GPA, or previous internship. You do need to be able to work with us in New York City for part of the week and enter a lawful contractor engagement where you live.

• A conversation with Logan about what you have built, what you want to learn, and the work here.
• A code walkthrough with an engineer. Bring a project you know well and walk through your decisions. There is no algorithm quiz and no whiteboard puzzle.
• A working session in our New York office on a small, self-contained tooling problem. You do not need to prepare anything in advance.

Then we make a decision.

Apply for the internship

Tell us about something you have built and how you work through unfamiliar engineering problems.

Full name

Email address

Project link

Share a project, repository, demo, or write-up you can walk us through.

Tell us about your project

What did you build, what decisions did you make, and what would you change next?

Working with coding agents

Describe a time a coding agent got something wrong. How did you notice, and what did you do? If you have not used one, describe how you checked your own code instead.

Can you work with us in New York City for part of the week?

Resume or profile link (optional)

A resume, personal website, or professional profile is optional.

We use your answers to review your application. Read our privacy policy .