Who Gets Hired, What It Pays, and Which Lanes Exist
A six-founder logistics marketplace in New York runs no graduate program. It posts eight roles, pays $100K to $300K, and expects every hire to own a piece of the product from day one. The question isn't whether you're qualified — it's whether you match one of the narrow lanes this team actually funds.
Porter lists six founders on its board page: Justin Rhee, Uttam Digga, Pranav Goel, Vikas Choudhary, Trevor Shim, and Alexander Belanger. That founder-to-role ratio (6:8) signals a team still close to the code. The board shows eight salaried openings, all technical, all New York-based except one remote DevOps role. Median posted band: $200K (Zero G Talent's figures put the median at $200K). Top of band: $300K for a Founding Security Engineer (Zero G Talent board data reported). The spread, $100K at the low end for a Growth/Product Engineer or Backend Engineer (Go), reflects a deliberate choice: pay senior IC rates for focused scopes, not management ladders.
| Role | Location | Salary Band (USD/yr) |
|---|---|---|
| Founding Security Engineer | New York, NY | $200K–$300K |
| Staff Frontend Engineer | New York, NY | $200K–$280K |
| Staff Infrastructure Engineer | New York, NY | $200K–$280K |
| Frontend Engineer | New York, NY | $150K–$200K |
| Backend Engineer (Go) | New York City | $100K–$200K |
| Full Stack Engineer | New York City | $100K–$200K |
| Growth/Product Engineer | New York City | $100K–$200K |
| DevOps Support Engineer | Remote | $120K–$180K |
Source: Zero G Talent board postings for Porter: Founding Security Engineer, Staff Frontend Engineer, Staff Infrastructure Engineer, Frontend Engineer, Backend Engineer (Go), Full Stack Engineer, Growth/Product Engineer, DevOps Support Engineer.
The role slate maps to three product surfaces. Frontend and full-stack seats, including Frontend Engineer ($150K–$200K), Staff Frontend Engineer ($200K–$280K, as Zero G Talent board data found), and Full Stack Engineer ($100K–$200K), own the user-facing layer. Backend and infrastructure roles, including Backend Engineer (Go) ($100K–$200K), Staff Infrastructure Engineer ($200K–$280K), and DevOps Support Engineer ($120K–$180K, remote, according to Zero G Talent board data), own reliability and scale. The Growth/Product Engineer sits at the intersection. The Founding Security Engineer ($200K–$300K) stands alone: build the security program from zero.
No QA, no SRE, no technical program manager, no designer roles appear on the board. That absence is the signal. Porter hires engineers who ship complete features (design decisions, test strategy, deploy pipeline, incident response) without handoffs. The "Staff" titles at $200K+ aren't people-management slots; they're scope anchors for the hardest technical surfaces (rendering performance, distributed systems correctness, security architecture). Candidates who need a spec handed to them won't clear the bar.
The founder roster reinforces the profile. Six technical founders building in New York means the people writing the checks also review the PRs. Applicants should expect interviews that look like design reviews with peers, not behavioral screens with recruiters. The single remote role (DevOps Support) is the exception that proves the rule: the core team sits together in NYC because the work still benefits from shared context and fast iteration.
The $100K floor across most IC roles exceeds typical early-career bands at comparable-stage startups and functions as a filter. Candidates who clear the process are already operating at a level where they'd command that floor elsewhere. The $286K ceiling (the staff roles' upper bound), as Zero G Talent's board data shows, leaves room for exceptional hires without breaking the band structure. Founders set compensation directly; there's no HR ladder to negotiate through. The number on the offer letter reflects the specific gap the hire fills: security architecture, rendering performance, deployment scale — not a leveling matrix. Applicants who treat the band as a negotiation range rather than a signal of expected scope tend to stall in the process.
For a candidate, the takeaway is binary. You target one of these eight lanes with concrete evidence you've owned that exact surface: frontend performance at scale, Go services in production, security program build-out, infrastructure automation — or you don't apply. Generic "full-stack" resumes without a depth spike in one of the posted specialties get filtered before a human sees them. The team is small, the bar is high, and the bands are public. Match the lane. Prove the ownership. That's the entire game.
How the Hiring Process Tests Depth
Porter's interview loop moves fast and skips the traditional whiteboard. For software engineering roles, the process centers on a live sandbox coding round: candidates write and run code in a real environment while interviewers probe edge cases and scaling decisions. The technical surface area is explicit: SQL, Python, and data structures and algorithms are heavily emphasized, with a strong focus on case study analysis, low-level and high-level design, and system design.
The funnel varies by role family but follows a consistent pattern: an application screen (résumé plus eligibility), a skills assessment with role-specific problems, a behavioral or panel round evaluating ownership and fit, then offer and onboarding logistics. Recruiter screens act as the first filter; the screen looks for concrete evidence: shipped systems, scale numbers, ownership of outcomes, not narrative polish.
Strong applications mirror the board's posted roles. Candidates who clear the screen typically show: a match to one of these exact functions, not a generic "software engineer" pitch; quantified impact on systems comparable to Porter's stack (Go, React, distributed infrastructure); and a portfolio or GitHub trail that survives a live code review.
Disqualifiers are practical. Candidates who lead with benefits, hours, or vague "culture" questions signal low ownership. The behavioral round tests whether you can articulate how your past decisions would map to Porter's product problems. Refusing the live sandbox, treating the case study as a theoretical exercise, or failing to explain a design trade-off you actually made ends the process.
The system design and case study rounds are where the band separates. The emphasis on both levels of design means candidates who only operate at one altitude struggle. The case study isn't a take-home — it's a working session. Interviewers expect you to ask clarifying questions, state assumptions, and iterate. Porter's founders sit on panels for senior roles. They're evaluating whether you can operate at the pace the board data implies: a small New York team shipping across security, growth, infrastructure, and product simultaneously.
The timeline compresses. The process is mid-funnel, meaning the screen-to-offer window is short for candidates who match the function. Applicants who treat the application as a spray-and-pray rarely reach the sandbox. The ones who do have already decided which of the eight live roles they're built for, and they prove it in the first 15 minutes of the recruiter call.
Where the Work Happens
Porter operates from New York headquarters. First-party board data shows seven of eight current salaried roles based in New York City or New York, NY, US; only the DevOps Support Engineer post is marked Remote, signaling that physical presence at the Manhattan site is the default for engineering, security, and infrastructure functions.
That remote role (DevOps Support Engineer, $120K–$180K) suggests a narrow exception for infrastructure work that can be done off-site. Candidates targeting the Founding Security Engineer, and Staff Frontend Engineer, and Staff Infrastructure Engineer, or any of the full-stack, backend, or growth/product roles should expect their day-to-day to intersect with the New York hub.
Who Thrives Here
Employee-review data tells a clear story: Porter scores 3.64 on work-life balance and 3.46 on culture (its two strongest signals), while career growth sits at 2.85, the weakest. Fifty-two percent of reviewers would recommend the company to a friend. That pattern selects for people who value autonomy and a sustainable pace over rapid promotion, and who can operate without a layered management structure handing them work.
The lean New York team, built around a handful of senior engineers and the six founders, operates in a high-velocity logistics environment where last-mile demands daily recalibration. The people who last treat that ambiguity as a design constraint, not a bug.
What filters out? The career-growth score suggests that anyone expecting a structured ladder, mentorship programs, or title inflation will frustrate fast. The 52-percent recommend rate means nearly half the people who leave (or stay) see friction others don't. The trait that separates the two groups is simple: they treat the absence of guardrails as a mandate to build their own, and they document the build so the next person doesn't start from zero.
The lane you pick at application is the lane you own at hire. Six founders, eight roles — no one is coming to hand you a spec.
Working in frontier tech? Zero G Talent tracks the openings: see every open Porter role, browse frontier tech jobs, the companies hiring, and the people building the field.