<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Fulton Software Group Blog</title><link>https://blog.fultonsoftwaregroup.com/</link><description>Recent content in Home on Fulton Software Group Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</managingEditor><webMaster>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</webMaster><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.fultonsoftwaregroup.com/index.xml" rel="self" type="application/rss+xml"/><item><title>A Study of a Real QuickSort: What LeetCode Interviews Actually Ask You to Reinvent</title><link>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-leet-code-a-study-of-real-quicksort/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><author>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</author><guid>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-leet-code-a-study-of-real-quicksort/</guid><description>When a LeetCode interviewer asks you to &amp;lsquo;implement quicksort,&amp;rsquo; you are being asked to produce a toy. The production sorting implementation that ships with the JVM is a 4,430-line adaptive system containing seven distinct algorithms, twelve empirically derived thresholds, IEEE 754 compliance, and parallel execution support — authored over fifteen years by four engineers whose combined contributions define modern Java. This page examines that implementation, in detail, and asks a simple question: why are we testing for this?</description></item><item><title>Cited Works: Behavioral Interviews</title><link>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-cited-works-behavioral/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><author>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</author><guid>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-cited-works-behavioral/</guid><description>Over 90% of candidates engage in faking behavior during behavioral interviews. Self-presentation tactics inflate ratings without predicting job performance. Interview ratings correlate twice as strongly with impression management as with job-related competence. The STAR method, now universally taught, has made the format so transparent that it grades preparation skill, not work ability. Four decades of research converge on a single finding: behavioral interviews measure the wrong thing, and they measure it reliably.</description></item><item><title>Cited Works: Unstructured Interviews</title><link>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-cited-works-unstructured/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><author>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</author><guid>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes-cited-works-unstructured/</guid><description>Decades of peer-reviewed research — including work by a Nobel laureate — converge on a single finding: traditional unstructured interviews are foundationally flawed as a method of evaluating candidates, frequently performing worse than random selection from a qualified pool.</description></item><item><title>Disturbingly Flawed Interview Processes — A Cri de Coeur</title><link>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><author>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</author><guid>https://blog.fultonsoftwaregroup.com/posts/2026/02/interview-processes/</guid><description>The research is not ambiguous. Unstructured interviews perform worse than random selection. Behavioral interviews measure impression management, not competence. LeetCode exercises test rote memorization in a context disconnected from the work. The methods that would work are known — and have been for decades. The industry has chosen not to adopt them. This post examines why.</description></item><item><title>About</title><link>https://blog.fultonsoftwaregroup.com/about/</link><pubDate>Fri, 16 Jan 2026 00:11:20 +0000</pubDate><author>contact+blog@fultonengineeringservices.com (J. Patrick Fulton)</author><guid>https://blog.fultonsoftwaregroup.com/about/</guid><description>&lt;p&gt;Authored by J. Patrick Fulton, focusing on software engineering, cloud architecture, and technical leadership topics.&lt;/p&gt;
&lt;p&gt;I write as a career software engineer and technology leader who has spent more than two decades building and scaling SaaS
products—most recently as a Chief Technology Officer in the healthcare technology vertical. I&amp;rsquo;ve led engineering, quality assurance, and DevOps organizations
through high-growth phases, guided architectural overhauls into cloud-native platforms, and worked the intersection of
product strategy, technical design, and real-world delivery.&lt;/p&gt;</description></item></channel></rss>