Careers @ ClearPoint
We’re different—in a good way.
 

The Senior Software Developer is responsible for building the next generation of the ClearPoint product alongside a small senior engineering team. The job is not to crank out tickets. The job is to deeply understand what we are trying to build for our customers, write the code that makes it real, and care enough to keep making it better.

We are looking for an engineer who treats code as a craft. Someone who reads code carefully, writes it deliberately, and takes the time to make it right. Someone who gets genuinely excited about a clean abstraction, a measurable performance win, or a quietly elegant API. The product is a strategy execution platform used by local governments, healthcare systems, nonprofits, and enterprises—serious people doing serious work—and the software should feel like it was built for them, not bolted together.

This role is focused on the customer-facing experience of the product. The web app is React 19, TypeScript, and Vite. The most important work in the next two quarters is building the surfaces where customers interact with ClearPoint directly: a self-service onboarding flow that gets new customers to first value without hand-holding, an in-product guidance layer that helps customers do the right thing at the right moment, and the AI-driven experiences that put our 25 years of strategy execution methodology into customers' hands. We need someone who can architect those experiences end-to-end, write the React that makes them real, and care enough about how they feel to keep refining them after they ship.

The back end is well-understood and stable, and other engineers own most of that work. You will touch it occasionally—reading CFML/Lucee, extending an endpoint, writing a SQL query against SQL Server—but deep back-end expertise is not a requirement. The willingness to read unfamiliar code without flinching is.
This is also an AI-first role. You will work side-by-side with Claude Code, Cursor, and the next generation of AI engineering tools, and we expect you to use AI as the default lever for any repeatable work. Your time should go to the high-judgment work that actually moves the product forward. The fundamentals matter precisely because they are what make AI tools useful—engineers who deeply understand their stack can direct AI well, review its output critically, and catch the subtle wrong answers. Engineers who do not, cannot.
You will work directly with a Co-Founder and one other senior engineer. There is no layer of process between you and the work.

Responsibilities

• Build new features and product surfaces in our React/TypeScript web app, translating product direction into high-quality, maintainable code.
• Own the customer-facing AI experiences end-to-end—self-service onboarding, in-product guidance, AI-assisted configuration, and the surfaces where customers interact with our methodology layer through AI.
• Architect and build the in-product guidance layer—context-aware help that knows what the customer is doing in the product right now and surfaces the next right action.
• Design and build the React patterns and components that make AI-driven UX feel trustworthy: streaming responses, review-and-edit interactions, error states, escalation paths, and the small details that determine whether customers use the AI or work around it.
• Push the boundaries on front-end performance—bundle size, render cost, paint and layout, memory, time-to-interactive—because real-time AI UX makes performance even more visible than it used to be. Treat performance as a feature.
• Care about what the system does. Notice the small things that make a product feel good or feel cheap, and fix them without being asked.
• Touch the API layer (CFML/Lucee) and database (SQL Server) when product work calls for it. Deep back-end expertise is not required—reading unfamiliar code without flinching is.
• Use Claude Code and other AI tools as the default lever for repeatable work. Continuously raise the floor on what AI handles so your time goes to the work that matters.
• Review code with the goal of making it better, not just making it pass. Coach less experienced engineers when there are any.
• Document significant components and decisions so the next engineer to touch them thanks rather than curses you.
• Contribute to architecture and product discussions. Bring a point of view, not just a willingness to execute.
• Bring a team-first attitude, a can-do spirit, and high standards every day.

• Craft: The code you ship is a pleasure to work in. Other engineers point to it as the example. The next person to touch your work has an easy time understanding what you did and why.
• Customer-Facing AI Quality: The in-product AI experiences feel trustworthy and helpful. Customers choose to use them rather than escalate around them. New customers reach first value through self-service onboarding without needing a CSM call.
• Performance: The web app measurably gets faster on your watch—startup time, time-to-interactive, runtime responsiveness, memory footprint—even as we ship more AI-driven UX.
• Velocity: You ship meaningful work on a regular cadence. PRs stay reviewable. Things finish, often before they are due.
• AI Leverage: You consistently demonstrate that AI is multiplying your output. You ship more, you ship faster, or you ship harder things than would have been possible before.
• Care for the System: The product gets better in the small ways that matter—the rough edges customers would never have filed a ticket about. You see them and you fix them.

• We Care About The Customer: A time you fixed something nobody asked you to fix because you cared about the people on the other end of the software.
• We Play To Win: A time you held yourself or your team accountable for great work—and what you did when the bar was not being met.
• We Are Passionate: A time you got genuinely excited about the work. Bonus if it shows up in a side project, an open source contribution, or a piece of writing.
• We Are Exceptionally Open: A time you flagged a problem early, asked the awkward question, or surfaced something uncomfortable instead of letting it sit.
• We Are Welcoming: A time you helped build an environment where engineers with different backgrounds or experience levels could do their best work.

• A craftsperson. You care how the code looks, reads, and ages. You live for the quiet wins.
• An application architect. You think in component patterns, state flow, and UX systems. You have built complex customer-facing applications and you know what makes them feel good.
• Hungry. You want the work. You want to learn. You want to be good at this.
• Humble. You ask questions, take feedback, and do not pretend to know things you do not.
• Fast. You move quickly, write clearly, and do not need a lot of structure to make progress.
• Comfortable with ambiguity. Priorities shift, processes change, and that is okay.
• Direct. You say what you think, push back when necessary, and do not hide bad news.
• AI-fluent. You already use AI tools in your day-to-day. You have opinions about them.
• A clear communicator. You listen and you can explain technical decisions without jargon.
• Curious. You read. You poke at the edges. You want to understand why, not just what.

• 6+ years of professional software development experience, with the bulk of that time on the front end, required.
• Strong proficiency with TypeScript and modern JavaScript required.
• Strong proficiency with React, including a working understanding of rendering, hooks, and state management, required.
• Demonstrated experience architecting and building substantial customer-facing web applications—not just contributing to features, but owning patterns and surfaces—required.
• Solid understanding of the front-end stack end-to-end—browser fundamentals, rendering pipeline, the module system, and the modern build toolchain—required.
• Demonstrated ability to diagnose and fix front-end performance issues using profiling tools (Chrome DevTools Performance, React Profiler, Lighthouse, or equivalents) required.
• Hands-on experience using AI engineering tools (Claude Code, Cursor, Copilot, custom agents, etc.) in a professional context required.
• Experience building UX patterns for AI-driven or LLM-driven features—streaming, review-and-edit flows, handling uncertainty, error states for hallucinations—preferred.
• Experience with onboarding flows, in-product guidance, or other progressive-disclosure UX patterns preferred.
• Experience with state management at scale (Redux, Zustand, Jotai, or equivalents) and with data-fetching patterns (React Query, SWR, or equivalents) preferred.
• Bachelor's degree in Computer Science, Software Engineering, or four years of relevant technical experience, preferred.
• Evidence of caring about code as a craft—open source work, technical writing, side projects, conference talks, or a clear story about how you have made codebases better—preferred.
• Background in B2B SaaS preferred.

Interested?

Please read this posting carefully, visit our website, learn about us, and then apply. To be considered, please fill out the form and attach your resume. We needed someone yesterday, and we are excited to grow our team, so if you're a good fit, expect this process to move quickly.

Pre-Employment Background Checks

All offers of employment are contingent upon clear results of a thorough background check. Background checks will be conducted on all final candidates and on all employees who are promoted, as deemed necessary and may include: Social Security Verification, Criminal History, Credit History, Personal and Professional References, social media, Prior Employment Verification, Educational Verification, and Motor Vehicle Records. ClearPoint reserves the right to modify this policy at any time without notice.

EEO Statement

ClearPoint Strategy provides equal employment opportunities (EEO) to all employees and applicants without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, age, disability, or genetics. We seek to build a diverse staff representative of the communities we serve. All qualified applicants are strongly encouraged to apply.

Physical Requirements

This is sedentary work requiring typing and other and repetitive motions. Vocal communication is required for expressing or exchanging ideas by means of the spoken word. Hearing is required to perceive information at normal spoken word levels. Visual acuity is required for operation of a computer and for observing general surroundings and activities. The worker is not subject to adverse environmental conditions.