Software Engineer III

FanThreeSixty•Leawood, KS

15d

About The Position

Software Engineer III is the technical backbone of a product area — the person who can take an ambiguous problem, from a bug fix to a multi-sprint feature, and own it end-to-end without needing to be told how to break it down.

Requirements

5–8 years of software development/engineering experience.
Bachelor's degree or equivalent certification in Computer Science, Information Systems, or Software Engineering (or equivalent experience).
Strong grasp of system design, data structures, and modern development practices.
Hands-on with Java, Python, React, or similar; comfortable with Playwright, Vitest, JUnit, VSCode/IntelliJ.
Experience building and consuming REST and SOAP APIs (sync and async), including caching and fault tolerance.
Comfortable designing relational schemas and working with NoSQL data stores.
Solid understanding of microservices architecture and inter-service communication patterns.
Fluent in Git-based workflows and tools like Jira.
Track record of independently scoping, estimating, and communicating project timelines.
Experience mentoring or coaching other engineers.
Familiarity with observability tooling — logging, metrics, tracing, and alerting (e.g., Datadog-class platforms) — as baseline competency, not just testing.
Secure coding practices and data-privacy awareness (OWASP-level fluency), given F360 handles fan/customer data.
Named fluency in CI/CD pipeline design and cloud-native practices (containers, infrastructure-as-code) — beyond just using a pipeline someone else built.
Comfortable using AI-assisted development tools (e.g., Cursor, Claude, Gemini) as part of the daily workflow — not just aware they exist.

Responsibilities

Own delivery for a significant slice of F360's product surface: bugs, enhancements, and net-new features alike.
Take on large, ambiguous problems and structure them into a plan others can execute against.
Design, build, and maintain code and data across the F360 stack, with working knowledge of how products, workflows, and edge cases connect across systems.
Turn product requirements into technical specs: partner with product owners on requirements, research, and proofs of concept.
Plan and run projects — set milestones, delegate work, and manage the resources needed to hit them.
Write tests and documentation for every change, and call out gaps in coverage before they become production issues.
Review peers' code and participate in architecture/design discussions with real influence over outcomes.
Diagnose and resolve complex bugs, fixing the root cause rather than just the symptom.
Mentor and unblock less senior engineers as part of daily work, not as a side project.
Own features through production — participate in on-call rotation and take responsibility for incident response on services this role owns.
Identify where technical debt or architecture choices are limiting team velocity, and make the case for addressing it — not just execute assigned work.