Meet Amelia, a software engineer who works in our #Manchester offices. She combines her training and passion for our mission with a creativity for tackling the toughest of problems on a daily basis. Although she can't tell you any more about herself, she's kindly given a glimpse into what her work in engineering looks like ⬇️
GCHQ’s Post
More Relevant Posts
-
Really good take on writing accurate job descriptions to ensure that a higher percentage of those who apply will be right. Top tips 👌🏾
As part of a continued drive to clarity and transparency in job descriptions, Abhik Pramanik (Ashby Co-Founder & VP of Engineering) and I have worked in a "Why you shouldn't apply" section to a new role we posted yesterday. It's for an Engineering Director - the bullets are here and the full job description, linked below, will give more context to these. Let me know what you think recruiters and hiring managers! Would you try this? Interested in the outcomes? "Put another way; you shouldn’t apply if: You don’t enjoy coding or don’t find time to stay up-to-date on technology. You want to make all the product decisions instead of empowering your team to make those calls. You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done. A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews. You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications)." Follow Ashby here for more release updates and well crafted talent content: https://lnkd.in/gDtuNspH The job is here
To view or add a comment, sign in
-
As part of a continued drive to clarity and transparency in job descriptions, Abhik Pramanik (Ashby Co-Founder & VP of Engineering) and I have worked in a "Why you shouldn't apply" section to a new role we posted yesterday. It's for an Engineering Director - the bullets are here and the full job description, linked below, will give more context to these. Let me know what you think recruiters and hiring managers! Would you try this? Interested in the outcomes? "Put another way; you shouldn’t apply if: You don’t enjoy coding or don’t find time to stay up-to-date on technology. You want to make all the product decisions instead of empowering your team to make those calls. You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done. A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews. You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications)." Follow Ashby here for more release updates and well crafted talent content: https://lnkd.in/gDtuNspH The job is here
Careers | Ashby
ashbyhq.com
To view or add a comment, sign in
-
In a busy city, there was a cool company known for its great ideas and fun work environment. Sarah was in charge of finding awesome people to join their team. One project needed smart engineers, so Sarah picked Emily, who was super smart and great at solving problems. But just before Emily could start, she said she couldn't because of personal stuff. Sarah was sad but didn't give up. She found Adam, who was also really good but wasn't picked before. Even though it was a last-minute thing, Adam said yes. Together, they worked hard and did an amazing job on the project. Afterward, Sarah realized that even though things didn't go as planned, it turned out great. She learned that sometimes unexpected changes can lead to good things. And thanks to people like Adam, the company kept growing and doing well. #AdaptabilityWins #UnexpectedOpportunities #ResilienceInRecruitment #TeamworkTriumphs #TalentDiscovery #EmbracingChange #OvercomingObstacles #SuccessThroughSetbacks #TurningChallengesIntoOpportunities #GrowthMindset #recruiter
To view or add a comment, sign in
-
Software Engineer @Monzo Bank | Prev: Bloomberg, and Amazon | I help you fast-track your tech career growth 📈
3 Things to Do When Things Are Unstable In Your Team Changes happen, people come and people go in any software engineering team. Here's what to do to cope with the changes. 1. Stay stable in the middle of instability Work with what you have and strive to stay as connected as possible with your team's work, and what everyone is doing. 2. Be human, listen to others It's a way of showing we're human. We're not just machines working together; we're people collaborating. 3. Be precise, direct, and detailed If you have a new manager on the team, it's important to keep them updated on your plan. Read more in this week's short publication: https://lnkd.in/eUgGxSNV #softwareengineering #softwaredevelopment
3 Things to Do When Things Are Unstable In Your Team
basmataha199.substack.com
To view or add a comment, sign in
-
The type of posts I want to see on LinkedIn
🎉 Exciting Milestone: Reached Town Hall 13 in Clash of Clans! 🏰 Today, I'm thrilled to share that I've reached Town Hall 13 in Clash of Clans, and believe it or not, this journey has taught me invaluable lessons about being an engineer. Here are some insights that directly translate to my professional growth: Strategic Planning: Just like in software development, advancing in Clash of Clans requires meticulous planning and strategic thinking. Prioritizing upgrades, managing resources, and anticipating challenges mirror the project management skills needed in engineering. Continuous Improvement: Reaching higher levels demands constant learning and improvement. This resonates with the iterative nature of software engineering, where continuous integration, testing, and deployment are key to delivering robust solutions. Team Collaboration: Success in the game is often driven by the strength of your clan. Similarly, in software engineering, collaboration and teamwork are crucial. Sharing knowledge, supporting peers, and leveraging collective strengths lead to outstanding outcomes. Adaptability: In both Clash of Clans and software development, the landscape is ever-changing. Being adaptable and quick to pivot when facing new challenges is a vital trait. It fosters innovation and resilience in dynamic environments. Problem-Solving: Every raid and defense in Clash of Clans involves critical problem-solving skills. In software engineering, debugging and optimizing code require a similar analytical approach to overcome obstacles and achieve success. Reaching Town Hall 13 is more than just a gaming achievement; it symbolizes growth, perseverance, and the continuous pursuit of excellence. I’m excited to bring these insights into my professional journey as an engineer and to continue pushing the boundaries of what’s possible. Let's keep leveling up, both in games and in our careers! 💪🚀 #SoftwareEngineering #StrategicPlanning #ContinuousImprovement #TeamCollaboration #Adaptability #ProblemSolving #CareerGrowth #Tech #ClashOfClans #GamingToGrowth
To view or add a comment, sign in
-
-
“Your job title says "software engineer", but you seem to spend most of your time in meetings. You'd like to have time to code, but nobody else is onboarding the junior engineers, updating the roadmap, talking to the users, noticing the things that got dropped, asking questions on design documents, and making sure that everyone's going roughly in the same direction. If you stop doing those things, the team won't be as successful. But now someone's suggesting that you might be happier in a less technical role. If this describes you, congratulations: you're the glue. If it's not, have you thought about who is filling this role on your team? Every senior person in an organisation should be aware of the less glamorous - and often less-promotable - work that needs to happen to make a team successful. Managed deliberately, glue work demonstrates and builds strong technical leadership skills. Left unconscious, it can be career limiting. It can push people into less technical roles and even out of the industry.” https://noidea.dog/glue
Being Glue — No Idea Blog
noidea.dog
To view or add a comment, sign in
-
Software architect | Microsoft MVP | Author of Ode To Software Architecture book | Founder of Evolutionary Architecture by Example Repository
As a software engineer, I am guided by five basic principles: ➡ First, make it work, then make it right ➡ Prioritize simplicity and clarity over complexity ➡ Base architectural decisions on current needs rather than wishful thinking ➡ Foster a culture of collaboration where everyone has their voice, no matter their experience ➡ Be the kind of person you would want to work with These principles are my roadmap. What are yours? 🙂
To view or add a comment, sign in
-
🎉 Exciting Milestone: Reached Town Hall 13 in Clash of Clans! 🏰 Today, I'm thrilled to share that I've reached Town Hall 13 in Clash of Clans, and believe it or not, this journey has taught me invaluable lessons about being an engineer. Here are some insights that directly translate to my professional growth: Strategic Planning: Just like in software development, advancing in Clash of Clans requires meticulous planning and strategic thinking. Prioritizing upgrades, managing resources, and anticipating challenges mirror the project management skills needed in engineering. Continuous Improvement: Reaching higher levels demands constant learning and improvement. This resonates with the iterative nature of software engineering, where continuous integration, testing, and deployment are key to delivering robust solutions. Team Collaboration: Success in the game is often driven by the strength of your clan. Similarly, in software engineering, collaboration and teamwork are crucial. Sharing knowledge, supporting peers, and leveraging collective strengths lead to outstanding outcomes. Adaptability: In both Clash of Clans and software development, the landscape is ever-changing. Being adaptable and quick to pivot when facing new challenges is a vital trait. It fosters innovation and resilience in dynamic environments. Problem-Solving: Every raid and defense in Clash of Clans involves critical problem-solving skills. In software engineering, debugging and optimizing code require a similar analytical approach to overcome obstacles and achieve success. Reaching Town Hall 13 is more than just a gaming achievement; it symbolizes growth, perseverance, and the continuous pursuit of excellence. I’m excited to bring these insights into my professional journey as an engineer and to continue pushing the boundaries of what’s possible. Let's keep leveling up, both in games and in our careers! 💪🚀 #SoftwareEngineering #StrategicPlanning #ContinuousImprovement #TeamCollaboration #Adaptability #ProblemSolving #CareerGrowth #Tech #ClashOfClans #GamingToGrowth
To view or add a comment, sign in
-
-
Best line I read all week from Tanya Reilly's post on glue work -- "You know that thing where everyone on a software engineering team turns up and just writes code for eight hours a day and then later the project is successful? No you don't. Projects don’t work like that!". Great insights in there, especially for Staff+ and junior engineers: "doing glue work too early can be career limiting, or even push people out of the industry.". Read more here:
Being Glue — No Idea Blog
noidea.dog
To view or add a comment, sign in
-
Staff SWE at HubSpot • Helping Techies become Leaders in their Software Careers & Balanced Beings at Life • Author at Curious Soul’s Corner Newsletter - subscribe now!
"She's too new to Software Engineering....not quite a fit" "He hasn't committed enough code this quarter." "When I was at his experience level, I was promoted to Senior... " "She's at the stage of her life where she's going to focus on her kids and not coding." "He's going to retire in a few years." "Her peak performance time is history now." If you ever hear these things at your current or future workplace... STOP...and pivot immediately. These comments and observations SHOULD NOT belong in the decision-making process. Ever. Judge Engineers by what they bring to the table. Not by their current circumstances. Agree? ---- Follow Gourav Khanijoe for daily Engineering Insights! (𝙿𝚑𝚘𝚝𝚘 𝚋𝚢 𝚃𝚒𝚖 𝙶𝚘𝚞𝚠 𝚘𝚗 𝚄𝚗𝚜𝚙𝚕𝚊𝚜𝚑)
To view or add a comment, sign in
-