Software Engineer

Job Description

Role: Software Engineer

\n

Location: New York City | Monday–Thursday in office, Friday WFH

\n

Salary: $150K–$250K base + equity

\n

\n

I’m working with an early-stage NYC startup looking for an experienced Software Engineer to join a small, high-performing engineering team.

\n

\n

This isn’t a role where you’ll join a large engineering organisation and spend your time picking up predefined tickets.

\n

\n

They’re looking for engineers who have operated in flat, highly autonomous environments, where you’re trusted to understand the problem, decide how to solve it and then take ownership of building and shipping the solution.

\n

\n

The opportunity

\n

\n

You’ll be joining at a stage where individual engineers can have a genuine impact on the product and technical direction of the business.

\n

\n

The team operates with very little hierarchy and a high level of ownership. You’ll work closely with other engineers and the wider business, contributing to both what gets built and how it gets built.

\n

\n

A major part of the role is 0→1 engineering.

\n

\n

You’ll be tackling problems where there may not be an existing solution, established architecture or perfectly defined roadmap.

\n

\n

You could be:

\n

\n
• Designing and building new products and features from scratch
\n
• Taking products from concept through to production
\n
• Making key architectural and technical decisions
\n
• Solving ambiguous technical and product problems
\n
• Owning projects end-to-end
\n
• Shipping quickly and iterating based on real-world feedback
\n
• Improving the architecture as the product and customer base scales
\n
• Helping establish engineering standards and best practices
\n
• Working directly with the wider team rather than through layers of management
\n

\n

\n

Tech stack

\n

\n
• Python / TypeScript
\n
• React / Next.js
\n
• Node.js
\n
• PostgreSQL
\n
• AWS
\n
• Docker / Kubernetes
\n
• Modern cloud infrastructure and CI/CD tooling
\n
• GO (desirable)
\n

\n

\n

You don't necessarily need to have worked with every technology in the stack.

\n

\n

They’re much more interested in finding strong engineers who can learn quickly, make good technical decisions and take complete ownership of what they build.

\n

\n

What they’re looking for

\n

\n

The biggest requirement is having already demonstrated that you can operate with autonomy in an early-stage environment.

\n

\n

Ideally, you’ll have:

\n

\n

\n
• Strong commercial Software Engineering experience
\n
• Previous early-stage startup experience
\n
• A track record of building products or major features 0→1
\n
• Experience working within a flat organisational structure
\n
• Strong backend and/or full-stack engineering skills
\n
• Experience designing scalable production systems
\n
• The ability to own projects from initial idea through to deployment
\n
• Strong product thinking alongside technical ability
\n
• Confidence making technical decisions without excessive oversight
\n
• Experience working through ambiguity and finding solutions independently
\n
• A bias towards building, shipping and iterating
\n
• The ability to move quickly without sacrificing engineering quality
\n

\n

\n

This is particularly suited to someone who has previously been an early or founding engineer, or has worked in a startup environment where engineers are expected to take significantly more ownership than they would in a traditional engineering organisation.

\n

\n

Interested?

\n

\n

If you’re a Software Engineer in NYC who has built 0→1, thrives with autonomy and wants genuine ownership over what you build, please apply with an up to date resume.