Kikoff Senior Software Engineer at Kikoff leading complex projects and owning systems behind financial products used by millions. Responsible for architecture decisions, cross-functional coordination, and production system reliability.
Responsibilities
Kikoff builds and operates financial products used by millions of people. Our engineers own the customer experience and the systems behind it, including onboarding, payments, subscriptions, and credit reporting.
As a Senior Software Engineer, you'll lead complex projects from shaping the opportunity through launch and own the systems you deploy. You'll work with product, design, marketing, and data to identify solutions, decide what and how to build, and measure and demonstrate the impact. You'll make architecture decisions within your projects, coordinate work cross functionally, and resolve tradeoffs between delivery speed, reliability, security, and long-term maintenance.
This is a hands-on role. You'll own the implementation and review the code, investigate production failures, and improve systems that customers already depend on. You'll use AI agents to ship high quality solutions across the stack and move work forward in parallel, with responsibility for the design, correctness, and production behavior of what you ship.
Define projects around customer and business outcomes. Use customer feedback and data to challenge assumptions, establish the expected impact, and choose a scope the team can deliver.
Lead delivery across multiple contributors and services. Turn ambiguous requirements into a technical approach and a sequence of releases, anticipate dependencies, and unblock work when plans change.
Design and implement complete customer flows. Own the decisions connecting user experience, APIs, data models, and external integrations, including retries, partial failures, and recovery.
Own your systems in production. Establish tests, monitoring, safe rollouts, and rollback plans. Respond to incidents, protect customers' credit, money, and data, and address the causes of recurring failures.
Be accountable for results after launch. Measure customer adoption, retention, reliability, or delivery speed against the project's goals, and drive changes when results fall short.
Improve the team's technical judgment and delivery. Review designs and code, coach engineers through difficult decisions, and simplify brittle systems and recurring manual work.
Sustained ownership of production software. You've led complex projects, operated what you built, handled failures, and improved the system afterward. You can explain your decisions, the results, and what you'd do differently.
Strong coding and system design skills. You have depth in at least one area and can work across the stack. You can trace behavior through unfamiliar code, reason about data and failure modes, and judge whether an implementation is correct and maintainable.
Product and business judgment. You make reversible product and design decisions independently to keep work moving, and know when to involve product, design, or data partners. You use customer evidence and business results to test your assumptions and adjust your decisions.