Connor Jones / Software Engineer

Complex problems.
Thoughtful interfaces.

I build web applications with React and TypeScript, combining practical engineering with a close eye for design.

Selected work

01 / Selected work

Built with purpose.

Enterprise applications, early-stage products,
and ideas brought to life.

A little more of the visual side.

Selected client websites and application work

02 / Experience

Craft, backed by practice.

Download resume (PDF)

Titan Cloud Software

May 2024 – Oct 2026

Software Engineer

Complex enterprise interfaces, reusable components, data visualization, API integration, and cross-stack troubleshooting.

Bluewell

Sep 2021 – Feb 2023

Lead Front-End Developer

Front-end architecture and UI/UX design for a legal-referral platform, collaborating with a small engineering team to deliver the MVP.

Independent

Mar 2018 – Jan 2022

Freelance Front-End Developer

Client websites and applications, from requirements and wireframes through development and deployment.

Automatit

Sep 2017 – Feb 2018

Junior Front-End Developer

Implemented websites from design mockups in collaboration with front-end and back-end teams.

What I bring

Interface architecture

React, TypeScript, reusable components, responsive CSS, and design translated into working interfaces.

Data-heavy applications

Complex grids, filtering, selection, visualization, and thoughtful loading and request handling.

Work across the stack

REST APIs, C# / ASP.NET, SQL Server, and collaboration that connects product needs with implementation.

03 / A bit about me

An engineer with
an eye for design.

Based in Tucson, Arizona

I’m Connor, a software engineer whose work spans enterprise web applications, freelance delivery, and independent products.

My background in design shapes how I build: I care about how an interface looks, how it behaves, and whether it helps someone get their work done.

I enjoy working through the details with designers, product teams, and other engineers, especially when the solution crosses more than one part of the stack.

04 / Get in touch

Let’s build something
worth using.

Have an engineering role in mind? I’d like to hear about it.

Selected work / 01

Titan Cloud Software

Making complex reporting work for people.

Application engineering shaped by collaboration across product, data, and development teams.

My role
Software Engineer
Focus
Feature ownership · Cross-team delivery

The challenge

A reporting workflow was retrieving more data than the application could handle comfortably. Loading was slow, requests were unreliable, and users could not consistently access the information they needed. I headed the feature work, connecting application development with the product and data teams.

Delivering an interim solution

I implemented paging in the front end and application services to make the workflow usable while we investigated further. The underlying queries could not efficiently provide total counts or support repeated sorting and filtering requests. We shipped sequential page navigation with those interactions temporarily restricted, making the tradeoffs explicit with the team.

Reframing the problem together

Paging reduced what each request returned, but did not resolve the cost of preparing the data. Working with product management and data engineers, we revisited report-selection criteria and identified unnecessary data. The data team refined that selection while we worked toward a better delivery approach.

A more sustainable approach

I proposed preparing datasets outside the interactive request path, so opening the report would not require repeating the expensive preparation work. The application retrieved prepared datasets, refreshed in response to relevant events, and transformed them into the data displayed by the grid.

Ownership across team boundaries

I implemented the application endpoints and front-end integration and coordinated feature delivery. The data team owned dataset generation and background processing. Keeping those responsibilities connected helped us move from an urgent workaround to a complete application experience.

The outcome

The final workflow restored paging, sorting, and filtering. The work combined hands-on engineering with cross-team problem solving: addressing the immediate usability issue, questioning the original constraints, and following the feature through to a more sustainable solution.

Client identities, internal visuals, and implementation specifics are omitted to respect confidentiality.

Back to work
Selected work / 02

Bluewell / 2021–2023

A professional network, built from the ground up.

A legal-referral platform combining professional networks, direct messaging, and referral workflows.

My role
Front-end lead · UI/UX designer
Team
Front-end, design, and back-end collaborators
Archived Bluewell dashboard showing network navigation and onboarding
Archived product interface. Some screens include placeholder content from development.

The problem

Lawyers needed a way to connect with peers and refer work outside their specialization. A small team had to bring the product’s workflows, messaging, and visual design together in an MVP.

What I owned

I led the front-end team, designed the UI and UX, and architected the front-end application. I worked closely with the back-end lead and engineers to define how the interface and services fit together, with some additional CRUD work on the back end.

The approach

We structured data delivery around the interface’s needs, used lazy loading to defer work, and applied component and data memoization where appropriate. Responsive layouts and clear interaction patterns supported the networking and referral workflows.

Bluewell network interface with its navigation drawer
Network navigation and application UI.

The outcome

We brought the MVP to market and refined the experience using usability feedback and user data. The project gave me end-to-end ownership of front-end architecture and product design within a collaborative engineering team.

Back to work
Selected work / 03

Strength and Keto / Independent product

A plan shaped around personal preferences.

A working meal-planning product that connected food preferences with recipes, a calendar, shopping lists, and calorie planning.

My role
Primary application developer · Product designer
Front-end stack
HTML · SCSS · jQuery
Food-selection step in the Strength and Keto preference wizard
A guided step for selecting preferred foods.

The problem

Planning meals around food preferences and nutrition targets creates a lot of decisions. We wanted to turn those inputs into a practical plan people could use throughout the week.

What I built

I built the large majority of the application, including its guided preference wizard and meal-planning experience. The working product generated recipes, arranged a calendar, produced shopping lists, tracked calories, and estimated deficits from activity and body metrics.

A shared effort

My brother owned the database work, OAuth authentication, and payment processing. Together, we brought the planned core features into a working product.

The outcome

The product worked, but our limited marketing efforts did not attract enough customers to sustain it. Expansion into other diet types remained planned. It remains a valuable example of independent product design and hands-on implementation.

Back to work
Additional work

Scalefirm / Client website

A clear introduction to a legal practice.

Freelance website design and development for Scalefirm.

My role and approach

Worked on the site’s design and implementation, organizing the firm’s services, people, and client information into a cohesive web experience.

The result

The archived work shows the home, practice, attorney, and client pages. These images document the delivered design rather than the current state of a live website.

Archived Scalefirm homepage design
The archived homepage.
Back to work
Additional work

RollWorks / Client website

Building on an established web presence.

Website design and development in collaboration with RollWorks’ engineering and product teams.

My contribution

I was contracted to add new pages and refine existing parts of the website. The work combined UI design, development, and performance and conversion optimization audits.

Working within an existing product

The project involved collaborating with the client’s teams on changes to an established site, rather than building an isolated concept.

The result

These archived screens show the website work from that engagement. They document the past implementation rather than the current live site.

Archived RollWorks homepage with product, customer, and marketing sections
Archived website interface.
Back to work
Additional work

HiMS / Axiom mobile application

Dense information. A smaller screen.

Front-end design and development for a mobile application from Health Information Management Systems.

The challenge

The application needed to present a substantial amount of information on a small screen while supporting data entry and detailed views.

My contribution

I designed and developed the front-end experience. The approach used compact tables, swipe navigation, row indicators, and expandable rows to make more information available within the mobile layout.

The result

The archived interface shows how navigation, dense information, and input controls were organized for mobile use. It adds another example of my work on data-heavy application interfaces.

Archived Axiom mobile interface with compact information sections and expandable forms
Archived mobile application interface.
Back to work