CINQCARE’s Post

Principal Engineer Staff Engineer Distinguished Engineer (my favourite) I’m going to say it and it’s likely a little rhetorical: I dislike all these terms immensely. Please can someone give me the canonical description for what they are supposed to mean? (I know I can use a search engine or AI to do it… I want to know what people think they mean). The industry I work in is in danger of disappearing up its own backside. What’s wrong with: Software engineer Why do we need to differentiate? The only reason I can see is signposting to people with differing levels of experience or different sets of responsibilities. If we need to do that then, I’m not sure our teams are set up correctly in the first place. #software #softwareengineering #softwaredevelopment #productdevelopment

We are now #hiring into our new Advanced Client Solutions department, with a range of newly created full-time job roles available for those working in Legal Project Management, Product Development, Legal Technology, or with paralegals. Find out more about the new team and how it forms a vital part of our broader innovation strategy here: https://ow.ly/joHg50RbNq1 The job descriptions for each role are now available on our 'Careers' section, under ‘Current roles’. #KnowingWhatMatters #PrivateCapital #LegalInnovation

In software engineering, it's much more than just writing code; it's the art of turning ideas into reality, of creating solutions that positively impact people's lives. With every line of code we write, we're shaping the future, molding the world around us. It's the opportunity to tackle complex challenges, solve intriguing problems, and collaborate with a diverse and talented team. In software engineering, we're driven by the relentless pursuit of knowledge, by innovation, and by a passion for creating something meaningful. Every bug fixed, every new feature implemented brings us closer to our ultimate goal. It's this sense of progress, of constantly learning and evolving, that motivates us to get up every morning and face the challenges that await us. Ultimately, in software engineering, we find not just a career but a calling, an opportunity to make a difference and leave a lasting legacy in the world of technology.#technology #software #engineering #solutions

If you’re applying for a job there’s generally multiple qualifications in a bulleted format. For example if there’s four qualifications, and one of them requires a license or certification that’s generally not the one where the “transferable skills” rule applies. Look for the people management, administrative experience, or things like that. Move on to the one that says must have “great people skills” or “excellent written and verbal communication required” since those are subjective. Software engineering is not transferable to a job as a CT tech, just as a CT Tech can’t write lines of code.

As tech becomes even more important for law firms to remain competitive in the market, we've noticed a trend that there are simply not enough candidates with experience for the #legaltech roles that are available. For large law firms, this means either competing over a relatively small pool of talent, or hiring for potential and training them up. As a software business with ambitious goals, building a high perforning tech team is one of the most important things we do, and we like to think we are pretty good at it now. Our CTO Tony Johnson firmly believes that hiring for attitude is equally as important as skill & knowledge when looking to build a high performing culture. Check out the following blog post from Tony for more insights: https://lnkd.in/eU6nPhcP

This is consistent with how I’ve coached my teams to think on this and set expectations for different levels

It's the vision you fall in love with and the clarity with which PSK Varma puts it is absolutely intriguing. These opportunities are truly transformative. Please give it a thought if it matches your desires. Feel free to DM, if you need more clarity. TECHSOPHY #hiring #techopenings #Java

Handling ambiguity well is a key component to advancing as a software engineer. How do you quantify "ambiguity" without being hand-wavy? Here's a framework for how to think about ambiguity at each engineering level (see attached screenshot): 1. Junior (IC3) - No ambiguity. We know exactly what we need to do, project just needs to be completed. 2. Mid-level (IC4) - Feature-level ambiguity. We know the solution but don't know the details of how to implement it yet. 3. Senior (IC5) - Roadmap-level ambiguity. We know what problem to solve and why, but we don't know what to do to solve it yet. 4. Staff (IC6) - Strategy-level ambiguity. We don't even know what problems we should tackle. IC6s create scope. If you have another way of thinking about engineering ambiguity I'd love to hear it. How do you quantify ambiguity?

Rust Engineer will be very important. you want performant systems, that takes loads