Treating technology as its own specialty has been key to finding exceptional talent for the energy sector. For years, our traditional hiring model prioritized candidates who already knew the energy industry -- candidates who spoke the language, and could plug in quickly. The result was a fairly narrow pool of workers who could hit the ground running. But they often weren't on the cutting edge of technology -- more like several yards back. They understood the established systems, but when it come to building new processes, they were hesitant instead of ambitious. What shifted things was deliberately recruiting technologists from adjacent industries where the problems were just as complex but framed differently, like logistics, aerospace maintenance software, and even large-scale agriculture. Instead of advertising roles through standard energy-sector channels, we partnered with niche technical communities, open-source project forums, and engineering meetups where people were solving reliability, optimization, and safety problems at scale, even if they'd never set foot on a rig or substation. And alongside this shift, we also changed how we assessed candidates. We stopped leading with industry-specific credentials and started evaluating how people thought: how they handled system failure, how they approached data integrity, how they balanced speed with risk in high-consequence environments. We used practical problem-solving discussions instead of resume-driven screening, and we were explicit that industry knowledge could be taught, but systems thinking and engineering judgment could not. The result was a pipeline of technologists who brought fresh perspectives into the energy space, challenged legacy assumptions, and eventually, upended slow and inefficient processes for the better.
When we needed to bring on a new developer at Lock Search Group, our ambitions slightly outpaced our budget. The capabilities we wanted to adopt -- stronger AI functionality, better automation, and a more modern internal stack -- called for a level of technical expertise that was just out of reach. Like many mid-sized firms, we were in an awkward middle ground: sophisticated enough to need advanced tech, but not large enough to justify a full-time top talent hire. So, instead of forcing a traditional hire that would strain resources, we took a different route: fractional hiring. We partnered with two other firms in the recruiting sector and jointly brought on a developer to support all three organizations. It was a genuine leap of faith. Our needs weren't identical, our workflows differed, and we hadn't collaborated at this level before. There was real risk in assuming alignment where it didn't yet exist. The key was recognizing that this wasn't a standard employer/candidate negotiation, but rather, a B2B relationship that required much more upfront clarity. To ensure satisfaction, we spent significant time ironing out expectations, priorities, timelines, and boundaries before any work began. Anyone who's navigated multi-party business agreements knows how delicate that process can be, but for us, doing the hard work early absolutely prevented friction later. In the end, the payoff was enormous. We built development tools we simply couldn't have afforded independently, upgraded our tech stack faster than expected, and gained access to expertise that would have otherwise remained out of reach. And, as a bonus, the collaboration also strengthened our relationships with the other firms, opening the door to future talent sharing and partnership opportunities.
I generally don't like to just say surface level stuff, so let me give you the root cause analysis. Traditional tech recruiting is optimized for the same visible ponds. The same schools, the same titles, the same keywords, and the same networks. If you want exceptional talent, you have to change the signal you are searching for. One creative strategy that worked for me was hiring from builders in public. Instead of starting with resumes, we sourced from small but high quality proof like GitHub repos, technical write ups, and thoughtful answers in developer communities. We would pick a narrow problem we cared about and look for people who had already solved something adjacent, even if their title did not match. I once found an incredible engineer through a blog post about debugging a payroll edge case. That person was not actively job hunting, but they were clearly the kind of thinker we needed. This differed from traditional methods because we did not begin with job boards or years of experience filters. We began with evidence of craftsmanship and curiosity. One practical tip is to write outreach that references the work specifically and invite a short technical conversation, not a generic interview. When people feel seen for their craft, the response rate and quality jumps.
CIO - Strategy, Technology and PMO Delivery at Strategic Project Leader (SPL Global)
Answered 4 months ago
This was an interesting exploration, when our team discovered that the most effective recruitment move did not feel like recruitment at all. We stopped starting with job postings and started with real work. Instead of saying, "We are hiring for this role," we said, "We have a real problem we need to solve. If you are interested, come work on it with us for a short sprint." It was paid. It was time-bound. It was real. That one shift changed everything. People showed up who would never have made it through a traditional hiring process. Self-taught engineers. Career returners. Burned-out consultants who were tired of slides and wanted impact. Even people inside the organization who were not in tech roles but had been quietly building tools, automations, and systems on their own time. On paper, many of them did not look "perfect" but in practice, they were exceptional. What surprised me most was how much easier decisions became. No guessing. No overanalyzing resumes. No trying to read between the lines in interviews. You could see how people thought. How they handled ambiguity. How they asked questions when the problem was not clear. How they balanced speed with quality. How they responded to feedback. Those things never show up on a resume, but they matter more than almost anything else in tech. This was completely different from our traditional approach. Before, we were hiring based on signals. Titles. Tools. Past companies. Certifications. This approach was about value. Could you move something forward in a real environment with real constraints? It also flipped the relationship. Candidates were not trying to impress us. They were deciding if they wanted to work with us. That honesty led to better conversations, faster decisions, and stronger commitment on both sides. The uncomfortable truth is that the best talent is not always scrolling job boards. They are building things. Solving problems. Learning in public or in silence. Waiting for work that actually respects their capability. Once we treated recruitment as a value exchange instead of a filtering exercise, finding exceptional talent stopped feeling hard. It just required us to change where and how we looked.
We began looking for tech talent in unexpected places such as local universities with lesser-known programs. By offering internship opportunities and mentorship we were able to discover hidden gems who might not have applied through traditional hiring methods. This approach helped us find candidates who were passionate about growth and eager to learn. The initiative proved to be a great fit for our culture. It allowed us to build a diverse talent pool while fostering relationships with young professionals. This method not only helped us uncover fresh talent but also contributed to creating a nurturing environment for their development. It highlighted the importance of exploring non-traditional channels to find exceptional talent that aligns with our values and vision.
One of the most successful and unexpected recruitment strategies we used to find exceptional tech talent came not from job boards or referral programs, but from hosting a "Code for a Cause" hackathon—an open, impact-driven event inviting developers, designers, and problem-solvers to build tech solutions for local nonprofits over a weekend. It wasn't positioned as a recruiting event. The traditional hiring methods we used—like posting to tech job sites, working with recruiters, and relying on LinkedIn outreach—gave us access to volume, but not always values alignment. We needed self-motivated, mission-driven builders who thrived in ambiguity and cared about impact as much as output. The hackathon flipped the script. Instead of asking people to prove themselves through a resume, we invited them to co-create, collaborate, and build something real. And we got to observe them doing it—not in an interview chair, but in a live, team-based environment. One standout hire was Tayo, a self-taught developer who had no formal CS degree and had been overlooked by traditional screeners. At the hackathon, he took the lead on integrating an SMS donation system for a youth shelter—and did it in less than 24 hours. But it wasn't just his technical ability that stood out. It was the way he navigated team dynamics, prioritized UX for underserved users, and explained complex logic to non-technical stakeholders. He didn't apply for a job—he just showed up and solved a problem. We offered him a full-time role within two weeks. This approach worked because it removed the artificiality of interviews and replaced it with shared purpose and collaboration. It also attracted talent we wouldn't have found through traditional methods—career switchers, autodidacts, community college grads, and others who are often excluded by rigid filters. A study by Harvard Business School and Accenture backs this up, noting that "hidden workers"—those overlooked by conventional recruiting systems—often bring equal or better performance when given the right entry points. Hackathons, passion projects, and community-led tech spaces are exactly those kinds of entry points. In a market flooded with noise, the most creative recruitment strategy is often to stop asking, "Who applied?" and start asking, "Who's already showing up to solve real problems?" That's where exceptional talent lives—off the beaten path, but right on mission.
We identified talent by observing unanswered questions shared in learning spaces. One participant returned days later with thoughtful solutions that helped others move forward. That patience stood out because it showed responsibility and respect for the community. Traditional hiring often values speed and visible output while this approach focused on follow through and steady effort. We decided to test this mindset by inviting the same person to solve a real internal problem. The task required focus context and accountability similar to the public help offered earlier. The quality of work matched the earlier effort and confirmed the initial signal. It became clear that strong talent often appears in overlooked corners of shared learning when people act with intent.
One creative recruitment strategy that really worked for us was hiring through problem-led discovery instead of job ads. Instead of posting typical roles with long lists of requirements, we put out real, unsolved problems we were working on. For instance, standardizing fee structures across fintech products or building logic to compare FX behavior under different travel scenarios. We shared these challenges in niche developer communities, fintech forums, and on GitHub discussions, and invited people to suggest solutions or approaches. This brought up strong candidates who weren't actively looking for jobs and would never have applied through a regular hiring funnel. Many were engineers, analysts, or product thinkers who liked solving complex problems but were turned off by generic recruitment processes. Their responses gave us immediate insight into how they think, not just what tools they said they knew. This approach was different from traditional hiring in two main ways. First, it focused on the quality of their thinking over CV keywords. Second, it created a two-way evaluation right from the start. Candidates checked if the problem interested them, while we checked how they approached it. The result was fewer interviews, better cultural fit, and hires who were already invested before day one. For tech roles especially, sparking curiosity beats chasing credentials.
A recruitment tactic that paid off for us quite uniquely was to hire people from problem-solving communities rather than job boards. We reached out to open-source contributors, small Discord communities, and technical forums where coders tended to naturally discuss existing challenges, and offered exceptional contributors a trial project before any interview process took place. This differed from traditional hiring because we evaluated candidates on how they think and build, not resumes or titles. The result was higher signal, stronger culture fit, and engineers who ramped faster—because we met them where they already demonstrated passion and skill, not where everyone else was recruiting.
One approach that worked surprisingly well for us was hiring through people who were building, not applying. Instead of posting roles on job boards, we spent time in niche developer communities, open-source GitHub repos, and even long comment threads on technical blogs where people were actively solving problems. We noticed that some of the best engineers weren't job hunting at all, they were just building things in public. We reached out based on the quality of their thinking, not their resume. This was very different from our traditional hiring process, which relied heavily on applications, CV screening, and structured interviews. Also we extensively used skills assessments as a pre-screening method, which worked very well for us.
Among the creative approaches that really paid off was recruiting engineers from open source communities through an assessment of their real work instead of their resumes. This was different from other recruitment approaches because we judged potential employees based on how they worked together and provided solutions to problems in shared codes. This helped us find engineers who were highly qualified and not necessarily job-seeking.
We implemented automated initial resume screening that evaluated candidates on core skills rather than schools or job titles. This reduced unconscious bias and gave fair consideration to underrepresented applicants and those from non-traditional paths. It also sped up our interview process so we could assess many more candidates. As a result, we saw a 35% increase in hires from non-traditional career paths and added fresh perspectives to the team. Compared with our previous background-focused process, this skills-first approach revealed exceptional talent we had been overlooking.
We shifted from traditional full-time recruiting to building a network of part-time, highly skilled specialists who preferred flexible engagements. This differed from our earlier approach of hiring generalists too early and asking them to cover multiple functions. To ensure consistency, we used a structured two-week onboarding and custom playbooks so specialists could ramp quickly. Each specialist was matched with an in-house point person and we emphasized knowledge-sharing across the team. This model helped us lift a client's SaaS trial funnel conversion from 3.1% to 4.4% in 30 days and complete a B2B website migration with no ranking dropoffs.
Honestly, I always had my doubts regarding the effectiveness of the traditional advertisement-CV-interview cycle in bringing the best candidates to me. The technique that worked for me in a way was to frame a real-world problem scenario and ask, is there someone who would like to take a shot at this? At times, this was a small open-source issue, and at times, a mini-technical challenge made available to the public. I didn't even take a glance at the CV, the education, or the title; all that I was interested in was the way they reasoned. This tactic stood in stark contrast to the traditional way of hiring since the candidates did not simply throw their resumes at me; they actually volunteered. What is more, some weren't even actively seeking a job. But their resolution to the issue, the few lines of code that they wrote, or the questions they posed, signaled more than I could have ever got from a lengthy discussion in interviews. This enabled us to take advantage of the situation and found some earlier seemingly unfit yet truly strong candidates in the Programmer. — Eylem Culculoglu, Founder of Textara.ai
The best engineers we found weren't even job hunting. We built a series of open coding challenges tied to real issues from our product roadmap, then shared them quietly in developer communities. Within weeks, we saw submissions from people who had never applied for a role in their lives. Some were self-taught, some from non-tech backgrounds, all with sharp instincts and curiosity that didn't show on a resume. We hired three of them. The process worked because it replaced outreach with discovery. Instead of asking who was available, we learned who could think through problems the way our team does.
One creative recruitment strategy that worked surprisingly well for me was hiring through problem-solving, not resumes. Instead of posting traditional job descriptions on the usual platforms, we designed a real-world challenge based on an actual problem our team was facing and shared it in developer communities where people were already learning, building, and helping each other. The challenge was open, unpaid, and framed as a learning opportunity, not a hiring test. What stood out immediately was the range of candidates it attracted. We heard from self-taught developers, career switchers, and contributors from open-source forums who would never have applied through a standard hiring funnel. Because the task mirrored real work, we could see how people thought, communicated, and handled ambiguity. That told us far more than a polished resume ever could. This approach differed from our traditional methods in two major ways. First, it shifted the focus from credentials to capability. Instead of filtering by years of experience or specific titles, we evaluated curiosity, problem framing, and trade-off thinking. Second, it made the process feel mutual. Candidates were assessing us at the same time, getting a sense of our culture and expectations before any formal interview. The result was a smaller but stronger candidate pool and hires who ramped up faster because they already understood how we worked. Most importantly, it expanded our definition of where great talent comes from, which has influenced how I think about hiring ever since.
One creative recruitment strategy that worked for us was sourcing engineers from technical problem spaces instead of job boards. While building automation at WhatAreTheBest.com, we identified developers actively contributing to open-source scraping tools and data pipelines we relied on. These weren't candidates applying for jobs, but builders already solving the same problems we faced. We reached out with real system challenges rather than resumes or titles. That differed from traditional hiring, which filtered candidates by roles and years of experience. This approach surfaced pragmatic engineers who shipped fast and needed little onboarding. GitHub research shows developers who contribute to open source demonstrate higher problem-solving autonomy. Hiring from execution signals instead of credentials consistently produced stronger technical leaders for us. Albert Richer, Founder, WhatAreTheBest.com.
We invited tech candidates to solve a real internal problem rather than submit resumes. This surfaced talent who thought clearly under real constraints. It differed from traditional hiring by prioritizing problem solving over credentials.
Engaging the public in virtual hackathons and coding challenges was one of the more imaginative recruitment strategies employed. This was not a traditional hiring approach; it focused on skills and immediate problem-solving within a defined timeframe, rather than relying solely on resumes, referrals, or other conventional methods. Candidates who showcased their skills during the coding challenges were fast-tracked to the interview stage, allowing the company to access candidates we might otherwise have overlooked through traditional job ads. It worked because it reinforced the necessity of these skills, support, creativity, and interpersonal cooperation, all within a highly pressurized environment. Ultimately, we were able to find out extraordinary skills that would otherwise remain hidden.
One of our best hires came from partnering with a local coding bootcamp to create a "logistics tech challenge" where students built solutions to real fulfillment problems we were facing at Fulfill.com. We discovered incredible talent that traditional job postings would have completely missed. Here's what made this different: Instead of filtering resumes by years of experience or specific tech stacks, we presented actual operational challenges from our 3PL marketplace. One challenge involved optimizing warehouse routing algorithms when inventory is distributed across multiple facilities. Another focused on predicting shipping delays based on carrier performance data. Students had two weeks to build working prototypes, and we offered mentorship throughout. What surprised me most was that the winners weren't always the most technically polished developers. They were the ones who asked the smartest questions about how fulfillment actually works. One candidate, who became our senior logistics engineer, had zero supply chain experience but spent hours interviewing warehouse managers to understand their pain points before writing a single line of code. That curiosity and user-focused thinking is incredibly rare. Traditional tech hiring in logistics tends to prioritize candidates who already know our industry, which severely limits the talent pool. The problem is that logistics technology is evolving so rapidly that yesterday's experience isn't always relevant to tomorrow's challenges. We needed people who could learn quickly and think creatively about problems that don't have established solutions yet. This approach also changed our interview process permanently. Now, every technical candidate works on a mini-project based on real Fulfill.com challenges, regardless of their background. We've hired former teachers, retail workers, and even a professional musician through this method. What they all share is problem-solving ability and genuine interest in making supply chains work better. The bootcamp partnership cost us maybe 20 hours of engineering time and yielded three exceptional hires in our first year. Compare that to the six months we spent trying to fill the same roles through LinkedIn and recruiters. More importantly, these hires stayed longer because they were genuinely excited about the problems we're solving, not just collecting a paycheck. If you're struggling to find tech talent, stop competing for the same candidates everyone else wants.