Software Engineer
Trovy
- Location
- New York City
- Employment
- Full Time
- Work model
- On-Site
- Level
- Mid
- Salary
- $110k – $115k/yr
- Posted
- 2h ago
Skills
About this role
About Trovy Trovy is building the financial home base for America's 86 million homeowners — the go-to platform for managing your home and accessing low-rate credit, because life is expensive and unpredictable. We believe your biggest asset should unlock your best financial options: bypass the myriad of expensive, rigid credit products and replace them with one simple, powerful solution built around your home equity. Backed by top-tier venture capital, Trovy is led by a team of proven fintech innovators on a mission to make homeownership and personal finances more manageable. Don't own a home without it.
Role
Overview We're looking for a Software Engineer, a hybrid of engineering and cross-functional problem-solving. You won't just write code; you'll embed with the teams that run our business: Operations, Support, Compliance, and Finance. Your job is to understand how they work, find the friction, and build the internal tools that make them faster, smarter, and happier. If you're the kind of person who talks to users, sketches on a whiteboard, ships something by end of week, and iterates based on real feedback, this is the role for you. This is an entry-level role designed for someone early in their career who wants to see how a real fintech company operates end to end.
What You'll Do
Embed with internal teams: sit with ops, support, compliance, finance teams to understand their workflows, pain points, and manual processes ripe for automation. Build internal tools and admin panels: ship features that reduce manual work, prevent errors, and speed up decisions across the company (think: ticket triage dashboards, workflow automations, metrics dashboards etc.). Own small-to-medium projects end-to-end from scoping with stakeholders through design, implementation, testing, rollout and maintenance. Wire up observability: add monitoring, alerting, and dashboards so teams can see what's happening in their tools without asking engineering. Write clean, tested code primarily in Kotlin with Spring Boot on the backend, plus some frontend work for admin UIs Document what you build: write clear runbooks and guides so the tools live on beyond the person who built them Participate in code reviews, standups, and team rituals: you're a full member of the engineering team from day one.
What We're Looking For
You're graduating (or recently graduated) with a degree in Computer Science, a related field, or equivalent practical experience. You've built something end-to-end: a side project, hackathon app, open-source contribution, or class project and can talk through the decisions you made. You've used AI coding assistants (Claude Code, Copilot, Cursor, etc.) as part of your workflow and can articulate when they help and when they don't — you treat AI as an accelerator, not a crutch. You're comfortable with at least one backend language (Kotlin, Java, Python, Go, TypeScript. We use Kotlin, but we'll teach you). You have a working knowledge of databases (SQL), APIs (REST), and version control (Git). You're curious about how businesses actually work — you care about the why behind the feature, not just the how . You communicate clearly and aren't afraid to ask questions, challenge assumptions, or say "I don't know". You're excited to work in-person in NYC, pairing with teammates and walking over to the desk of the person whose problem you're solving.
Nice to Have
Experience with Spring Boot, Kotlin, or JVM-based services. Exposure to frontend development (React, HTML/CSS) — enough to build a functional admin panel - Familiarity with event-driven systems, queues, or webhooks. Interest in fintech, homeownership, or consumer finance. Prior internship experience at a startup or fast-paced engineering team. What You’ll Learn How to leverage AI coding assistants (Claude Code) in a professional engineering workflow — not just autocomplete, but using AI for code review, debugging, test generation, and navigating large codebases. How to ship