alignment, and team connection. Join us at 84.51°! __________________________________________________________ Senior Software Engineer, AI Agents Summary As a Senior Software Engineer on our AI agent team, you will desig…
Software Engineer jobs in Cincinnati, OH
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open software engineer roles
9 shown of 373 · sorted by freshness
Job Description Job Description Job Location: Cincinnati, OH Position Overview: This position is to lead a team of software engineers implementing cloud based, full-stack software applications that incorporate advanced a…
Stack developer is a member of an agile squad, responsible for implementing new features and enabling capabilities using modern software engineering tools and practices. Adheres to practices and standards, set by communi…
Description: On-site in Cincinnati, OH Our client is seeking a software engineer to join the Serviced Modernization Squad to help modernize a legacy customer servicing platform. The role focuses on Java and backend servi…
We are searching for the best talent for a Principal Platform Engineer Sales professional to be located in Raritan NJ J&J sites on the... ...adoption. Required Qualifications ~7 years of software engineering experience d…
reliability and scalability. The ideal candidate has strong experience with .NET C# SQL Server application architecture and the full software development lifecycle. Responsibilities Develop test and maintain .NET/C# appl…
Job Description Summary The Software Lead Engineer is the technical lead for embedded engine control software. You'll own the design of highly complex modules, critical components, or a whole software product, and integr…
Job Description Business Overview GE Aerospace's Defense Engines & Services organization is the provider of choice for combat and... ...military engines). On my team, we think it's the logic and software that stitch all…
Job Summary: We are looking for a full-stack engineer with strong React, Node.js, and SQL experience to join a forward-deployed team delivering a new AI product to enterprise clients. You will connect client data systems…
What software engineers earn in Cincinnati
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$47 | $70k–$98k |
| Mid level | $47–$67 | $98k–$140k |
| Senior | $65–$89 | $135k–$186k |
Adjusted for the Cincinnati market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer jobs in Cincinnati?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.