Senior Software Engineer

Location: Remote, United States
Type: Full-Time Contract
Schedule: 40 hours/week

About Project vNext

Project vNext builds software for both internal products and external clients, with a primary focus on financial technology.

We're a small team that values ownership, pragmatism, discipline, and execution. We care more about an engineer's judgment, problem-solving ability, communication, and track record of delivering quality work than whether they've worked with a specific framework or technology before.

We're looking for a Senior Software Engineer with approximately 5–8 years of professional experience who can own meaningful technical work, turn ambiguous product or business needs into practical implementation plans, and remain highly hands-on while helping raise the quality and effectiveness of the engineering team.

What You'll Do

  • Own meaningful technical work across frontend, backend, infrastructure, and supporting systems
  • Turn ambiguous product or business needs into technical plans, milestones, and shipped implementations
  • Design and implement services, APIs, data models, integrations, and user-facing systems
  • Own meaningful architecture for services and features while discussing larger system direction with architects
  • Improve existing applications, services, deployment pipelines, observability, reliability, and maintainability
  • Lead technical discussions, code reviews, implementation planning, and tradeoff analysis
  • Mentor engineers through code review, pairing, feedback, technical guidance, and examples of strong execution
  • Set strong engineering patterns and contribute to team practices, documentation, maintainability, and overall engineering quality
  • Participate in client or stakeholder calls when implementation details, tradeoffs, or technical clarification are needed
  • Stay hands-on with implementation while helping the team make pragmatic technical decisions

Most of your work will remain hands-on engineering: designing, building, reviewing, debugging, and improving production software. Opportunities for greenfield development will arise as well.

Technology Stack

Our current stack includes:

  • Go
  • HTMX
  • Tailwind CSS
  • Templ
  • Connect RPC
  • PostgreSQL
  • Docker
  • AWS
  • ECS
  • Server-Side Rendering (SSR)
  • Native Mobile Applications

We favor simple, maintainable systems and server-rendered applications over complex frontend architectures whenever practical. We believe strong engineering comes from choosing the right level of complexity for a problem rather than adopting technology for its own sake.

Experience with every technology listed above is not expected, but candidates should expect to have meaningful experience with several of them or closely related technologies.

What We're Looking For

Required

  • 5–8 years of professional software development experience
  • Significant experience building, shipping, and maintaining production software in a professional environment
  • Experience with at least one strongly typed programming language such as:
    • Go
    • C#
    • Java
    • Kotlin
    • Rust
    • Swift
    • TypeScript
  • Ability to own meaningful technical work from ambiguous requirements through delivery
  • Strong practical design ability for services, components, APIs, data models, and feature-level architecture
  • Strong problem-solving ability, technical judgment, and ability to make pragmatic tradeoffs
  • Strong written communication skills
  • Ability to work effectively in a remote environment
  • Demonstrated ability to execute consistently, unblock others, and drive work forward with minimal supervision
  • Ability to learn unfamiliar technologies when required and help others adopt effective practices

Preferred

  • Experience with several of the technologies in our current stack or closely related tools
  • Experience with PostgreSQL or relational database design
  • Experience with Docker or containerized development workflows
  • Experience building web applications across both frontend and backend systems
  • Experience supporting production systems, debugging issues, improving observability, and participating in incident response or support processes
  • Experience with cloud platforms such as AWS
  • Open-source contributions, personal projects, startup experience, technical leadership, or other evidence of initiative and independent execution

Education

A Computer Science degree or related technical degree is welcome but not required.

For this role, we care more about professional work experience, ownership, technical judgment, mentorship, and demonstrated delivery than formal education.

What Success Looks Like

The ideal candidate is:

  • Product-minded, pragmatic, and delivery-oriented
  • Able to own outcomes across ambiguous or complex technical work
  • Comfortable making practical tradeoffs and explaining technical decisions clearly
  • Able to work through ambiguity, reduce uncertainty, and unblock others
  • Able to mentor engineers and improve team practices through practical examples, code review, and feedback
  • Comfortable giving and receiving feedback while continuing to learn
  • Disciplined, focused, and consistent
  • Committed to remaining hands-on while helping the engineering team improve

Compensation

Compensation is based on experience, demonstrated capability, and role responsibilities. The ranges below are annualized for a full-time contract role at 40 hours per week.

  • $160,000–$180,000 for Senior Software Engineer candidates who are not participating in on-call support responsibilities
  • $170,000–$200,000 for Senior Software Engineer candidates participating in light on-call support responsibilities

On-call expectations, rotation frequency, response expectations, and any additional support responsibilities will be discussed clearly during the hiring process.

Hiring Process

We keep the process concise and practical.

1. Manager Conversation

A discussion focused on background, interests, goals, and mutual fit.

2. Technical Exercise

A practical coding exercise focused on engineering fundamentals and problem-solving ability.

3. Architecture Discussion

A collaborative discussion focused on system design, tradeoffs, communication, and technical reasoning.

The entire process typically requires approximately two hours of candidate time.

How to Apply

Please provide:

  • Resume or LinkedIn profile
  • GitHub profile, if available
  • Brief description of projects you've built or contributed to
  • Professional references or recommendations, if available

We're particularly interested in candidates who take ownership, communicate clearly, make practical technical decisions, enjoy building software, keep learning, and consistently deliver high-quality work.