I discounted investigating NUMA as early on they told me they had their applications pinned to nodes, and I would have otherwise investigated that more quickly and probably solved the issue in less time. How 8 Software Engineers Solved Their Biggest Technical Challenges. But yeah... my main point was to say that moving a company from "old broken" to "new shiney fixed" while keeping everything working, adding new features, etc is, at the heart, the largest technical challenge I've faced. We created entity relationship diagrams to better illustrate ideas and uncover potential issues — these were paired with potential designs where we discussed the UI/UX process and how it related.
Every developer dreams of going greenfield. But it's sometimes exhausting to investigate stuff like that, plus most of the reasonable managers will try to prevent you from going down the rabbit hole if the bug takes too long to fix. They want to know a bit more about you. So my question to you, HNers, is: What is the hardest technical problem YOU have run into? If you want to know about business gains and side effects of technical work, ask "How did your work help your employer? " Just the metadata was using about 5gb of memory. What made this particular challenge so tricky? While I understand and don't disagree with what you say - a full rewrite is normally not the answer - you haven't seen this codebase. What is the hardest technical problem you've solved in spanish. And while that might seem overwhelmingly obvious, the four also reflected on what they learned from their challenges — the biggest highlight of the problem-solving process. I believe my full-stack engineering abilities and diverse experience in the industry would help me succeed in improving XYZ Co's products and services. The best approach to answering this question: Focus on a problem you have already effectively resolved. By asking this question, the interviewers are trying to gauge what "challenging" means to you and how well you're able to problem-solve and handle stressful situations.
"In search of a solution, I resorted to the instincts carried by any child with a LEGO set: I did some serious playing and tinkering around, " said Hubert Shon, a full stack engineer at KPI Sense. Sometimes unexpected scenarios are unavoidable, so being able to recover from failure and shorten the down time becomes the best mitigation to combat the unexpected. I realize this is a potential place for me to show growth, but I would ultimately first have to admit that I initially fell flat on my face.
Susan: Thanks for sharing! 10 Challenges Every Software Product Developer Faces. A process as complex as software product development comes with its own set of challenges – challenges that you might encounter every day. The problem is niche so no stackoverflow or blog post to help me either. This one makes for a nice story when I talk about computer-specific language issues: I'd love for someone to tell me a story about something they couldn't solve (or at least not the way they wanted to).
However, it can be daunting, as it's one you need to get right. Involving math, or scaling, or some other stuff? I'm checking in on the Fullstack Engineer role I interviewed for on February 20th, 2021. 4 Software Engineers Share the Biggest Technical Challenges They’ve Faced | Built In ATX. Good work is quiet and consistent, usually not astonishing. But there are many interviewers that don't expect to hear the atom bombs, or the circus acts, or whatever else. I could never figure why wasn't it working. My effort was target at using inside a bigger system.
If you start from scratch, you understand the whole stack/platform, everything is customized to your liking, and so on. Further review: know the answers to these 100 Common Interview Questions to be fully prepared for your interview! Unlike the more specific questions we've outlined above, this question is a generic question that requires a concise but powerful answer. Later a junior employee worked on it, was unable to develop pixel-level measurements still, though was able to get it to work at lower resolutions. I proposed making pixel-level optical measurements on mirasol displays using a high-resolution camera to watch those pixels after subjecting them to complex drive waveforms. We also leveraged multiple ingress controllers in the Kubernetes cluster to support different canary mechanisms for the F5 traffic versus the AWS ALB traffic. Devil is in the details - and "spinning" it correctly without bad mouthing the company (Which I do like, otherwise I'd not still be there) and while keeping to that main point (upgrading a company) is... interesting. What is the hardest technical problem you've solved now. If you're not careful, it can lead to unexpected consequences when deploying updates. The value is preserved using a constant to ensure the original fractional number is returned to the backend on a response from a vendor containing the fully constructed fractional number. This email should be short and sweet and should include: An example email could look like this: Hi Josephine, Thank you for taking the time out to speak to me yesterday — I throughly enjoyed discussing the frontend engineer role with you. For example, we would often find a chart disappearing or seeing display settings intended for one chart get applied to all charts. So yeah - this is very vague question in my opinion.
If talking about money wasn't uncomfortable enough already, most job seekers worry that proposing the "wrong number" would cost them the job — or land them a job offer with a disappointing salary. An example of how to best answer this question for entry level candidates: "In my recent internship, I was given a technical problem that no one internally had yet been able to solve. For originality, what about the problem made it non-trivial to solve with out of the box tools? If you chose a bug fix, can you describe exactly what triggered the bug as opposed to just knowing what fixed it? That's why we can't look back at something as "hard".
But they also need to show they can plan workflows, solve problems, and work in teams to ensure a smooth development process if they get hired. Solution: Security is not just the responsibility of the software engineer but also the responsibility of all the stakeholders involved including the management, project managers, business analysts, quality assurance managers, technical architects, and application and developers. So my way of dealing with it is to leave and go somewhere else. For our Ruby on Rails app during a rolling deploy process. Roadblocks are inevitable with any project, and code is notoriously finicky. If you can get orders of magnitude improvements left and right, it means that something about the company's management is off. The discovery helped tie all the pieces of the dashboard builder together. They are also developers.
Simply respond to the original follow-up email to help the hiring manager keep track of each applicant. It helped me realize that every decision should be made with purpose — and it's important to keep in mind future improvements. You want someone whose output is professional and consistent. Something something smart-person-speak. Displaying multiple types of charts meant numberless possibilities of what could happen, and what could go wrong. Unexpectedly difficult to write with some features we wanted, but after a couple of iterations, I finished, and since then, new features and plugins worked perfectly and nicely together, and were easy to add and implement. It's a private group, but recently it got some attention on Twitter and we figured it might help aspiring data scientists if we published a few of the conversations we've been having on there.
It doesn't involve pushing the limits of your datasources or inventing new algorithms. At my current company/position, our group basically replaced an outside company - two programmers. Leveraging Technology as a Strategic Differentiator in an Organization's Growth. The hardest technical problems I've run into, have been mostly human; i. e. other people.
Here is what I did when I was approached with a request to resolve the problem…". Within Agile work practices, it's usually a team effort to decide the best programming languages/tools/services are the best fit for the project, within customer requirements. Successful salary negotiation, like any negotiation, relies heavily on your knowledge about the market, "intuition" about when to engage in this topic, and some rhetorical skills. Just trying to explain why I have a hard time with this question. I just don't think it's a good interview question. This might sound like humblebragging, and perhaps it is.
I wanted a good enough analytical solution. Systems get convoluted in the process of development, business needs demand quick shoehorning of something instead of thorough refactoring, etc. But that was no good because I couldn't share my weak_ptr<> so it's not really useful. I was able to reach out to experts in varying areas and pull ideas together to make solid, confident decisions about our direction. With that said, there's a fine line between showing your eager attitude and coming off as desperate. Solution: Testing the software, application, or product in a separate real-life test environment is critical to your software's success. These software development challenges need to be addressed almost immediately to reduce the impact they have on your end product. Therefore, your answer should confirm that you'll be a good hire. Then you don't have to stress too much about showing your long-term commitment when answering this question. So my point is that probably there are several axes of "hardness" in a problem that can be mixed together, and that makes it difficult to compare a problem to another (i. over which combination of axes are you comparing one to another? WTF is this gloriousness? When there's limited time and multiple projects going on, you may not be able to give 100% to the projects at hand. Think about this as your elevator pitch—you should be able to sell yourself to the interview within a matter of minutes.